Actually, I see this in the assembly documentation: http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html
"This goal will force Maven to build all included POMs up to the package phase BEFORE the assembly is processed." Did it always work this way? I thought that running an "assembly" included the "install" goal - when/why did this change? Additionally (but unrelated) when did we start stripping off the ".dir" suffix that's generated when you use assembly:directory? -----Original Message----- From: EJ Ciramella [mailto:[email protected]] Sent: Wednesday, March 11, 2009 5:06 PM To: Maven Users List Subject: RE: installing a war from a war based project automatically Mvn assembly:directory, but I've tried mvn install and that doesn't seem to work either. I think I see what's going on now - we have a custom packaging type that extends the war functionality. What's weird is, we're building the jar, then the war and finally our custom packaging type. But only the jar and the custom one are installed by default. I'm looking at the plexus configuration we have right now.... -----Original Message----- From: Wendy Smoak [mailto:[email protected]] Sent: Wednesday, March 11, 2009 4:12 PM To: Maven Users List Subject: Re: installing a war from a war based project automatically On Wed, Mar 11, 2009 at 12:48 PM, EJ Ciramella <[email protected]> wrote: > Is there a good way to, when building a war type project, to have the > resulting war file placed in the users local repository? Just 'mvn install' should do that. What command are you using and what's going wrong? -- Wendy --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
