Just to chime in: Maven Indexer already cranks up and parses plugin.xml to gather the plugin prefix and existing goals....
Thanks, ~t~ On Tue, Feb 8, 2011 at 11:00 PM, Jason van Zyl <ja...@sonatype.com> wrote: > > On Feb 8, 2011, at 4:54 PM, Dennis Lundberg wrote: > >> My current focus is on the Apache Maven project's plugins and >> components. I think it is up to all plugin authors out there to document >> their own plugins. >> > > Same plugin could be run on the Apache Nexus instance. They have to mark the > mojos as theadsafe, but you could easily generate the list so people would > know, or could even be metadata IDEs could consume to guide users if they are > to find @threadsafe plugins. > >> On 2011-02-08 22:36, Jason van Zyl wrote: >>> Write a Nexus plugin that walks a repository looking for Maven plugins, >>> crack it open and pull out the metadata and make a report. >>> >>> You could take the Nexus Archetype plugin as an example. If you wanted to >>> create a global list this is the only real way you could accomplish this. >>> >>> On Feb 8, 2011, at 3:41 PM, Dennis Lundberg wrote: >>> >>>> 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 >>>> >>> >>> Thanks, >>> >>> Jason >>> >>> ---------------------------------------------------------- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> --------------------------------------------------------- >>> >>> We all have problems. How we deal with them is a measure of our worth. >>> >>> -- Unknown >>> >>> >>> >>> >> >> >> -- >> Dennis Lundberg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
