Good day to you, Gregory, I think it is simply for ease of use. Intead of configuring the assembly plugin, you can simply do mvn sources:jar. Same goes for the other packaing goals ( jar:jar, javadoc:jar, ejb:ejb, ejb3:ejb3, war:war, ear:ear, etc ). Usually, you don't have to use the assembly plugin because the other packaging goals are much easier to use. But if those goals are not enough for your needs, then go for the assembly plugin.
As for the difference between -sources and -src, I am not sure myself :-) Cheers, Franz Gregory Kick-2 wrote: > > After looking through the documentation for each of these plugins, I > am left with a few questions: > > - Isn't the functionality of the source plugin just a subset of the > assembly plugin (i.e. couldn't I just use the assembly plugin to do > the same thing and only have to worry about one plugin)? > > - Is there a reason that the assembly plugin uses -src for its > archives while the sources plugin uses -sources? > > - Should the Source Plugin be deprecated for a pre-defined assembly > descriptor with the same behavior? > > -- > Gregory Kick > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Source-Archives%3A-Source-Plugin-vs.-Assembly-Plugin-tf2963424s177.html#a8292765 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
