Re: Maven-sar plugin changes

peter royal wrote:

> On Nov 4, 2003, at 8:27 AM, Mauro Talevi wrote:
>
>> Yes, but once the plugin has been installed, it applies the postGoal
>> to *all* java:compile, regardless of the fact that it is invoked in a
>> project that has the sar plugin as a dependency.
>> So it ends up being used in other projects that have no need for it.
>> And I think this is counterintuitive - and could also be annoying.
>
>
> ah, that's bad!
>
>> how about we try to keep it automatised but turn the thing on its head.
>> ie have a dependency structure like:
>>
>>    <goal name="sar:metagenerate" prereqs="java:compile"/>
>>    <goal name="sar:sar" prereqs="sar:metagenerate, jar:jar"/>
>>
>> in this way, someone wanting to compile and generate descriptors would
>> call the sar:metagenerate goal in place of java:compile.
>
>
> That sounds like it would work..
> -pete

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.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net