Return-Path: 
 <notifications-return-4837-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@locus.apache.org
Received: (qmail 10092 invoked from network); 23 Sep 2008 13:28:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 Sep 2008 13:28:44 -0000
Received: (qmail 22701 invoked by uid 500); 23 Sep 2008 13:28:41 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 22651 invoked by uid 500); 23 Sep 2008 13:28:41 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 22451 invoked by uid 99); 23 Sep 2008 13:28:41 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 06:28:41 -0700
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 13:27:41 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 9631B234C1E4
	for <notifications@ant.apache.org>; Tue, 23 Sep 2008 06:27:44 -0700 (PDT)
Message-ID: <991171743.1222176464614.JavaMail.jira@brutus>
Date: Tue, 23 Sep 2008 06:27:44 -0700 (PDT)
From: "Erik-Berndt Scheper (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Updated: (IVYDE-121) IVYDE classpath container should
 support bundle types by default
In-Reply-To: <1105156734.1222155404184.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erik-Berndt Scheper updated IVYDE-121:
--------------------------------------

    Description: 
By default, the ivy classpath container does not support bundle types as jar files. 
These are generated automatically by Ivy 2.0 RC1 (and higher) when importing maven POMs to an ivy repository.

Sample based on http://repo1.maven.org/maven2/org/springframework/ws/spring-oxm-tiger/1.5.4/spring-oxm-tiger-1.5.4.pom

{code:xml}
<publications>
<artifact name="spring-oxm-tiger" type="bundle" ext="jar" conf="master"/>
<artifact name="spring-oxm-tiger" type="source" ext="jar" conf="sources" m:classifier="sources"/>
<artifact name="spring-oxm-tiger" type="javadoc" ext="jar" conf="javadoc" m:classifier="javadoc"/>
</publications>
{code}

The result is that the jar file is resolved from the ivy file, but not shown in the classpath container.


  was:
The ivy classpath container does not support bundle types as jar files. 
These are generated automatically by Ivy 2.0 RC1 (and higher) when importing maven POMs to an ivy repository.

Sample based on http://repo1.maven.org/maven2/org/springframework/ws/spring-oxm-tiger/1.5.4/spring-oxm-tiger-1.5.4.pom

{code:xml}
<publications>
<artifact name="spring-oxm-tiger" type="bundle" ext="jar" conf="master"/>
<artifact name="spring-oxm-tiger" type="source" ext="jar" conf="sources" m:classifier="sources"/>
<artifact name="spring-oxm-tiger" type="javadoc" ext="jar" conf="javadoc" m:classifier="javadoc"/>
</publications>
{code}

The result is that the jar file is resolved from the ivy file, but not shown in the classpath container.


     Issue Type: Wish  (was: Bug)
        Summary: IVYDE classpath container should support bundle types by default  (was: IVYDE classpath container does not support bundle types)

You are right, by setting 

{code}Accepted types = jar,bundle{code}

in the ivy preferences, bundle files are shown in the classpath container.

I've edited this issue to a 'wish' instead of a bug. 

I believe bundle files should be shown by default in the classpath container. The reason is that we will most likely see many more bundles in the future, with the increased popularity of OSGi. 


> IVYDE classpath container should support bundle types by default
> ----------------------------------------------------------------
>
>                 Key: IVYDE-121
>                 URL: https://issues.apache.org/jira/browse/IVYDE-121
>             Project: IvyDE
>          Issue Type: Wish
>          Components: classpath container
>    Affects Versions: 2.0.0.alpha1
>            Reporter: Erik-Berndt Scheper
>             Fix For: 2.0
>
>
> By default, the ivy classpath container does not support bundle types as jar files. 
> These are generated automatically by Ivy 2.0 RC1 (and higher) when importing maven POMs to an ivy repository.
> Sample based on http://repo1.maven.org/maven2/org/springframework/ws/spring-oxm-tiger/1.5.4/spring-oxm-tiger-1.5.4.pom
> {code:xml}
> <publications>
> <artifact name="spring-oxm-tiger" type="bundle" ext="jar" conf="master"/>
> <artifact name="spring-oxm-tiger" type="source" ext="jar" conf="sources" m:classifier="sources"/>
> <artifact name="spring-oxm-tiger" type="javadoc" ext="jar" conf="javadoc" m:classifier="javadoc"/>
> </publications>
> {code}
> The result is that the jar file is resolved from the ivy file, but not shown in the classpath container.

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