- This topic has 3 replies, 3 voices, and was last updated 12 years ago by
.
-
Posts
-
I have a Maven project that depends on 20 or so other Maven projects. When I deploy the war in MyEclipse I get a set of jar files, based on my Web Deployment settings, in my WEB-INF/lib directory. This set of jars include the Maven dependencies of my project plus a lot of jars from those other projects. So…the issue is I want to exclude some, but not all of the jars from those dependent projects. How do I do this? I tried using plugin tags for the maven-war-plugin but that did nothing. I seems the deployment part of MyEclipse is not even using that plugin for maven projects.
If my projects pom file had a dependency tag for the other projects, I would just add exclude tags for the jars I didn’t want. But I am not using pom dependencies on those other projects. I am setting them up as dependent projects in MyEclipse.
Thaks in advance.
Bob
Bob,
Sorry that you are seeing this issue. I have escalated it to a dev team member. They are looking into it.
Sorry for the inconvenience
Bob,
You are correct that the MyEclipse deployer will not deploy using the Maven WAR plugin, that would typically be used when you run a Maven specific goal or build. Due to the additional support required during deployment, we need to deploy using our own deployment algorithms.
However, if you use the provided scope for a dependency (in the pom.xml), then the MyEclipse deployer will skip it during deployment. Could you use this for the dependencies that you do not wish to deploy in the projects that the Maven web project depends on.
Hope this helps.
@Support-Brian wrote:
Bob,
You are correct that the MyEclipse deployer will not deploy using the Maven WAR plugin, that would typically be used when you run a Maven specific goal or build. Due to the additional support required during deployment, we need to deploy using our own deployment algorithms.
However, if you use the provided scope for a dependency (in the pom.xml), then the MyEclipse deployer will skip it during deployment. Could you use this for the dependencies that you do not wish to deploy in the projects that the Maven web project depends on.
Hope this helps.
Interesting idea. Its a bit of a kludge from the maven perspective and I’d have to put the dependencies in a profile the only get used when building from MyEclipse, but it just might work. I’ll give it a try. Thanks for the suggestion.
Bob
