Sonatype will be presenting at Eclipse Day hosted by Google in California this week.
Each year Google hosts an Eclipse Day and puts together an agenda that includes Eclipse and Google related topics. This year there will be presentations that feature Android, Helios, GWT, EGit, Linux Tools, Eclipse 4.0, EMF, XText and more. Sonatype’s founder, Jason van Zyl, will be presenting on Next Generation Development Infrastructure with Maven, m2eclipse, Nexus and Hudson.
This talk focuses on the Maven Ecosystem and the under-pinnings of technologies that are going to shape the Next Generation Maven Development Stack. While the Maven 3 release retains backward-compatibility with plugins written for Maven 2, the foundational technologies used in Maven are being recast to allow for more space for expansion as Maven starts to expand into newer spaces like OSGi and Polyglot development. In this talk, van Zyl discusses new, emerging technologies and how they fit into the overall approach to the development of a Next Generation Maven Development Stack. This presentation will include an overview of the following technologies:
- Moving Maven from Plexus to Guice
- Continued work to support OSGi development with Tycho
- Support for Polyglot development and alternative languages
- m2eclipse, the primary Eclipse IDE Maven-integration used at Sonatype which is also integrated with STS and JBoss Tools.
Eclipse Day hosted by Google:
- Thursday, August 26, 2010
- 9:00am – 5:00pm
- 1600 Amphitheatre Parkway
- Mountain View, CA
This August Sonatype will be presenting at Eclipse Day hosted by Google in Mountain View, California. Each year Google hosts an Eclipse Day and puts together an agenda that includes Eclipse and Google related topics. This year there will be presentations that feature Android, Helios, GWT, EGit, Linux Tools, Eclipse 4.0, EMF, XText and more.
Sonatype founder Jason van Zyl will be presenting on next generation development infrastructure with Maven, M2Eclipse, Nexus and Hudson. This presentation will show how to employ best practices when using these tools individually as well as together, as a powerful set.
All development organizations eventually converge on a set of tools to reduce costs, lower onboarding time, and leverage knowledge in strong communities to create standard processes. To this end we see in many organizations the emergence of a standard development stack consisting of Maven, M2Eclipse, Nexus & Hudson. Sonatype itself leverages this stack on a daily basis and this discussion will focus not only on the tools individually, but how they can work together to create a best practices approach to building and delivering your software in your organization.
Eclipse Day takes place on August 26, 2010 in Mountain View, California. For more information please visit the Sonatype events page. We hope to see you there!
Sonatype is happy to announce that Google Web Toolkit 2.0.4 jars are now available in the Maven Central repository. The Google Web Toolkit blog explains this move in more detail:
Better maven support has been frequently requested on the issue tracker and mailing list, and this is a first step in that direction. In the future, Google will publish GWT releases to maven central as part of the release process.
The GWT 2.0.4 jars currently in the repository include gwt-user, gwt-dev, and gwt-servlet. To publish these artifacts in the Maven Central repository, Google publishes artifacts to Nexus OSS, the Open Source oss.sonatype.org repository. You can see the Google-specific repository on this server here. Releases are staged to this Google repository on oss.sonatype.org and then subsequently released and synchronized to the Maven Central repository.
Now that I’ve had a few days to start using with Google App Engine’s Java support, some patterns are emerging and it’s becoming clearer what the lifecycle elements of an App Engine application is. Here’s the initial list of goals of what I’d like to see in a GAE Maven Plugin:
- gae:run – analogous to jetty:run. Runs a WAR project on the GAE dev appserver. Ideally has all the same reloading features that we know and love from the Jetty plugin.
- gae:start / gae:stop – this might be accomplished by creating a Cargo adapter for GAE’s dev appserver.
- gae:update – Deploys a project to GAE.
- gae:generate-appenginexml – Generate the appengine-web.xml file.
- gae:enhance-classes – perform the necessary DataNucleus byte code enhancement.
But the big one is some kind of processing that will let you know if your application uses classes not in the App Engine whitelist. The application I (perhaps foolishly) ported was an image manipulation application that uses some AWT classes internally. And a number of people have run into the Spring’s dependency upon JNDI when JPA is present. Neither of these issues came up when running the dev appserver locally. Even if they had, it’d be great to discover these types of issues at compile time, instead of at run time.
Anyone else have good goal ideas? Post them in the comments.