RE: indiscriminate dependencies ...
Try mvn dependency:analyze It will tell you when you are not using dependencies and also when you haven't declared things you are directly using. -Original Message- From: Giovanni Azua [mailto:[EMAIL PROTECTED] Sent: Sunday, September 30, 2007 8:27 AM To: 'Maven Users List' Subject: indiscriminate dependencies ... Hi all, I get very frustrated when I would like to quickly build some project X and I see maven downloading half internet just because one of the developers of project X thought that some of the dependencies might be needed at some point but not now. This also happens when you develop project A that depend on B but then someday you don't depend on B anymore and you forget getting rid of the dependency entry B in A's pom.xml I know it is not Maven's fault. It is just that maven makes it very easy to depend on anything. Is there any way perhaps some fancy plugin that will prevent maven from downloading every little single dependency but only those actually used by the project X ... kind of lazy dependency resolution, so developers suggest but do not command what dependencies are required by the build ... You get the idea. regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
indiscriminate dependencies ...
Hi all, I get very frustrated when I would like to quickly build some project X and I see maven downloading half internet just because one of the developers of project X thought that some of the dependencies might be needed at some point but not now. This also happens when you develop project A that depend on B but then someday you don't depend on B anymore and you forget getting rid of the dependency entry B in A's pom.xml I know it is not Maven's fault. It is just that maven makes it very easy to depend on anything. Is there any way perhaps some fancy plugin that will prevent maven from downloading every little single dependency but only those actually used by the project X ... kind of lazy dependency resolution, so developers suggest but do not command what dependencies are required by the build ... You get the idea. regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: indiscriminate dependencies ...
i'm unaware of any plugins to prohibit unused deps but the dependency plugin has an analyze goal can give you a report showing dependencies that are declared and unused that I find useful when cleaning dependencies. mvn dependency:analyze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: indiscriminate dependencies ...
on a related note ... is there a global exclusions ability? currently you have to track down every use of the dependency in order to exclude it. For me the classic case of this is junit. We don't use junit but every jar that we include seems to have a dependency to junit... which completely clutters the pom. On 9/30/07, Tomislav Stojcevich [EMAIL PROTECTED] wrote: i'm unaware of any plugins to prohibit unused deps but the dependency plugin has an analyze goal can give you a report showing dependencies that are declared and unused that I find useful when cleaning dependencies. mvn dependency:analyze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: indiscriminate dependencies ...
http://jira.codehaus.org/browse/MNG-1977 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
