[
https://issues.apache.org/jira/browse/IVYDE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932449#action_12932449
]
Nicolas Lalevée commented on IVYDE-265:
---------------------------------------
1. IvyDE actually doesn't care at all about the extension of the file. Are you
sure the extension is the issue ? What are the type and the name of the "jar"
and the "source" artifacts ?
2. With IVYDE-230, it will be possible in IvyDE 2.2 to make IvyDE consider the
only source jar available the source of every binary artifact. It seems it will
fit your use case, doesn't it ?
On the note, it is always difficult to make a software do automatically what we
can do manually, a software compute and doesn't think. So unless we find the
algoithm to make IvyDE find the proper mapping, there is no way it can read our
mind ;)
> 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.
