The ear plugin has its definition built in - it should work. Is nothing produced, or is the ear empty?
Currently it doesn't aggregate modules, but instead uses dependencies so must be a side-by-side project to its modules (like in m1). - Brett On 10/4/05, Robert Biernat <[EMAIL PROTECTED]> wrote: > Hi, > > > > I'm attempting to convert and existing project that currently produces a > single ear artifact to use m2, but it appears that even when my top level > pom.xml has a packaging type of ear, the ear plugin never gets invoked. I've > looked at the code for the plugin and executed maven with the debug switch > and do not see any logging from then plugin. > > > > In the doco on the website it talks about modifying the > META-INF/plexus/components.xml file contained within the plugin's jar file > when a new type of packaging is required. I looked at the ear plugins jar > file and it doesn't contain this file. Am I required to modify/create this > file or possibly some other file in order to associate the ear plugin with > the "package" lifecycle phase. > > > > Thanks > > > > Rob > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
