Jason van Zyl wrote: ...
I will add this use case as it has become fairly common and to provide a high degree of usability plugins builds and installations have to be taken into consideration when bootstrapping.
I would suggest the script solution as it's pretty easy and you need to invoke maven a second time to pick up the plugins you installed the first time.
As a little follow up, I took a peek and it probably wouldn't be that hard to poke something in to check to process the plugins before each build. We are planning to release rc2 next week so I'll try to squeeze that a fix in.
I have a small qestion, how long does it take to process the plgins? 1 sec, 10sec? if so, adding that chekc before everybild, would that not slow down the whole process a lot?
maven does after all know when new plugins are beeing installed.. why not do the check there instead of before every build?
if you make the funktionality to "process the plugins" "public" to the jellyscripts, it would not be hard to add the functionallity to the plugin:install jelly script or any other jelly script that needs to.
is not that just a more flexible sollution?
/Christian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
