Re: Maven-sar plugin changes

Ryan Hoegg wrote:

> This is similar to what we had before.  The only inconvenience is that 
> if I want to make a jar with metainfo in it and install it in the 
> repository (for example, for inclusion in another project's sar) I have 
> to run "maven sar:metagenerate jar:install" or set that up as a goal in 
> maven.xml.  This is done in the jervlet projects now, the demoserver 
> uses jars generated by the jervlet and jervlet-jetty projects. 

yep - but then one might argue that if one wanted the metageneration of
code to be included in the jar:jar goal, it would probably be best to 
try to incorporate it in the jar plugin.

I am personally not too bothered about defining goals in my project.
As a matter of fact, I tend to always define at least the build
and deploy goals which then invoke the appropriated goals dependending
on the nature of the artifacts (jar, war, sar, etc ..), and/or attain
more than one goal if desidered (eg, jar:install, site:site).
This also allows the projects to have a consistent build facade,
independent of the what you are building, ie I know that 'maven build' 
will always build the project artifacts.

Cheers