You could probably grab the source, tweak it a bit, and create a new configuration value "createEarFile" or something (with default value true) to meet your needs. Then the plugin does exactly what you want/need.
Wayne On Thu, Sep 25, 2008 at 11:07 AM, Kem Elbrader <[EMAIL PROTECTED]> wrote: > I've tried several other phases with no luck. It appears that the > dependencies are copied and any other ear work is done during the > package phase where the ear:ear goal is bound. But the packaging of > the .ear file is also done by this goal. Is there a way to prevent > this plugin of creating the .ear file? > > On Wed, Sep 24, 2008 at 12:30 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: >> On Wed, Sep 24, 2008 at 11:30 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: >> >>> Take a look at the lifecycle [1] and see if you can stop at one of the >>> earlier phases. Maybe 'mvn test' or 'mvn compile' would do what you >>> need. >> >> Missing footnote. :) >> >> [1] >> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html >> >> -- >> Wendy >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > 've > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
