I think it would be a useful service to our users to list which plugins
and components are @threadSafe, and also in which version it was first
marked as @threadSafe.

We can start writing things down on the wiki page you mentioned. I'll
add a new heading and start to accumulate the info. We can move it to
the Maven site when we are done. Perhaps each plugin should have that
info on its own site?

On 2011-02-07 21:39, Kristian Rosenvold wrote:
> 
> find . -name *Mojo.java | xargs grep threadSafe  
> 
> I suppose that may not be good enough ;) I was hoping to get all the 
> non-deprecated 
> core plugins @threadSafe, and by the looks of it it's not that far off. 
> If I subtract the retirement-candidates there only seem to be a few left.
> 
> I'm not technically sure it helps, but I'd generally expect users running
> parallel to be running the latest versions of everything. I don't think it'd
> be *that* much work to make a wiki page or similar describing "when" each 
> plugin/lib
> was declared threadsafe, since it's all in jira. Would we still need it if
> I just ran through the remaining plugins ?
> 
> As you're aware I've documented known problematic libraries at [1], but I'm
> open to doing something else/more.
> 
> Kristian
> 
>> ma., 07.02.2011 kl. 18.57 +0100, skrev Dennis Lundberg:
>> Hi
>>
>> I'd like to start a list of which versions of plugins and components are
>> @threadSafe. Where should we have such a list?
>>
> 
> [1] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to