Hi Ben,I hate usemod (it's ugly, it's primitive, it's limited). Up until now it was a means to an end. We've now got something better and the content could be easily ported.
Cool, but why don't you use the Apache Wiki? :-) Actually, I don't
really care which wiki we use but I think it's better to use only one.
If we decide to move what little information we have in that wiki out, I'll do the "conversion". If we decide we want a dedicated wiki and not a codehaus branded one, that can also be arranged. If the masses want to stay with usemod, that can be arranged, but only after they are beaten with a large bat.
Also, I think it is duplicate information from the one found inWell that would be an better way, but developer information is generally out-of-date also (developers are never removed). Cvs is the best way to go. Just trap the last few people to touch the plugin.
project.xml.
Why don't we instead generate a page on http://maven.apache.org/reference/plugins/ that would extract <developer> information from the project.xml ?
I see a core plugin as something that maven provides directly and is required to build maven. eg. jar / test etcAlso, I'm not convinced yet that there should core plugins versus non-core plugins. I think all plugins must be viewed equals. Otherwise, we will not resist the temptation to do some "hacks/shotcuts" such as the one done in the jar plugin which calls test:test when a jar is generated. There are other test plugins that would also like to do that for example. etc
Non core would be an extension such war or ear.
External would be plugins outside the control of maven
XDoc falls into a middle ground as it isn't truly required to build maven.
Also, I think that we need plugin metadata to stop people hooking inside plugins - eg.
http://wiki.codehaus.org/general/Maven_2fPluginMetadata
Cheers,
Ben
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
