You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Mackinlay (JIRA)" <ji...@codehaus.org> on 2011/02/15 17:59:23 UTC
[jira] Commented: (MDEP-272) purge-local-repository does nothing if
certain dependencies are included
[ http://jira.codehaus.org/browse/MDEP-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256172#action_256172 ]
Paul Mackinlay commented on MDEP-272:
-------------------------------------
This does not look like it is specific to jasperreports.jar, I have other dependencies and am experiencing the same issue.
> purge-local-repository does nothing if certain dependencies are included
> ------------------------------------------------------------------------
>
> Key: MDEP-272
> URL: http://jira.codehaus.org/browse/MDEP-272
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: purge-local-repository
> Affects Versions: 2.0
> Reporter: Michele Lorenzini
> Assignee: Brian Fox
> Attachments: pom.xml
>
>
> I've noticed that the {{purge-local-repository}} goal does nothing if certain dependencies are present in the dependency tree of the project.
> After some attempts I've found some of the dependencies that can show problem.
> See attached {{pom.xml}}: if I run {{mvn validate}} as is, maven purges the local repository and the log4j jar is downloaded from the remote repository.
> Removing the comment around the jasperreports dependency and re-running {{mvn validate}} gives the following result:
> {code}
> [INFO] [dependency:purge-local-repository {execution: default}]
> [INFO] Nothing to do for project: test-issue:test-issue:pom:1.0.0.0-SNAPSHOT
> {code}
> So it seems that something goes wrong while resolving the dependencies for the project if the jasperreports jar is included, resulting in the {{purge-local-repository}} to skip the clean of the local repository.
> I dont know if this happens only with jasperreports dependency or if it is something more general.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira