[
https://issues.apache.org/jira/browse/IVYDE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551740
]
Gerard Fernandes commented on IVYDE-66:
---------------------------------------
In my opinion, it is very important that the "-src" part be acceptable and
recognised by IvyDE. If one has to workaround by:
1- changing the source artifact name
2- adding "-src" in ivysettings
One runs the risk of Ivy resolving source artifacts instead of binaries.
E.g. Try having cglib 2.1_03 and commons-cli and configuring Ivy with the cglib
binary only and commons-cli with binary and source artifacts by working around
in the ivysettings. The cglib artifact attached is the source artifact! Of
course Eclipse compilation breaks.
Try with the ivysettings as you've mentioned below and Ivy configuration:
<dependency org="cglib" name="cglib" rev="2.1_03"
conf="COMPILE,RUNTIME,TEST->default"/>
<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 kind of workaround also affects Ivy and breaks the ant build as well! This
means my CruiseControl build is no longer working because of the workaround in
ivysettings and the above configuration to accommodate IvyDE for attaching
sources in Eclipse.
> 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.
