Sybren Stüvel wrote:
Hi.
Our current projects currently make extensive use of Maven 1.0. Since
Maven 2 looks very promising, we'd like to make the switch. At this
moment, many projects contain project-specific goals in maven.xml. We
could convert this code into M2 plugins, but that would separate the
project-specific plugin from the rest of the project.
What's so bad about that?
Joining the project would require yet another action to be done by the
programmer, namely copying the plugin from the project to his/her M2
plugin directory. Changes to the plugin would have to be copied back and
then committed.
I don't quite get it. You just mvn clean install plugin and it's available to
the project. I also have several project-specific Maven plugins. They just
reside in their own modules, build during the whole build and thus available to
the subsequent modules.
You may configure plugin repositories on a per-project basis.
Nice. Can that be done with paths relative to the project directory?
It's just a simple url, I think you can configure a relative path there as well
(haven't tried myself, however).
<project>
...
<pluginRepositories>
<pluginRepository>
<id>snapshots</id>
<url>http://people.apache.org/maven-snapshot-repository/</url>
</pluginRepository>
</pluginRepositories>
...
</project>
Bye.
/lexi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
