[
https://issues.apache.org/jira/browse/IVYDE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551741
]
Gerard Fernandes commented on IVYDE-66:
---------------------------------------
Workaround suggested by X. Hanin:
===============================================================================
There are other ways to implement what you want without having to use multiple
patterns. You can for instance use a custom attribute on your source artifact,
and put this token in your pattern. For instance:
<artifact name="commons-cli" suffix="-src" type="source" ext="zip"
conf="COMPILE" />
${ivy.conf.dir}/[organisation]/[revision]/[artifact][suffix].[ext]
But I agree that making IvyDE more flexible by recognizing artifact name suffix
for sources could make things easier to use. Feel free to open a new issue.
Xavier
===============================================================================
> IvyDE source artifact not recognised
> ------------------------------------
>
> Key: IVYDE-66
> URL: https://issues.apache.org/jira/browse/IVYDE-66
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Reporter: Gerard Fernandes
>
> IvyDE doesn't recognise source artifacts with a different name than the
> binary artifact.
> E.g., If I have a JAR called commons-cli-1.1.jar and it's source called
> commons-cli-src-1.1.zip, an Ivy configuration with the following will resolve
> and the sources are downloaded (can be confirmed by the Ivy report as well as
> checking the cache) but will NOT attach sources in Eclipse:
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli-src" type="source"
> ext="zip" conf="COMPILE" />
> </dependency>
> Ivy settings are:
> <filesystem name="externalLibraries">
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> </filesystem>
> The only way to make this work is to change Ivy settings to:
> <filesystem name="externalLibraries">
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]"/>
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.[ext]"/>
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]"/>
> <artifact
> pattern="${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]-src.[ext]"/>
> </filesystem>
> And rename
> commons-cli-src-1.1.zip
> To
> commons-cli-1.1-src.zip
> And finally change the Ivy configuration to:
> <dependency org="jakarta-commons-cli" name="commons-cli"
> rev="1.1" conf="COMPILE,RUNTIME,TEST->default">
> <artifact name="commons-cli" type="jar"/>
> <artifact name="commons-cli" type="source" ext="zip"
> conf="COMPILE" />
> </dependency>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
