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. > You may configure plugin repositories on a per-project basis. Nice. Can that be done with paths relative to the project directory? Greetings, -- Sybren Stüvel <[EMAIL PROTECTED]> Software Engineer CHESS iBusiness Nieuwe Gracht 13, Haarlem Postbus 5021, 2000 CA Haarlem
signature.asc
Description: PGP signature
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
