[jira] Commented: (IVYDE-121) IVYDE classpath container should support bundle types by default
[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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] Commented: (IVYDE-121) IVYDE classpath container should support bundle types by default
[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 should support bundle types by default
[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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] Commented: (IVYDE-121) IVYDE classpath container should support bundle types by default
[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
