[jira] (MDEP-272) purge-local-repository does nothing if certain dependencies are included
[
https://jira.codehaus.org/browse/MDEP-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier closed MDEP-272.
--
Resolution: Fixed
More refactoring of the purge-local-repository goal in
[r1400760|http://svn.apache.org/viewvc?view=revision&revision=1400760],
including an IT using a version range. I believe this issues is resolved now.
> purge-local-repository does nothing if certain dependencies are included
>
>
> Key: MDEP-272
> URL: https://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: Paul Gier
> Fix For: 2.6
>
> Attachments: pom.xml, PurgeLocalRepositoryMojo.patch,
> PurgeLocalRepositoryMojo.patch
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-272) purge-local-repository does nothing if certain dependencies are included
[
https://jira.codehaus.org/browse/MDEP-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated MDEP-272:
---
Fix Version/s: 2.6
Assignee: Paul Gier (was: Brian Fox)
Thanks for the patch, however we've made some recent changes to the
purge-local-repository goal, and not every use case requires the full test
scope dependency resolution. Can you check if this issue still affects you?
And if possible provide a new patch?
> purge-local-repository does nothing if certain dependencies are included
>
>
> Key: MDEP-272
> URL: https://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: Paul Gier
> Fix For: 2.6
>
> Attachments: pom.xml, PurgeLocalRepositoryMojo.patch,
> PurgeLocalRepositoryMojo.patch
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-272) purge-local-repository does nothing if certain dependencies are included
[
https://jira.codehaus.org/browse/MDEP-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310743#comment-310743
]
Tuomas Kiviaho commented on MDEP-272:
-
I think that this patch also takes care of MDEP-256 and MDEP-290
> purge-local-repository does nothing if certain dependencies are included
>
>
> Key: MDEP-272
> URL: https://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, PurgeLocalRepositoryMojo.patch,
> PurgeLocalRepositoryMojo.patch
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-272) purge-local-repository does nothing if certain dependencies are included
[
https://jira.codehaus.org/browse/MDEP-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated MDEP-272:
Attachment: PurgeLocalRepositoryMojo.patch
Here's an updated version of the patch that avoids NPE caused by artifact files
which aren't present in local repo.
> purge-local-repository does nothing if certain dependencies are included
>
>
> Key: MDEP-272
> URL: https://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, PurgeLocalRepositoryMojo.patch,
> PurgeLocalRepositoryMojo.patch
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-272) purge-local-repository does nothing if certain dependencies are included
[
https://jira.codehaus.org/browse/MDEP-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated MDEP-272:
Attachment: PurgeLocalRepositoryMojo.patch
For me it failed with dependencies that had unresolvable parents or which used
version ranges. Here's a fix that I'm using to get past this problem.
> purge-local-repository does nothing if certain dependencies are included
>
>
> Key: MDEP-272
> URL: https://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, PurgeLocalRepositoryMojo.patch
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
