Hi, The plugin seems to be ready to be released and I'd like to get your feedback and make sure we are on the same page.
# The plugin is released as 1.0 with its components.xml # The maven ear plugin is updated to deal with this new packaging type and a set of its are added, relying on this plugin (<extensions>true</extensions>) # The artifacts-handlers file of Maven core is updated to take care of this new packaging type[1] Does that make sense? I've not found any other plugin that has a lifecycle for a packaging type. I have no idea how this works and if, for instance, a conflict might occur if someone enable the extensions of the maven-acr-plugin with the upcoming maven 3.0.4 ? I will call for a release as soon as I am done with documentation Thanks, Stéphane [1] http://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-core/src/main/resources/META-INF/plexus/artifact-handlers.xml On Mon, Mar 14, 2011 at 9:22 AM, Stephane Nicoll <[email protected]>wrote: > Hi, > > I am currently working on supporting the "application-client" artifact > type properly in the EAR plugin. Pablo (in CC) wrote a > maven-car-plugin[1] which is very similar to the EJB plugin but for > application-client type. Do we think it would be reasonable to add > this plugin to the portfolio of standard plugins? (if Pablo accepts to > contribute it to the ASF but I don't think it would be an issue). > > I am bit puzzled about the type 'car' since car is already used by > Geronimo for their deployment plans; <type>application-client</type> > would better fit I'd say (with a .jar extension) > > The problems I am having is that since we don't have an "official" > maven type for that thing and nothing to build it with Maven, I can't > detect these artifacts other than scanning every single jar file added > to a project to see if there is a META-INF/application-client.xml > file. Frankly, I am not going to implement a feature that will scan > every single jar file before building an EAR > > The plugin needs a bit of cleanup (namely the jEE version check) and I > don't know if the community uses this a lot but we don't cover the > whole spectrum of the JavaEE spec and it wouldn't cost us much to do > it. > > Can someone remind me how these "official" types gets added and > detected by Maven? Do we absolutely need to touch the core type > definition files or is there another way? > > Please let me know what you think. > > Thanks, > S. > > [1] http://code.google.com/p/maven-car-plugin >
