[IVYDE-265] 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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 2.1.0
• Component/s: classpath container

Environment

Eclipse IDE (J2EE version) 3.6 (Helios)

• Assignee: Unassigned
• Reporter: Gerard Fernandes
• Created: 13/Nov/10 08:43
• Updated: 02/Feb/12 20:30
• Resolved: 02/Feb/12 20:30

Description

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.