Hi folks!

In maven 3 there is a hard separation between plugin repositories and 'normal 
repositories. Which means a plugin cannot access a dependency which is not in a 
repository listed as <pluginRepository>

I can see that this was a attempt to make the repos more 'clean'. But serious, 
I'm not sure if the separation was such a wise step in the long run.

I now have the 3rd project where this leads to having almost all repos 
mentioned in <repositories> AND in  <pluginRepositories>.

The reason is that _lots_ of plugins needs dependencies to 'normal' artifacts.

* hibernate-maven-plugin
* jboss-maven-plugin
* tomcat-maven-plugin
.... you name it ...
basically ALL plugins which serve as helper for any 3rd party libraries and 
products.

In addition this problem hits a lot use cases where plugins get 'resources' via 
dependencies like
* maven-checkstyle-plugin
* maven-pmd-plugin
* emma-maven-plugin
* etc

Have you ever had one project which uses _none_ of those plugins? Then you are 
happy and don't need that. But for all other projects there is a good chance 
that you will end up duplicating all your repository sections as 
pluginRepository ...
 
Any feedback on this? 
Am I doing something wrong, or do others have similar problems with this new 
restriction in mvn3?

I can certainly see that there are good pro arguments, but they vanish if all 
repos get duped anyway, isn't?

LieGrue,
strub


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to