Grégory Joseph wrote:
Hi,
I was pretty sure I'd done that before but somehow can't find it in my
backups; I seem to remember it had to do with plugging the plugin to a
different lifecycle phase.
As for the depenency to jr, you should be able to redeclare it in your
pom's build/plugins/plugin section and it would override the one
declared by the plugin. Re-release the plugin for each jr release
would mean that we would force users in using a given cuting edge
version. However, 1) i guess the next release will have an updated
dependency, hoping people can downgrade and stay compatible with their
project 2) your suggestion is very good, thought about it myself but
never had the time/need combination to do it myself. I'll happily
apply a patch ;)
One need to add <phase>compile</phase> to the <execution> block. The
site documentation mentions it but it gives the wrong string that one is
supposed to add.
Let's hope some kind soul will do the work for us as I don't have any
time for these interesting things :) .
Thanks,
Srgjan
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
