[
https://issues.apache.org/jira/browse/IVY-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659284#comment-13659284
]
Christian Plätzinger commented on IVY-1221:
-------------------------------------------
Since we have only rare test artifacts I have implemented another workaround.
The Ivy retrieve task is called from a single ant target. So I extended the
target to delete all test artifacts from the ivy cache directory. Thus Ivy is
forced to download the test artifacts every time and gets the latest version.
Not that nice but works for me ;)
{code}<target>
...
<delete verbose="true">
<fileset dir="${ivy.defaultCacheDir}"
includes="**/*tests.jar"/>
</delete>
...
</target>
{code}
> ivy won't resolve updated maven SNAPSHOT artifacts with classifiers from
> local repo
> -----------------------------------------------------------------------------------
>
> Key: IVY-1221
> URL: https://issues.apache.org/jira/browse/IVY-1221
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.2.0-RC1
> Environment: Mac OS X 10.6, Ant 1.7.1, Maven 2.2.1
> Reporter: Nick Bonatsakis
> Labels: patch
> Attachments: fix3.patch
>
>
> The situation I'm running into is as follows: I have a maven project that
> produces two artifacts foo-SNAPSHOT.jar and foo-SNAPSHOT-tests.jar. When I
> resolve these via ivy, they are both pulled properly initially, however with
> the following ivysettings ibiblio, only the foo-SNAPSHOTS.jar is getting
> updated on resolve after re-installing via maven.
> <ibiblio name="local_m2_repo"
> m2compatible="true"
> usepoms="true"
> changingPattern=".*-SNAPSHOT.*"
> changingMatcher="regexp"
> checkmodified="true"
> root="${localm2repo.url}"/>
> I started out trying the pattern ".*-SNAPSHOT" which I would have expected to
> pick up the tests jar, but tried this in the hopes of getting it to work,
> which of course it did not. This doesn't seem to be a retrieve issue either,
> the modified date of the foo-SNAPSHOT.jar in the local ivy cache is being
> updated while foo-SNAPSHOT-test.jar is not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
