[jira] [Commented] (IVY-1607) Apache IVYDE 2.5.0.cr1 does not resolve correctly.

2019-09-07 Thread jaikiran pai (Jira)


[ 
https://issues.apache.org/jira/browse/IVY-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924927#comment-16924927
 ] 

jaikiran pai commented on IVY-1607:
---

I don't have Eclipse at hand, but this issue is most likely caused by IVY-1580 
which, incidentally, I fixed just a few hours back. I plan to do a release of 
Ivy soon, assuming there are no other blockers. Once that is done, it should 
get picked up by IvyDE (I think).

> Apache IVYDE 2.5.0.cr1 does not resolve correctly.
> --
>
> Key: IVY-1607
> URL: https://issues.apache.org/jira/browse/IVY-1607
> Project: Ivy
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.5.0-rc1
>Reporter: Michael Breu
>Priority: Major
> Attachments: Ivy2.5.0.5rcTests.zip
>
>
> Sorry, to cross post the issue IVYDE-391 here, however the IVYDE project does 
> not seem to react on this issue in Apache Ivy 2.5.0.cr1_20180412005305 (and 
> even has no reference to version 2.5.0.cr1), and I'm not sure, whether the 
> problem is rooted in in 2.5.0-rc1 .
> On https://www.apache.org/dist/ant/ivyde/updatesite/ the apache Ivy library 
> "Apache Ivy 2.5.0.cr1_20180412005305" is provided, and it seems that this is 
> now installed as default, because it is the newest version. (BTW: it seems 
> that it is published as *cr* (change request?), not as *rc* (release 
> candidate?))
>  
> However: It does not resolve certain dependencies correclty. E.g
> {{ {{version="2.1" }}
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;
> >
>  organisation="Ivy Test"
> module="Ivy250rcTest"
> status="integration">
> 
> 
> 
> 
> 
> 
> 
> 
>  rev="2.12.0" conf="*->runtime"/>
> 
>  rev="2.12.0" conf="*->default"/>
> 
>  rev="2.12.0" conf="*->default"/>
> 
> 
> 
> does not resolve log4j-core.jar, although included.
>  
> Find enclosed a simple eclipse project that demonstrates this issue.
>  
> If you can reproduce this problem, please withdraw version IVYDE 2.5.0.cr... 
> . It spoils every installation and it seems very hard to reset to a previous 
> version.
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (IVY-1607) Apache IVYDE 2.5.0.cr1 does not resolve correctly.

2019-09-07 Thread Michael Breu (Jira)
Michael Breu created IVY-1607:
-

 Summary: Apache IVYDE 2.5.0.cr1 does not resolve correctly.
 Key: IVY-1607
 URL: https://issues.apache.org/jira/browse/IVY-1607
 Project: Ivy
  Issue Type: Bug
  Components: Core
Affects Versions: 2.5.0-rc1
Reporter: Michael Breu
 Attachments: Ivy2.5.0.5rcTests.zip

Sorry, to cross post the issue IVYDE-391 here, however the IVYDE project does 
not seem to react on this issue in Apache Ivy 2.5.0.cr1_20180412005305 (and 
even has no reference to version 2.5.0.cr1), and I'm not sure, whether the 
problem is rooted in in 2.5.0-rc1 .

On https://www.apache.org/dist/ant/ivyde/updatesite/ the apache Ivy library 
"Apache Ivy 2.5.0.cr1_20180412005305" is provided, and it seems that this is 
now installed as default, because it is the newest version. (BTW: it seems that 
it is published as *cr* (change request?), not as *rc* (release candidate?))

 
However: It does not resolve certain dependencies correclty. E.g

{{http://www.w3.org/2001/XMLSchema-instance;
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;
>


















does not resolve log4j-core.jar, although included.

 

Find enclosed a simple eclipse project that demonstrates this issue.

 

If you can reproduce this problem, please withdraw version IVYDE 2.5.0.cr... . 
It spoils every installation and it seems very hard to reset to a previous 
version.

 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (IVY-1582) OutOfMemory during ANT deploy task

2019-09-07 Thread jaikiran pai (Jira)


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

jaikiran pai reassigned IVY-1582:
-

Assignee: jaikiran pai

> OutOfMemory during ANT deploy task
> --
>
> Key: IVY-1582
> URL: https://issues.apache.org/jira/browse/IVY-1582
> Project: Ivy
>  Issue Type: Bug
>  Components: Ant
>Affects Versions: 2.5.0-rc1
>Reporter: Sebastian Götz
>Assignee: jaikiran pai
>Priority: Minor
>
> I recently came to test the 2.5.0-rc1 to find out if it could cure a problem 
> with preemptive authentication during deploy.
> For this I simply replaced the 2.4.0 jar-file with the 2.5.0-rc1 and 
> restarted the build server. The rest of the configuration remained untouched:
>  * Jenkins 2.107.3
>  * Apache ANT 1.8.3
>  * Oracle JDK 1.8.0_111 (x86)
>  * Windows 10
> During the deploy of the build artifact of subproject the upload failed with 
> an out of memory exception:
> java.lang.OutOfMemoryError: Java heap space
>   at java.util.Arrays.copyOf(Arrays.java:3236)
>   at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
>   at 
> java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
>   at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
>   at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:78)
>   at org.apache.ivy.util.FileUtil.copy(FileUtil.java:255)
>   at org.apache.ivy.util.FileUtil.copy(FileUtil.java:234)
>   at 
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:315)
>   at 
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:168)
>   at org.apache.ivy.util.FileUtil.copy(FileUtil.java:219)
>   at 
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:88)
>   at 
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:146)
>   at 
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:236)
>   at 
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:217)
>   at 
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:275)
>   at 
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:254)
>   at 
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:177)
>   at org.apache.ivy.Ivy.publish(Ivy.java:622)
>   at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:316)
>   at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>   at org.apache.tools.ant.Task.perform(Task.java:348)
>   at org.apache.tools.ant.Target.execute(Target.java:392)
>   at org.apache.tools.ant.Target.performTasks(Target.java:413)
>   at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>   at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>   at 
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>   at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
> From the Jenkins configuration I cannot see that any memory flags are passed 
> to the ANT call. So I guess the default memory constraints apply.
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Work started] (IVY-1582) OutOfMemory during ANT deploy task

2019-09-07 Thread jaikiran pai (Jira)


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

Work on IVY-1582 started by jaikiran pai.
-
> OutOfMemory during ANT deploy task
> --
>
> Key: IVY-1582
> URL: https://issues.apache.org/jira/browse/IVY-1582
> Project: Ivy
>  Issue Type: Bug
>  Components: Ant
>Affects Versions: 2.5.0-rc1
>Reporter: Sebastian Götz
>Assignee: jaikiran pai
>Priority: Minor
>
> I recently came to test the 2.5.0-rc1 to find out if it could cure a problem 
> with preemptive authentication during deploy.
> For this I simply replaced the 2.4.0 jar-file with the 2.5.0-rc1 and 
> restarted the build server. The rest of the configuration remained untouched:
>  * Jenkins 2.107.3
>  * Apache ANT 1.8.3
>  * Oracle JDK 1.8.0_111 (x86)
>  * Windows 10
> During the deploy of the build artifact of subproject the upload failed with 
> an out of memory exception:
> java.lang.OutOfMemoryError: Java heap space
>   at java.util.Arrays.copyOf(Arrays.java:3236)
>   at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
>   at 
> java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
>   at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
>   at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:78)
>   at org.apache.ivy.util.FileUtil.copy(FileUtil.java:255)
>   at org.apache.ivy.util.FileUtil.copy(FileUtil.java:234)
>   at 
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:315)
>   at 
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:168)
>   at org.apache.ivy.util.FileUtil.copy(FileUtil.java:219)
>   at 
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:88)
>   at 
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:146)
>   at 
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:236)
>   at 
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:217)
>   at 
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:275)
>   at 
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:254)
>   at 
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:177)
>   at org.apache.ivy.Ivy.publish(Ivy.java:622)
>   at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:316)
>   at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>   at org.apache.tools.ant.Task.perform(Task.java:348)
>   at org.apache.tools.ant.Target.execute(Target.java:392)
>   at org.apache.tools.ant.Target.performTasks(Target.java:413)
>   at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>   at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>   at 
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>   at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
> From the Jenkins configuration I cannot see that any memory flags are passed 
> to the ANT call. So I guess the default memory constraints apply.
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IVY-1587) Wrong POM translation for dependencies appearing more than once

2019-09-07 Thread jaikiran pai (Jira)


[ 
https://issues.apache.org/jira/browse/IVY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924883#comment-16924883
 ] 

jaikiran pai commented on IVY-1587:
---

I just tried this locally with 2.5.0-rc1, I see 2 artifacts:

{code}
java -jar ivy-2.5.0-rc1.jar -cache ./cache -dependency "org.slf4j" 
"slf4j-log4j12" "1.7.25" -confs default -types jar -retrieve 
lib/[originalname](-[type]).[ext]
{code}

and it resolved and retrieved both the jars:

{code}
:: resolving dependencies :: org.slf4j#slf4j-log4j12-caller;working
confs: [default]
found org.slf4j#slf4j-log4j12;1.7.25 in public
found org.slf4j#slf4j-api;1.7.25 in public
found log4j#log4j;1.2.17 in public
downloading 
https://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.7.25/slf4j-log4j12-1.7.25.jar
 ...
.. (11kB)
.. (0kB)
[SUCCESSFUL ] org.slf4j#slf4j-log4j12;1.7.25!slf4j-log4j12.jar (916ms)
downloading 
https://repo1.maven.org/maven2/org/slf4j/slf4j-api/1.7.25/slf4j-api-1.7.25.jar 
...
.. (40kB)
.. (0kB)
[SUCCESSFUL ] org.slf4j#slf4j-api;1.7.25!slf4j-api.jar (1093ms)
:: resolution report :: resolve 9064ms :: artifacts dl 2016ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  default |   3   |   3   |   3   |   0   ||   2   |   2   |
-
:: retrieving :: org.slf4j#slf4j-log4j12-caller
confs: [default]
2 artifacts copied, 0 already retrieved (52kB/7ms)
{code}

Here's the contents of the retrieved lib directory:
{code}
> ls lib
slf4j-api-1.7.25-jar.jarslf4j-log4j12-1.7.25-jar.jar
{code}

> Wrong POM translation for dependencies appearing more than once
> ---
>
> Key: IVY-1587
> URL: https://issues.apache.org/jira/browse/IVY-1587
> Project: Ivy
>  Issue Type: Bug
>Affects Versions: 2.5.0-rc1
>Reporter: Cédric Damioli
>Priority: Major
>
> Using 
>  
> {code:java}
> java -jar ivy.jar -dependency "org.slf4j" "slf4j-log4j12" "1.7.25" -confs 
> default -types jar
> {code}
> With Ivy 2.4.0, I get two artifacts : slf4j-api.jar and slf4j-log4j12.jar
> With Ivy 2.5.0RC1, I only get {color:#33}slf4j-log4j12.jar with no means 
> to get the -api artifact {color}
>  
> This seems to be related to the resolution of IVY-1576
>  
> In the POM, the slf4j-api dependency is present twice, once for compile, once 
> for tests.
> Before IVY-1576, it resulted in two different dependencies.
> With IVY-1576, there's only one dependency, offering only the test artifact.
>  
> The fix was good for "merging" dependencies with classifiers, but in this 
> case, the merge should not have occured
>  
> I don't set this ticket as critical as there are workarounds, but it is at 
> least very annoying
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IVYDE-391) Apache IVY 2.5.0.cr1 does not resolve correctly.

2019-09-07 Thread Michael Breu (Jira)


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

Michael Breu updated IVYDE-391:
---
Environment: 
# I tested it with
# 
# Version: Oxygen.3a Release (4.7.3a) [but I also reproduced it in recent 
Eclipse 2019 06]
# 
# *** Features:
# org.apache.ivyde.feature (2.3.1.201703031747) "Apache IvyDE"
# 
# org.apache.ivy (2.5.0.cr1_20180412005306) "Ivy" [Resolved]
# org.apache.ivy.eclipse.ant (2.5.0.cr1_20180412005306) "Apache Ivy Ant Plugin" 
[Resolved]
# org.apache.ivyde.eclipse (2.3.1.201703031747) "Apache IvyDE" [Active]
# org.apache.ivyde.eclipse.resolvevisualizer (2.3.0.201703031747) "Apache IvyDE 
Resolve
# 
# *** User Preferences:
# #Fri Aug 02 18:55:42 CEST 2019
# \!/=
# 
/bundle_defaults/org.apache.ivyde.eclipse/acceptedTypes=jar,bundle,ejb,maven-plugin
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.change=true
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.close=true
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.open=false
# /bundle_defaults/org.apache.ivyde.eclipse/booleanPreference=true
# /bundle_defaults/org.apache.ivyde.eclipse/choicePreference=choice2
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.default=0,0,0
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.procInstr=128,128,128
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.string=0,128,0
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.tag=0,0,128
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.xmlComment=128,0,0
# /bundle_defaults/org.apache.ivyde.eclipse/error.popup=true
# /bundle_defaults/org.apache.ivyde.eclipse/ivuUserDir=
# /bundle_defaults/org.apache.ivyde.eclipse/ivyConsole.ivyDELogLevel=2
# /bundle_defaults/org.apache.ivyde.eclipse/ivyConsole.logLevel=2
# /bundle_defaults/org.apache.ivyde.eclipse/ivyConsole.openOnStartup=false
# /bundle_defaults/org.apache.ivyde.eclipse/ivy_conf_path=
# /bundle_defaults/org.apache.ivyde.eclipse/ivy_org=
# /bundle_defaults/org.apache.ivyde.eclipse/ivy_org_url=
# 
/bundle_defaults/org.apache.ivyde.eclipse/javadocSuffixes=-javadoc,-javadocs,-doc,-docs
# /bundle_defaults/org.apache.ivyde.eclipse/javadocTypes=javadoc
# /bundle_defaults/org.apache.ivyde.eclipse/loadSettingsOnDemand=false
# /bundle_defaults/org.apache.ivyde.eclipse/mapIfOnlyOneJavadoc=false
# /bundle_defaults/org.apache.ivyde.eclipse/mapIfOnlyOneSource=false
# /bundle_defaults/org.apache.ivyde.eclipse/offline=false
# /bundle_defaults/org.apache.ivyde.eclipse/order.alphabetical=false
# /bundle_defaults/org.apache.ivyde.eclipse/propertyFiles=
# /bundle_defaults/org.apache.ivyde.eclipse/readOSGIMetadata=false
# /bundle_defaults/org.apache.ivyde.eclipse/resolveBeforeLaunch=false
# /bundle_defaults/org.apache.ivyde.eclipse/resolveInWorkspace=false
# /bundle_defaults/org.apache.ivyde.eclipse/resolveOnStartup=0
# /bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath=false
# 
/bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath.pattern=lib/[artifact]-[revision].[ext]
# /bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath.sync=false
# /bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath.types=jar
# /bundle_defaults/org.apache.ivyde.eclipse/sourceSuffixes=-source,-sources,-src
# /bundle_defaults/org.apache.ivyde.eclipse/sourceTypes=source
# /bundle_defaults/org.apache.ivyde.eclipse/stringPreference=Default value
# /bundle_defaults/org.apache.ivyde.eclipse/transitiveResolve=true
# /bundle_defaults/org.apache.ivyde.eclipse/workspaceResolver.ignoreBranch=false
# 
/bundle_defaults/org.apache.ivyde.eclipse/workspaceResolver.ignoreVersion=false
# 
#  

  was:
# I tested it with
# 
# Version: Oxygen.3a Release (4.7.3a) [but a also reproduced it in recent 
Eclipse 2019 06]
# 
# *** Features:
# org.apache.ivyde.feature (2.3.1.201703031747) "Apache IvyDE"
# 
# org.apache.ivy (2.5.0.cr1_20180412005306) "Ivy" [Resolved]
# org.apache.ivy.eclipse.ant (2.5.0.cr1_20180412005306) "Apache Ivy Ant Plugin" 
[Resolved]
# org.apache.ivyde.eclipse (2.3.1.201703031747) "Apache IvyDE" [Active]
# org.apache.ivyde.eclipse.resolvevisualizer (2.3.0.201703031747) "Apache IvyDE 
Resolve
# 
# *** User Preferences:
# #Fri Aug 02 18:55:42 CEST 2019
# \!/=
# 
/bundle_defaults/org.apache.ivyde.eclipse/acceptedTypes=jar,bundle,ejb,maven-plugin
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.change=true
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.close=true
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.open=false
# /bundle_defaults/org.apache.ivyde.eclipse/booleanPreference=true
# /bundle_defaults/org.apache.ivyde.eclipse/choicePreference=choice2
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.default=0,0,0
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.procInstr=128,128,128
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.string=0,128,0
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.tag=0,0,128
# 

[jira] [Updated] (IVYDE-391) Apache IVY 2.5.0.cr1 does not resolve correctly.

2019-09-07 Thread Michael Breu (Jira)


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

Michael Breu updated IVYDE-391:
---
Environment: 
# I tested it with
# 
# Version: Oxygen.3a Release (4.7.3a) [but a also reproduced it in recent 
Eclipse 2019 06]
# 
# *** Features:
# org.apache.ivyde.feature (2.3.1.201703031747) "Apache IvyDE"
# 
# org.apache.ivy (2.5.0.cr1_20180412005306) "Ivy" [Resolved]
# org.apache.ivy.eclipse.ant (2.5.0.cr1_20180412005306) "Apache Ivy Ant Plugin" 
[Resolved]
# org.apache.ivyde.eclipse (2.3.1.201703031747) "Apache IvyDE" [Active]
# org.apache.ivyde.eclipse.resolvevisualizer (2.3.0.201703031747) "Apache IvyDE 
Resolve
# 
# *** User Preferences:
# #Fri Aug 02 18:55:42 CEST 2019
# \!/=
# 
/bundle_defaults/org.apache.ivyde.eclipse/acceptedTypes=jar,bundle,ejb,maven-plugin
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.change=true
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.close=true
# /bundle_defaults/org.apache.ivyde.eclipse/autoResolve.open=false
# /bundle_defaults/org.apache.ivyde.eclipse/booleanPreference=true
# /bundle_defaults/org.apache.ivyde.eclipse/choicePreference=choice2
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.default=0,0,0
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.procInstr=128,128,128
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.string=0,128,0
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.tag=0,0,128
# /bundle_defaults/org.apache.ivyde.eclipse/editor.color.xmlComment=128,0,0
# /bundle_defaults/org.apache.ivyde.eclipse/error.popup=true
# /bundle_defaults/org.apache.ivyde.eclipse/ivuUserDir=
# /bundle_defaults/org.apache.ivyde.eclipse/ivyConsole.ivyDELogLevel=2
# /bundle_defaults/org.apache.ivyde.eclipse/ivyConsole.logLevel=2
# /bundle_defaults/org.apache.ivyde.eclipse/ivyConsole.openOnStartup=false
# /bundle_defaults/org.apache.ivyde.eclipse/ivy_conf_path=
# /bundle_defaults/org.apache.ivyde.eclipse/ivy_org=
# /bundle_defaults/org.apache.ivyde.eclipse/ivy_org_url=
# 
/bundle_defaults/org.apache.ivyde.eclipse/javadocSuffixes=-javadoc,-javadocs,-doc,-docs
# /bundle_defaults/org.apache.ivyde.eclipse/javadocTypes=javadoc
# /bundle_defaults/org.apache.ivyde.eclipse/loadSettingsOnDemand=false
# /bundle_defaults/org.apache.ivyde.eclipse/mapIfOnlyOneJavadoc=false
# /bundle_defaults/org.apache.ivyde.eclipse/mapIfOnlyOneSource=false
# /bundle_defaults/org.apache.ivyde.eclipse/offline=false
# /bundle_defaults/org.apache.ivyde.eclipse/order.alphabetical=false
# /bundle_defaults/org.apache.ivyde.eclipse/propertyFiles=
# /bundle_defaults/org.apache.ivyde.eclipse/readOSGIMetadata=false
# /bundle_defaults/org.apache.ivyde.eclipse/resolveBeforeLaunch=false
# /bundle_defaults/org.apache.ivyde.eclipse/resolveInWorkspace=false
# /bundle_defaults/org.apache.ivyde.eclipse/resolveOnStartup=0
# /bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath=false
# 
/bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath.pattern=lib/[artifact]-[revision].[ext]
# /bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath.sync=false
# /bundle_defaults/org.apache.ivyde.eclipse/retrievedClasspath.types=jar
# /bundle_defaults/org.apache.ivyde.eclipse/sourceSuffixes=-source,-sources,-src
# /bundle_defaults/org.apache.ivyde.eclipse/sourceTypes=source
# /bundle_defaults/org.apache.ivyde.eclipse/stringPreference=Default value
# /bundle_defaults/org.apache.ivyde.eclipse/transitiveResolve=true
# /bundle_defaults/org.apache.ivyde.eclipse/workspaceResolver.ignoreBranch=false
# 
/bundle_defaults/org.apache.ivyde.eclipse/workspaceResolver.ignoreVersion=false
# 
#  

  was:
I tested it with

Version: Oxygen.3a Release (4.7.3a) [but a also reproduced it in recent Eclipse 
2019 06]

*** Features:
org.apache.ivyde.feature (2.3.1.201703031747) "Apache IvyDE"

org.apache.ivy (2.5.0.cr1_20180412005306) "Ivy" [Resolved]
org.apache.ivy.eclipse.ant (2.5.0.cr1_20180412005306) "Apache Ivy Ant Plugin" 
[Resolved]
org.apache.ivyde.eclipse (2.3.1.201703031747) "Apache IvyDE" [Active]
org.apache.ivyde.eclipse.resolvevisualizer (2.3.0.201703031747) "Apache IvyDE 
Resolve

*** User Preferences:
#Fri Aug 02 18:55:42 CEST 2019
\!/=
/bundle_defaults/org.apache.ivyde.eclipse/acceptedTypes=jar,bundle,ejb,maven-plugin
/bundle_defaults/org.apache.ivyde.eclipse/autoResolve.change=true
/bundle_defaults/org.apache.ivyde.eclipse/autoResolve.close=true
/bundle_defaults/org.apache.ivyde.eclipse/autoResolve.open=false
/bundle_defaults/org.apache.ivyde.eclipse/booleanPreference=true
/bundle_defaults/org.apache.ivyde.eclipse/choicePreference=choice2
/bundle_defaults/org.apache.ivyde.eclipse/editor.color.default=0,0,0
/bundle_defaults/org.apache.ivyde.eclipse/editor.color.procInstr=128,128,128
/bundle_defaults/org.apache.ivyde.eclipse/editor.color.string=0,128,0
/bundle_defaults/org.apache.ivyde.eclipse/editor.color.tag=0,0,128

[jira] [Closed] (IVY-1604) Issue with Build when using IVY plugin

2019-09-07 Thread jaikiran pai (Jira)


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

jaikiran pai closed IVY-1604.
-
Resolution: Invalid

> Issue with Build when using IVY plugin
> --
>
> Key: IVY-1604
> URL: https://issues.apache.org/jira/browse/IVY-1604
> Project: Ivy
>  Issue Type: Bug
> Environment: Jenkins PROD instance
>Reporter: Nidhi Telang
>Priority: Major
> Attachments: Console output.txt
>
>
> One of our customers build is failing. Error message mentioned below. We have 
> checked some online article for this issue, but didn't get any proper 
> resolution. 
> Console output attached for your reference. 
> Ivy plugin - 1.22 version
> BUILD FAILED 
> Class org.jfrog.build.extractor.listener.ArtifactoryBuildListener could not 
> be loaded because of an invalid dependency.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (IVY-1586) Retrieves test-library instead of binary-library

2019-09-07 Thread jaikiran pai (Jira)


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

jaikiran pai resolved IVY-1586.
---
Resolution: Duplicate

> Retrieves test-library instead of binary-library
> 
>
> Key: IVY-1586
> URL: https://issues.apache.org/jira/browse/IVY-1586
> Project: Ivy
>  Issue Type: Bug
>  Components: Ant
>Affects Versions: 2.5.0-rc1
> Environment: Eclipse Photon 4.8.0 64bit
> Ant 1.10.3.v20180417-1627
> Apache IvyDE 2.2.0.final-201311091524-RELEASE
> Apache Ivy 2.5.0.cr1_20180412005306
>Reporter: Arni Schulze
>Assignee: jaikiran pai
>Priority: Blocker
> Attachments: Ant_1st_output.txt, Ant_2nd_output.txt, build.xml, 
> ivy.xml
>
>
> If I delete the local Ivy cache and run my Ant script to retrieve 
> "ch.quos.logback logback-classic 1.2.3" I get the correct library and its 
> dependencies (see Ant_1st_output).
> But if I run the Ant script again (now having a local Ivy cache) it retrieves 
> the test-library and the test-library of the dependencies instead of the 
> correct ones (see Ant_2nd_output).
> I added minimalistic ivy.xml and Ant script. Because of the different 
> behavior of the first and every other run, I think this is a bug in Ivy.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IVY-1586) Retrieves test-library instead of binary-library

2019-09-07 Thread jaikiran pai (Jira)


[ 
https://issues.apache.org/jira/browse/IVY-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924881#comment-16924881
 ] 

jaikiran pai commented on IVY-1586:
---

I just pushed a fix for IVY-1580. Please give our nightly build 
https://builds.apache.org/view/A/view/Ant/job/Ivy/lastSuccessfulBuild/artifact/ 
a try to verify if this solves your issue (be sure to use a clean Ivy cache 
before trying this newer version).

> Retrieves test-library instead of binary-library
> 
>
> Key: IVY-1586
> URL: https://issues.apache.org/jira/browse/IVY-1586
> Project: Ivy
>  Issue Type: Bug
>  Components: Ant
>Affects Versions: 2.5.0-rc1
> Environment: Eclipse Photon 4.8.0 64bit
> Ant 1.10.3.v20180417-1627
> Apache IvyDE 2.2.0.final-201311091524-RELEASE
> Apache Ivy 2.5.0.cr1_20180412005306
>Reporter: Arni Schulze
>Assignee: jaikiran pai
>Priority: Blocker
> Attachments: Ant_1st_output.txt, Ant_2nd_output.txt, build.xml, 
> ivy.xml
>
>
> If I delete the local Ivy cache and run my Ant script to retrieve 
> "ch.quos.logback logback-classic 1.2.3" I get the correct library and its 
> dependencies (see Ant_1st_output).
> But if I run the Ant script again (now having a local Ivy cache) it retrieves 
> the test-library and the test-library of the dependencies instead of the 
> correct ones (see Ant_2nd_output).
> I added minimalistic ivy.xml and Ant script. Because of the different 
> behavior of the first and every other run, I think this is a bug in Ivy.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (IVY-1580) Generated ivy.xml from pom with multiple dependencies with different classifier does not contain the main dependency

2019-09-07 Thread jaikiran pai (Jira)


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

jaikiran pai resolved IVY-1580.
---
Fix Version/s: master
   Resolution: Fixed

I have pushed a commit which contains a fix along with a test case for this 
issue. Please give it a try against our nightly build 
https://builds.apache.org/view/A/view/Ant/job/Ivy/lastSuccessfulBuild/artifact/ 
(do make sure that you try this against a clean Ivy cache).

> Generated ivy.xml from pom with multiple dependencies with different 
> classifier does not contain the main dependency
> 
>
> Key: IVY-1580
> URL: https://issues.apache.org/jira/browse/IVY-1580
> Project: Ivy
>  Issue Type: Bug
>  Components: Maven Compatibility
>Affects Versions: 2.5.0-rc1
>Reporter: Antoine Précigout
>Assignee: jaikiran pai
>Priority: Major
> Fix For: master
>
> Attachments: logback-classic-1.1.7-with-ivy-2.4.0.xml, 
> logback-classic-1.1.7-with-ivy-2.5.0-rc1.xml
>
>
> Hi,
> Sorry for the title, it's a bit difficult to summerize the problem...
> So, since we updated our Eclipse environment to Ivy 2.5.0-rc1 (available via 
> IvyDE), we encountered problems when resolving dependencies on our projects.
> Following a little investigation, it appear that the generated ivy.xml from 
> the pom.xml of some dependencies differs from the previous version.
> I think the slf4j-log4j12 package is a good exemple to illustrate my point :
> +Details :+
> {code:xml}
> 
>   org.slf4j
>   slf4j-log4j12
>   1.7.25
> 
> {code}
> Pom.xml :
> {code:xml}
> 
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
>   4.0.0
>   
> org.slf4j
> slf4j-parent
> 1.7.25
>   
>   slf4j-log4j12
>   jar
>   SLF4J LOG4J-12 Binding
>   SLF4J LOG4J-12 Binding
>   http://www.slf4j.org
>   
> 
>   org.slf4j
>   slf4j-api
> 
> 
>   log4j
>   log4j
> 
> 
>   org.slf4j
>   slf4j-api
>   test-jar
>   ${project.version}
>   test
> 
>   
> 
> {code}
> Generated Ivy.xml (dependency part) - 2.4.0
> {code:xml}
> 
> conf="compile->compile(*),master(*);runtime->runtime(*)"/>
> conf="test->runtime(*),master(*)">
>m:classifier="tests"/>
>
>[...]
> 
> {code}
> Two differents dependency entries :
>  - one for classic "jar"
>  - one for the type "test-jar".
> In another hand :
>  Generated Ivy.xml (dependency part) - 2.5.0-rc1
> {code:xml}
> 
> conf="compile->compile(*),master(*);runtime->runtime(*);test->runtime(*),master(*)">
>m:classifier="tests"/>
>
>[...]
> 
> {code}
> Only one dependency with artifact test-jar. 
>  As a result for some of our projects to only get the dependency test-jar...
> I think this is a bug, but maybe i did'nt understand a subtlety.
> PS : Is it link to the correction of IVY-1484 ?
> Thanks for your time :)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Jenkins build is back to normal : Ivy #816

2019-09-07 Thread Apache Jenkins Server
See 



Build failed in Jenkins: Ivy #815

2019-09-07 Thread Apache Jenkins Server
See 

Changes:

[jaikiran] IVY-1580 Resolve any implicit artifacts when one among multiple

--
Started by an SCM change
Running as hibou
[EnvInject] - Loading node environment variables.
Building remotely on H49 (ubuntu bionic) in workspace 

No credentials specified
Cloning the remote Git repository
Cloning repository https://gitbox.apache.org/repos/asf/ant-ivy.git
 > git init  # timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/ant-ivy.git
 > git --version # timeout=10
 > git fetch --tags --progress https://gitbox.apache.org/repos/asf/ant-ivy.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://gitbox.apache.org/repos/asf/ant-ivy.git 
 > # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url https://gitbox.apache.org/repos/asf/ant-ivy.git 
 > # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
 > git clean -fdx # timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/ant-ivy.git
 > git fetch --tags --progress https://gitbox.apache.org/repos/asf/ant-ivy.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision d714d9dffbaa2c91855297a7df1c5d9ddfe6d0b0 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d714d9dffbaa2c91855297a7df1c5d9ddfe6d0b0
Commit message: "IVY-1580 Resolve any implicit artifacts when one among 
multiple dependencies of the same module has an explicit artifact/includes 
declaration"
 > git rev-list --no-walk 3cdf4752ec2422c44caa536969569e23456416e6 # timeout=10
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
[Ivy] $ /bin/bash -xe /tmp/jenkins5436488723990681411.sh
+ cd 
+ wget http://www-eu.apache.org/dist/ant/binaries/apache-ant-1.9.13-bin.tar.gz
--2019-09-07 12:58:57--  
http://www-eu.apache.org/dist/ant/binaries/apache-ant-1.9.13-bin.tar.gz
Resolving www-eu.apache.org (www-eu.apache.org)... 2a01:4f9:2a:185f::2, 
95.216.24.32
Connecting to www-eu.apache.org (www-eu.apache.org)|2a01:4f9:2a:185f::2|:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2019-09-07 12:58:57 ERROR 404: Not Found.

Build step 'Execute shell' marked build as failure
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Archiving artifacts


[ant-ivy] branch master updated: IVY-1580 Resolve any implicit artifacts when one among multiple dependencies of the same module has an explicit artifact/includes declaration

2019-09-07 Thread jaikiran
This is an automated email from the ASF dual-hosted git repository.

jaikiran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant-ivy.git


The following commit(s) were added to refs/heads/master by this push:
 new d714d9d  IVY-1580 Resolve any implicit artifacts when one among 
multiple dependencies of the same module has an explicit artifact/includes 
declaration
d714d9d is described below

commit d714d9dffbaa2c91855297a7df1c5d9ddfe6d0b0
Author: Jaikiran Pai 
AuthorDate: Sat Sep 7 13:21:40 2019 +0530

IVY-1580 Resolve any implicit artifacts when one among multiple 
dependencies of the same module has an explicit artifact/includes declaration
---
 asciidoc/release-notes.adoc|   1 +
 .../org/apache/ivy/core/resolve/IvyNodeUsage.java  |  54 +++---
 .../org/apache/ivy/core/resolve/ResolveTest.java   |  79 +
 test/repositories/1/ivy-1580/ivy-1580.xml  |  27 +++
 .../1.2.3/1580-foo-api-1.2.3-tests.jar | Bin 0 -> 452 bytes
 .../1580-foo-api/1.2.3/1580-foo-api-1.2.3.jar  | Bin 0 -> 442 bytes
 .../1580-foo-api/1.2.3/1580-foo-api-1.2.3.pom  |  29 
 .../1.2.3/test-ivy-1580-foo-api-1.2.3.pom  |  29 
 .../1580-foo-impl/1.2.3/1580-foo-impl-1.2.3.jar| Bin 0 -> 444 bytes
 .../1580-foo-impl/1.2.3/1580-foo-impl-1.2.3.pom|  45 
 .../1580-foo-impl/1580-foo-impl-1.2.3.jar  |   1 +
 .../1580-foo-impl/test-ivy-1580-foo-impl-1.2.3.pom |  45 
 12 files changed, 300 insertions(+), 10 deletions(-)

diff --git a/asciidoc/release-notes.adoc b/asciidoc/release-notes.adoc
index 0fe816a..4f19284 100644
--- a/asciidoc/release-notes.adoc
+++ b/asciidoc/release-notes.adoc
@@ -87,6 +87,7 @@ For details about the following changes, check our JIRA 
install at link:https://
 - FIX: ModuleDescriptorMemoryCache didn't detect outdated entries when Ivy 
file was updated in the cache by another process
 - FIX: Store ArtifactOrigin's location as a URL
 - FIX: Retrieve task, with symlink enabled, would not create symlinks for 
artifacts in certain specific cases (jira:IVY-1594[])
+- FIX: Generated ivy.xml from pom with multiple dependencies with different 
classifier does not contain the main dependency (jira:IVY-1580[])
 
 
 - IMPROVEMENT: Throw an IllegalStateException when retrieving the 
resolutionCacheRoot on the DefaultResolutionCacheManager if the basedir (or 
IvySettings) is not set (jira:IVY-1482[])
diff --git a/src/java/org/apache/ivy/core/resolve/IvyNodeUsage.java 
b/src/java/org/apache/ivy/core/resolve/IvyNodeUsage.java
index 85a522b..f96beb9 100644
--- a/src/java/org/apache/ivy/core/resolve/IvyNodeUsage.java
+++ b/src/java/org/apache/ivy/core/resolve/IvyNodeUsage.java
@@ -24,10 +24,15 @@ import java.util.HashSet;
 import java.util.Map;
 import java.util.Set;
 
+import org.apache.ivy.core.module.descriptor.DefaultIncludeRule;
 import org.apache.ivy.core.module.descriptor.DependencyArtifactDescriptor;
 import org.apache.ivy.core.module.descriptor.DependencyDescriptor;
 import org.apache.ivy.core.module.descriptor.IncludeRule;
 import org.apache.ivy.core.module.descriptor.WorkspaceModuleDescriptor;
+import org.apache.ivy.core.module.id.ArtifactId;
+import org.apache.ivy.core.module.id.ModuleId;
+import org.apache.ivy.plugins.matcher.ExactPatternMatcher;
+import org.apache.ivy.plugins.matcher.PatternMatcher;
 
 /**
  * Class collecting usage data for an IvyNode.
@@ -233,20 +238,40 @@ public class IvyNodeUsage {
 return dependencyArtifacts;
 }
 
-protected Set getDependencyIncludesSet(String rootModuleConf) 
{
-Collection dependersInConf = dependers.get(rootModuleConf);
+protected Set getDependencyIncludesSet(final String 
rootModuleConf) {
+final Collection dependersInConf = 
dependers.get(rootModuleConf);
 if (dependersInConf == null) {
 return null;
 }
-Set dependencyIncludes = new HashSet<>();
-for (Depender depender : dependersInConf) {
-IncludeRule[] rules = 
depender.dd.getIncludeRules(depender.dependerConf);
-if (rules == null || rules.length == 0) {
-// no include rule in at least one depender -> we must include 
everything,
-// and so return no include rule at all
-return null;
+final Set dependencyIncludes = new HashSet<>();
+// true if the depedency descriptor of any of the depender *doesn't* 
have an explicit
+// "" or an "". false otherwise
+boolean atLeastOneDependerNeedsAllArtifacts = false;
+// true if the dependency descriptor of any of the depender either has 
an explicit ""
+// or an "". false otherwise
+boolean atLeastOneDependerHasSpecificArtifactSelection = false;
+for (final Depender depender : dependersInConf) {
+final DependencyArtifactDescriptor dads[] = 

[jira] [Commented] (IVY-1584) 'ivy:resolve' fails on spring-boot-starter

2019-09-07 Thread jaikiran pai (Jira)


[ 
https://issues.apache.org/jira/browse/IVY-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924847#comment-16924847
 ] 

jaikiran pai commented on IVY-1584:
---

This looks like an issue with Spring dependencies itself. 1.5.9.RELEASE of 
org.springframework.boot:spring-boot-autoconfigure:1.5.9.RELEASE pom.xml has 
this:
```
...

org.springframework.boot
spring-boot
test-jar
test

```
So it requires a tests-jar org.springframework.boot:spring-boot:1.5.9.RELEASE, 
but there isn't any here 
http://repo1.maven.org/maven2/org/springframework/boot/spring-boot-test/1.5.9.RELEASE/


> 'ivy:resolve' fails on spring-boot-starter
> --
>
> Key: IVY-1584
> URL: https://issues.apache.org/jira/browse/IVY-1584
> Project: Ivy
>  Issue Type: Bug
>Affects Versions: 2.5.0-rc1
>Reporter: Nicholas Lenzi
>Priority: Major
>
> When we attempt to resolve spring-boot-starter, we get an error indicating 
> org.springframework.boot tests-jar cannot be resolved.  We do not see this 
> issue with IVY 2.4.0.
> We were able to work around this issue by changing the ivy.xml.  Seems like a 
> bug.
> Before:
> {noformat}
> 
>  rev="1.5.9.RELEASE" conf="compile->default">
> 
> 
> {noformat}
> After:
> {noformat}
> 
>  rev="1.5.9.RELEASE" force="true" conf="compile->default"/>
>  rev="1.5.9.RELEASE" conf="compile->default">
> 
> 
> 
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (IVY-1592) Ivy creates wrong version numbers for transitive dependencies

2019-09-07 Thread jaikiran pai (Jira)


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

jaikiran pai resolved IVY-1592.
---
Fix Version/s: master
   Resolution: Fixed

> Ivy creates wrong version numbers for transitive dependencies
> -
>
> Key: IVY-1592
> URL: https://issues.apache.org/jira/browse/IVY-1592
> Project: Ivy
>  Issue Type: Bug
>Affects Versions: 2.4.0, master
>Reporter: mgsoft
>Assignee: jaikiran pai
>Priority: Major
> Fix For: master
>
> Attachments: ivy.xml, ivysettings.xml
>
>
> The following ivy.xml file
>  
> {code:java}
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;>
> 
> 
>  transitive="true" conf="*->default"/>
> 
> 
> {code}
>  
> and the ivysettings.xml file:
>  
> {code:java}
> 
> 
> 
>  value="${user.home}/.m2/repository/[organisation]/[module]/[revision]/[module]-[revision](-[classifier]).[ext]"
>  override="false"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
>  
>  
> yield to following error:
> {code:java}
> [ivy:retrieve] :: Apache Ivy 2.4.0 - 20141213170938 :: 
> http://ant.apache.org/ivy/ ::
> [ivy:retrieve] :: loading settings :: file = 
> /Users/mgsoft/development/eclipse/ws/photon/runtime-EclipseApplication/rcp_movie_sp4_to_ecl_rest_client/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies :: #;working@DNSNAME.local
> [ivy:retrieve] confs: [default]
> [ivy:retrieve] found org.jboss.resteasy#resteasy-client;3.6.1.Final in central
> [ivy:retrieve] found org.jboss.resteasy#resteasy-jaxrs;3.6.1.Final in central
> [ivy:retrieve] :: resolution report :: resolve 1717ms :: artifacts dl 2ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 17 | 0 | 0 | 0 || 2 | 0 |
> -
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve]  WARNINGS
> [ivy:retrieve] module not found: junit#junit;working@DNSNAME.local
> [ivy:retrieve]  local-maven2: tried
> [ivy:retrieve] 
> /Users/mgsoft/.m2/repository/junit/junit/working@DNSNAME.local/junit-work...@dnsname.local.xml
> [ivy:retrieve] -- artifact junit#junit;working@DNSNAME.local!junit.jar:
> [ivy:retrieve] 
> /Users/mgsoft/.m2/repository/junit/junit/working@DNSNAME.local/junit-work...@dnsname.local.jar
> [ivy:retrieve]  central: tried
> [ivy:retrieve] 
> https://repo1.maven.org/maven2/junit/junit/working@DNSNAME.local/junit-work...@dnsname.local.pom
> [ivy:retrieve] -- artifact junit#junit;working@DNSNAME.local!junit.jar:
> [ivy:retrieve] 
> https://repo1.maven.org/maven2/junit/junit/working@DNSNAME.local/junit-work...@dnsname.local.jar
> [ivy:retrieve] module not found: 
> org.jboss.spec.javax.ws.rs#jboss-jaxrs-api_2.1_spec;working@DNSNAME.local
> [ivy:retrieve]  local-maven2: tried
> [ivy:retrieve] 
> /Users/mgsoft/.m2/repository/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_2.1_spec/working@DNSNAME.local/jboss-jaxrs-api_2.1_spec-work...@dnsname.local.xml
> [ivy:retrieve] -- artifact 
> org.jboss.spec.javax.ws.rs#jboss-jaxrs-api_2.1_spec;working@DNSNAME.local!jboss-jaxrs-api_2.1_spec.jar:
> [ivy:retrieve] 
> /Users/mgsoft/.m2/repository/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_2.1_spec/working@DNSNAME.local/jboss-jaxrs-api_2.1_spec-work...@dnsname.local.jar
> [ivy:retrieve]  central: tried
> [ivy:retrieve] 
> https://repo1.maven.org/maven2/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_2.1_spec/working@DNSNAME.local/jboss-jaxrs-api_2.1_spec-work...@dnsname.local.pom
> [ivy:retrieve] -- artifact 
> org.jboss.spec.javax.ws.rs#jboss-jaxrs-api_2.1_spec;working@DNSNAME.local!jboss-jaxrs-api_2.1_spec.jar:
> [ivy:retrieve] 
> https://repo1.maven.org/maven2/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_2.1_spec/working@DNSNAME.local/jboss-jaxrs-api_2.1_spec-work...@dnsname.local.jar
> [ivy:retrieve] module not found: 
> org.jboss.spec.javax.xml.bind#jboss-jaxb-api_2.3_spec;working@DNSNAME.local
> [ivy:retrieve]  local-maven2: tried
> [ivy:retrieve] 
> /Users/mgsoft/.m2/repository/org/jboss/spec/javax/xml/bind/jboss-jaxb-api_2.3_spec/working@DNSNAME.local/jboss-jaxb-api_2.3_spec-work...@dnsname.local.xml
> [ivy:retrieve] -- artifact 
> org.jboss.spec.javax.xml.bind#jboss-jaxb-api_2.3_spec;working@DNSNAME.local!jboss-jaxb-api_2.3_spec.jar:
> [ivy:retrieve] 
> /Users/mgsoft/.m2/repository/org/jboss/spec/javax/xml/bind/jboss-jaxb-api_2.3_spec/working@DNSNAME.local/jboss-jaxb-api_2.3_spec-work...@dnsname.local.jar
> [ivy:retrieve]  central: tried
> [ivy:retrieve] 
>