Hi, I'd like to start adding explicit dependencies for maven plugins. Now that each plugin can be downloaded separately, I think this is a required step: Let's say I release a new version of plugin X. However, for this plugin to run I've also modified another plugin Y. When the end user runs "maven plugin:download -DartifactId=X...", plugin Y (in the correct version) also has to be downloaded.
I think a rule of thumb is that we should have these dependencies on latest released version of other plugins and not on SPANSHOT. Of course, if you're developing a new version of a plugin and it absolutely requires an unreleased of another plugin then the dependency should be on SNAPSHOT. However, the release process should release that other plugin first and then your plugin. Of course, there must be no SNAPSHOT reference when releasing plugins. What would be a real helper to add these dependencies would be a optional "strict" mode for <attainGoal>. By strict, I mean that only goals from declared dependencies would be allowed to run. Others will fail with a warning stating that it is missing a dependency. This would allow to easily identify dependencies. However, I'm not sure how easy (or how hard) it would be to implement this optional strict mode. Any idea? Fire away! Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
