ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerard Fernandes (JIRA)" <j...@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
Date Tue, 16 Nov 2010 20:28:13 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932642#action_12932642
] 

Gerard Fernandes 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 ?

This was what I thought as well. But I'm very sure. I tried this with the jakarta commons-lang
jars as downloaded from the commons-lang site. The jars follow the convention:
binary: commons-lang-[VERSION].jar
source: commons-lang-[VERSION]-sources.jar
javadoc: commons-lang-[VERSION]-javadoc.jar

I've configured (via ivysettings.xml) src, sources, and source as source artifact qualifiers.
With the default source package as downloaded from commons-lang, IvyDE failed to associate
the source jar artifact to the binary jar artifact. Although there were no errors reported
on resolution. Simply changing the source artifact extension to '.zip' made Eclipse recognise
the sources.

I tried this a couple of times to confirm.

>>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 ?

Yes - this looks like it will solve most common cases. In special cases, however, the approach
advocated by you is more robust (special meta-data to tell IvyDE which artifact to use as
source/javadoc artifacts). It would be nice if IvyDE were to eventually provide attribute
level metadata on the <artifact> element to allow associating source and javadoc with
the binary in the same element declaration (rather than separate ones for source and javadoc,
in which case it becomes difficult for IvyDE to know which artifact to associate to which
binary).

> 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.


Mime
View raw message