> > A comment on MAVEN-256
> > (http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-256)
> >  indicates a fix for goals executed via attainGoal being called 
> > multiple times.  Is this something I can move forward with 
> (ie. update 
> > a few plugins that are causing me grief and submit patches), or is 
> > there a plan to fix this issue a different way?
 
> What particular plugins/goals are causing you grief?

I'm doing some things in a java:compile preGoal.  The preGoal is getting
executed three times due to this issue:

Once due to maven-jdepend-plugin:report (does an attainGoal on
java:compile)...
Once due to maven-findbugs-plugin:report (via the jar prereq...calls
test:test)...
Once due to maven-clover-plugin:report...

I can understand a second compile for the clover plugin due to the
nature of what it's doing, but the other two have no reason to have a
unique session (that I know of).  Also, is there some way I could detect
that we're coming in for a second round of compiling (in the case of the
clover plugin) and avoid doing my logic?

> We need to be wary of introducing new behaviour late in the 
> 1.0 RC cycle. A lot of people may have worked around this in 
> their own way that could break.

I understand...so is this scheduled to be broken later, then?  ;)  If
anyone has any of these workarounds that they can share, I'd be more
than happy to use one of them.

-- Sean T.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to