[
https://issues.apache.org/jira/browse/IVY-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18098924#comment-18098924
]
Maarten Coene commented on IVY-1671:
------------------------------------
I gave it a try, but didn't encounter this issue.
Could you provide an ivy.xml file and a simple Ant script that can be used to
reproduce the issue?
> source-classifier artifact no longer resolved via configuration mapping after
> upgrade to 2.6.0
> ----------------------------------------------------------------------------------------------
>
> Key: IVY-1671
> URL: https://issues.apache.org/jira/browse/IVY-1671
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.0
> Environment: Linux
> Java 17
> Reporter: Frank
> Assignee: Maarten Coene
> Priority: Major
>
> After upgrading from Ivy 2.5.2 to 2.6.0, a dependency that maps a local
> configuration to the target module's {{sources}} configuration no longer
> resolves the {{{}source{}}}-typed (classifier {{{}sources{}}}) artifact. The
> main jar ({{{}type="jar"{}}}, no classifier) is still resolved correctly.
> ivy.xml:
> {code:java}
> <dependency org="com.twelvemonkeys.imageio" name="imageio-core" rev="3.9.4"
> conf="compile->default; ide->sources"/> {code}
> With Ivy 2.5.2, this retrieves a file imageio-core-source.jar.
> With Ivy 2.6.0, imageio-core-source.jar is gone.
> Cached module descriptor
> (com.twelvemonkeys.imageio/imageio-core/ivy-3.9.4.xml), generated correctly
> by Ivy from the Maven POM, and identical before/after the upgrade:
> {code:java}
> <publications>
> <artifact name="imageio-core" type="jar" ext="jar" conf="master"/>
> <artifact name="imageio-core" type="source" ext="jar" conf="sources"
> m:classifier="sources"/>
> <artifact name="imageio-core" type="javadoc" ext="jar" conf="javadoc"
> m:classifier="javadoc"/>
> </publications> {code}
> Since the module metadata is identical and correct in both cases, the
> regression appears to be in artifact-to-configuration matching during
> resolve, not in POM-to-Ivy translation.
> Resolution report for configuration ide, with Ivy 2.5.2 (correct — both
> artifacts listed):
> {code:java}
> <h5>Artifacts</h5>
> <table>
> <thead>
>
> <tr><th>Name</th><th>Type</th><th>Ext</th><th>Download</th><th>Size</th></tr>
> </thead>
> <tbody>
> <tr><td>imageio-core</td><td>source</td><td>jar</td><td
> align="center">no</td><td align="center">115 kB</td></tr>
> <tr><td>imageio-core</td><td>jar</td><td>jar</td><td
> align="center">no</td><td align="center">114 kB</td></tr>
> </tbody>
> </table>{code}
> Resolution report for configuration ide, with Ivy 2.6.0 (source/classifier
> sources artifact missing):
>
> {code:java}
> <h5>Artifacts</h5>
> <table>
> <thead>
>
> <tr><th>Name</th><th>Type</th><th>Ext</th><th>Download</th><th>Size</th></tr>
> </thead>
> <tbody>
> <tr><td>imageio-core</td><td>jar</td><td>jar</td><td
> align="center">no</td><td align="center">114 kB</td></tr>
> </tbody>
> </table> {code}
> Environment note:
> Fresh, version-specific cache directory used for each Ivy version (problem
> with cache reuse across versions ruled out as a cause).
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
