correction about assembly:single ;-) dont remember what it is for ;-)
On 10/9/06, dan tran <[EMAIL PROTECTED]> wrote:
Must agree with the plugin's doc is very confusing assembly:assembly is meant to run on command line only. Attach to phase will cause the problem you saw. assembly:attached is meant to be configured in a phase in the pom.xml, its output also is installed/deployed assembly:single: is the same as assembly:attached but its output never get installed/deployed. -D On 10/9/06, pjungwir <[EMAIL PROTECTED]> wrote: > > > > dan tran wrote: > > > > instead of attaching assembly:assembly to your package phase, use > > assembly:* > > attached * > > > > Ah, thank you, assembly:attached works great! So what is the difference > between assembly:attached and assembly:single? I see them both listed > here: > > http://maven.apache.org/plugins/maven-assembly-plugin/ > > From the descriptions, assembly:single seems to be identical except for > this > line: > > > > > Do not specify it as an aggregator, so it is only for a single > project. > > > > What is an aggregator? > > And what does this mean?: > > > > > Both cases aid it in working around issues with the Maven lifecycle > that > > should be addressed in Maven 2.1. > > > > Is there somewhere I can learn about Maven 2.1? I don't see anything on > the > maven homepage. Is there a cvs/svn checkout? A discussion of > features/changes? Will 2.0->2.1 be as drastic as 1->2? > > I like that "mvn assembly:assembly" does everything up to package. But > it's > a shame that when bound to a lifecycle the mojo can't be smarter. Even > the > docs suggest that assembly:attached and assembly:single are workarounds. > I > see that besides @execute, there is also a @phase attribute. Would this > handle both cases properly?: do everything up to package when run as a > goal, > but don't do anything extra when run bound to a phase? > > The BBWM book says that one benefit of "convention over configuration" > is > that developers can go to any project and know what it takes to run the > build. But if some projects use "mvn package" and some use "mvn > assembly:assembly," this is mitigated. Besides, "mvn assembly:assembly" > is > typing too much. :-) > > Thanks again for your help, > Paul > > -- > View this message in context: http://www.nabble.com/assembly%3Aassembly-does-everything-twice-tf2413291.html#a6728854 > > Sent from the Maven - Users mailing list archive at Nabble.com<http://nabble.com/> > . > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
