> | Having some minimal plugin versioning scheme from the > beginning would > | be good. Avoids having to retrofit them ala Centipede. > Perhaps with a > | well-defined <major>.<minor>.<micro> revision system, so > plugins can > | be automatically updated in the future by a 'maven:download-plugin' > | task. > Yep. My take is that plug-ins MUST be versioned in the > filename, i.e. maven-j2ee-1.0.0.jar.
You may want to look at how jEdit does versioning of plugins. Basically each plugin's jar file contains a properties file that describes its version and dependancies. This file is read by the classloader when the plugin is loaded. It's a very flexible system. You can find jEdit at: http://www.jedit.org Todd -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
