You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Erik-Berndt Scheper (JIRA)" <ji...@apache.org> on 2008/09/23 09:36:44 UTC
[jira] Created: (IVYDE-121) IVYDE classpath container does not
support bundle types
IVYDE classpath container does not support bundle types
-------------------------------------------------------
Key: IVYDE-121
URL: https://issues.apache.org/jira/browse/IVYDE-121
Project: IvyDE
Issue Type: Bug
Components: classpath container
Affects Versions: 2.0.0.alpha1
Reporter: Erik-Berndt Scheper
Fix For: 2.0
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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Erik-Berndt Scheper (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634387#action_12634387 ]
Erik-Berndt Scheper commented on IVYDE-121:
-------------------------------------------
I agree, but then we must think of a way to express that in the UI, that is not over complicated.
I've suggested an option above, but maybe you have a better idea?
> 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.
[jira] Resolved: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved IVYDE-121.
-----------------------------------
Resolution: Fixed
Assignee: Nicolas Lalevée
Now the default is "jar,bundle".
> 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Erik-Berndt Scheper (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634146#action_12634146 ]
Erik-Berndt Scheper commented on IVYDE-121:
-------------------------------------------
That should do for the moment, I believe.
Maybe it's a good idea to add some documentation comment to the Pom parser in ivy, that if extra types are added there, that they should be added to ivyde as well.
> 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634295#action_12634295 ]
Maarten Coene commented on IVYDE-121:
-------------------------------------
It will still be the cause of problems when you have defined additional types in your own ivy.xml files.
In one of my previous jobs, we had defined some extra types and it was this setting that caused a lot of problems with the usage of IvyDE, especially when new types were added.
> 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634117#action_12634117 ]
Maarten Coene commented on IVYDE-121:
-------------------------------------
You should also include the other types from maven2 that have "jar" extension. (See the Ivy pom parser code for a list of these types)
Maybe you could by default accept all types, but only add the files with a ".jar" extension to the classpath?
> 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634084#action_12634084 ]
Nicolas Lalevée commented on IVYDE-121:
---------------------------------------
Because type like "source" or "javadoc" should not be added to the classpath but only _attached_ to the actual "jar" or "bundle".
> 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634114#action_12634114 ]
Nicolas Lalevée commented on IVYDE-121:
---------------------------------------
The current UI allow you to specify as many type as you want, there is no feature missing here. What you are suggesting is about a use case where there will be so many different kind of type that have to be included to the classpath that the "accept" logic should be reverse: we would need an excluding a list more than an accepting a list.
But I don't know such use case. So it seems to me a useless complication of the UI.
> 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container does not
support bundle types
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633698#action_12633698 ]
Nicolas Lalevée commented on IVYDE-121:
---------------------------------------
Have you tried to add "bundle" to the list of "Accepted types" ?
Look into the [advanced tab|http://ant.apache.org/ivy/ivyde/history/latest-milestone/images/cp_advanced_conf.jpg] or the [global configuration|http://ant.apache.org/ivy/ivyde/history/latest-milestone/index.html#pref], and change the "Accepted types" field so you have something like "jar,bundle".
> IVYDE classpath container does not support bundle types
> -------------------------------------------------------
>
> Key: IVYDE-121
> URL: https://issues.apache.org/jira/browse/IVYDE-121
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Affects Versions: 2.0.0.alpha1
> Reporter: Erik-Berndt Scheper
> Fix For: 2.0
>
>
> 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.
[jira] Issue Comment Edited: (IVYDE-121) IVYDE classpath container
should support bundle types by default
Posted by "Erik-Berndt Scheper (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Issue Comment Edited: (IVYDE-121) IVYDE classpath container
should support bundle types by default
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634133#action_12634133 ]
hibou edited comment on IVYDE-121 at 9/24/08 6:22 AM:
----------------------------------------------------------------
We cannot accept every type with a .jar extension, because it will include sources and javadocs (at least for the default maven repositories).
I have looked to the pom parser, I have found two other types ("ejb" and "maven-plugin"), and I have added them to the default conf.
was (Author: hibou):
We cannot accepet every type with a .jar extension, because it will include sources and javadocs for maven repositories.
I have look to the pom parser, I have found two other types ("ejb" and "maven-plugin"), and I have added them to the default conf.
> 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634133#action_12634133 ]
Nicolas Lalevée commented on IVYDE-121:
---------------------------------------
We cannot accepet every type with a .jar extension, because it will include sources and javadocs for maven repositories.
I have look to the pom parser, I have found two other types ("ejb" and "maven-plugin"), and I have added them to the default conf.
> 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.
[jira] Updated: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Erik-Berndt Scheper (JIRA)" <ji...@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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634077#action_12634077 ]
Maarten Coene commented on IVYDE-121:
-------------------------------------
Why not accept all types by 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.
[jira] Commented: (IVYDE-121) IVYDE classpath container should
support bundle types by default
Posted by "Erik-Berndt Scheper (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634086#action_12634086 ]
Erik-Berndt Scheper commented on IVYDE-121:
-------------------------------------------
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.