[snip] > In order to simplify things, James Ervin and I started another project - > very closely related to m2eclipse - m2eclipse APIs. The purpose - is to ease > programmer's access to the Maven universe. For now we came from our > immediate needs - necessity to find an Artifact, find all Artifact > dependencies as a resolved scoped classpath or mavenize an Eclipse project. [snip]
Fantastic! > It would be awesome to hear comments - what kind of functionality is > interesting for users. This may be a little far afield but for the 9.3 release of m2eclipse, it would be nice (well, a requirement for us) to be able to extend or otherwise hook into m2eclipse for the purpose of filtering the available archetypes [1] used for new project creation. I'm imagining public extension points to the m2eclipse plugin that would allow one to extend certain behaviors -- think callbacks. Although, I've been thinking that a more appropriate design might be to have the archetype filtering handled by the archetype plugin itself, perhaps via a kind of policy. In any event, looks very promising. Oh, and is it just me or are maven, eclipse and the osgi frameworks the vanguard in large scale opensource java reuse? ;-) [1] http://jira.codehaus.org/browse/MNGECLIPSE-527 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
