Which implies that it should be a versioned file....
Sounds like a jar with a resource containing the parallel compatibility
info....
We'd have to maintain it versioned.... and perhaps provide some system
property to ovrerride the version via settings.xml... but each release of m3
would have it's own compatibility info and we would have another state:
unknown
e.g.
<thread-safety>
<plugin groupId="..." artifactId="...">
<wieve-mode action="ban" versions="...">message</wieve-mode>
<wieve-mode action="warn" versions="...">message</wieve-mode>
<wieve-mode action="checked" versions="..."/>
<parallel-mode action="ban" versions="...">message</paralle-mode>
<parallel-mode action="warn" versions="...">message</paralle-mode>
<parallel-mode action="checked" versions="...">message</paralle-mode>
</plugin>
</thread-safety>
Any plugins not in the list would be "unknown" and the user gets a big fat
warning
-Stephen
On 26 April 2010 10:15, nicolas de loof <[email protected]> wrote:
> >
> >
> > The issue is http://jira.codehaus.org/browse/MNG-4642, and as an
> > alternative solution we could
> > simply make a list somewhere that blacklists/whitelists/greylists
> plugins,
> > as long as there's a reasonable
> > way to update such a list. Maybe something enforcer-like;
> >
> > org.codehaus.plexus:plexus-io:[,1.0), BAN:"Serious compromises of thread
> > integrity"
> > org.apache.maven:plugins:maven-era-plugin:*:WARN:"Can only run once per
> > reactor"
> > org.codehaus.modell:modello-maven-plugin:(,1.3]:BAN:"Does not work
> -period"
> >
> > If there was some place we could put such a list and update it we could
> > probably provide the best
> > possible information. How could we do this ?
> >
> >
> We could maintain such compatibility matrix using a wiki page, but - to be
> usable from the build by various enforcer/check plugins - it should be
> deployed on central / downloaded to local repository in some
> computer-compliant format.
>
