ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik-Berndt Scheper (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (IVYDE-121) IVYDE classpath container should support bundle types by default
Date Wed, 24 Sep 2008 09:57:44 GMT

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

fbascheper edited comment on IVYDE-121 at 9/24/08 2:57 AM:
--------------------------------------------------------------------

Well, I wouldn't like to have the javadoc and source types included in the classpath container.

What might be an option is by default to include anything else than the types configured as
source/javadoc types.
I.e something like a checkbox with label "Include all other types" 
If this checkbox is enabled, then the input box where the user can enter the accepted types
should be disabled 
If this checkbox is disabled, then the input box where the user can enter the accepted types
should be enabled (with jar, bundle as default).

      was (Author: fbascheper):
    Well, I wouldn't like to have the javadoc and source types included in the classpath container.

What might be an option is by default to include anything else than the types configured as
source/javadoc types.
I.e something like a checkbox with label "Include other all types" 
If this checkbox is enabled, then the input box where the user can enter the accepted types
should be disabled 
If this checkbox is disabled, then the input box where the user can enter the accepted types
should be enabled (with jar, bundle as default).
  
> 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
>            Assignee: Nicolas Lalevée
>             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.


Mime
View raw message