Re: New version of sar plugin

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaarg :)

Sometimes I hate not knowing what the hell is going on in maven build. Anyways 
I followed the instructions and foo-barred my maven install because of some 
wierd interaction between different versions of the same plugin.

Anyways I really really dont like the idea of not using the latest build of 
the plugin when I am rebuilding the source. I want to be able to go into the 
directory jcontainer/loom and just do maven and have it all build. It is way 
to easy to get inconsistencies in builds if half the build is done using a 
jar built 2 weeks ago and the rest uses the latest stuff (which could happen 
if the plugin is continually developed).

So I rewrote the reactor and made it so that our build always uses the latest 
build of the plugin. The reactor at base directory (jcontainer/loom) will 
install this plugin and use it during the "build" goal.

I have also made the plugin use the .class files it stores internally. It took 
me ages to figure out how to do that ! Gotta love undocumented features ;)

Mauro - could you check it out as you seem to know the most about this area. 
Could you make sure I didn't stuff anything up. In theory you can go to base 
directory of loom and just type build and it will build the complete thing 
cleanly ... fingers crossed.

The dependencys also need to be plugin dependency now rather than jar 
dependency (as a result of storing .class files in plugin) which seems to 
work under rc1.

-- 
Cheers,

Peter Donald
*-------------------------------------------*
| "A handful of sand is an anthology of the | 
|            universe." -Albert Einstein    |
*-------------------------------------------*