Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <24791116.107541289912715069.JavaMail.jira@thor>
Date: Tue, 16 Nov 2010 08:05:15 -0500 (EST)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (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
In-Reply-To: <25140787.58731289637853205.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/IVYDE-265?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12932=
449#action_12932449 ]=20

Nicolas Lalev=C3=A9e 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 wha=
t we can do manually, a software compute and doesn't think. So unless we fi=
nd the algoithm to make IvyDE find the proper mapping, there is no way it c=
an read our mind ;)


> Ivy DE does not associate source artifacts with extensions other than '.z=
ip' to associated binaries & it also does not associate source artifacts wi=
th 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 t=
he following cases:
> 1. when the source artifact has an extension other than '.zip' : e.g. com=
mons-lang-2.5, which has a source extension of '.jar'. Many artifacts follo=
w this convention - so this is quite an irritant, having to rename artifact=
s just because IvyDE can not associate them correctly.
> 2. when the source artifact has a different name than the binary - e.g. i=
n the case of JUnit, where JUnit delivers junit-2.8.2-src.jar, which is com=
mon for 2 binary artifacts: junit-2.8.2.jar and junit-2.8.2-dep.jar. The so=
urce jar is a superset, covering both binaries. So, while this case is unus=
ual, IvyDE should support associating super-set source artifacts to binarie=
s with potentially different names within Eclipse.
> Note that both are possible manually in Eclipse (without IvyDE). Therefor=
e these cases should be covered by IvyDE transparently to the user.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.