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
http://jira.codehaus.org/browse/MINDEXER-11
Please comment.
Thanks,
~t~
2011/2/9 Tamás Cservenák ta...@cservenak.net:
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
On 2011-02-08 21:41, 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.
A list of released plugins is now in place, as well as some that are in
the pipeline
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
If a plugin is marked as thread safe, it is stated on the goal detail page.
See [1] for an example.
I believe it's the plugin-plugin that creating this info and possible some
plugin sites created with an old version of plugin-plugin doesn't contain
this info even though a goal is marked as thread
Right, this was added in version 2.6 of Plugin Plugin, so any site
generated with an earlier version won't have that info. See
http://jira.codehaus.org/browse/MPLUGIN-169
That however only tells you *if* the latest version is thread safe, but
it doesn't tell you *when* it was first marked as
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,
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.
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
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
Hi
I'd like to start a list of which versions of plugins and components are
@threadSafe. Where should we have such a list?
--
Dennis Lundberg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands,
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
11 matches
Mail list logo
