It would be nice if one of the commiters checked in a plugin-map.xml
xdoc that would contain a list of plugins similar to that one above, and
then all commiters would add their name next to the plugins they are willing to work on, and their name in ( ) next to the plugins they
know good enough to fix if they happen to break.
That's what project.xml is for - if they're willing to work on it, add themselves as a developer/contributor
You are right, it's even better - provided that the information in the POMs is accurate - it would be gread if the commiters checked their entries.
I second Michal's opinion that we should not put any more plugins into maven repository, and that some of the existing one should move away onto another CVS repo on maven.apache.org or even to the repos of their associated software projects.
I thought maven-plugin was to be the new apache cvs repo for plugins once we worked out how to declare plugin usage.
Yup, that repo is up already. Non core plugins could move there when the discovery/dependency stuff works.
I believe it was agreed to use <type>maven-plugin</type>
It's OK with me if it is an established policy. I would personaly opt for shorter 'plugin' name, because there is no ambiguity here - what
other type of plugins artifact could we have?
R.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
