Ivy DE does not associate source artifacts with extensions other than '.zip' to
associated binaries & it also does not associate source artifacts with names
other than the binary artifacts, in Eclipse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: IVYDE-265
URL: https://issues.apache.org/jira/browse/IVYDE-265
Project: IvyDE
Issue Type: Bug
Components: classpath container
Affects Versions: 2.1.0
Environment: Eclipse IDE (J2EE version) 3.6 (Helios)
Reporter: Gerard Fernandes
Priority: Minor
IvyDE does not associate source artifacts to binaries within Eclipse in the
following cases:
1. when the source artifact has an extension other than '.zip' : e.g.
commons-lang-2.5, which has a source extension of '.jar'. Many artifacts follow
this convention - so this is quite an irritant, having to rename artifacts just
because IvyDE can not associate them correctly.
2. when the source artifact has a different name than the binary - e.g. in the
case of JUnit, where JUnit delivers junit-2.8.2-src.jar, which is common for 2
binary artifacts: junit-2.8.2.jar and junit-2.8.2-dep.jar. The source jar is a
superset, covering both binaries. So, while this case is unusual, IvyDE should
support associating super-set source artifacts to binaries with potentially
different names within Eclipse.
Note that both are possible manually in Eclipse (without IvyDE). Therefore
these cases should be covered by IvyDE transparently to the user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
