[jira] [Closed] (IVY-1597) IBiblioResolverTest#testErrorReport failing
[
https://issues.apache.org/jira/browse/IVY-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Levy-Lambert closed IVY-1597.
-
Resolution: Fixed
> IBiblioResolverTest#testErrorReport failing
> ---
>
> Key: IVY-1597
> URL: https://issues.apache.org/jira/browse/IVY-1597
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Reporter: Antoine Levy-Lambert
>Priority: Major
>
> When building Ivy from source I am seeing this error :
>
> |estErrorReport|Error|Already seen doctype.
>
> {{java.text.ParseException: Already seen doctype.}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.newParserException(PomModuleDescriptorParser.java:470)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:326)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:841)}}
> {{at
> org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:858)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1362)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.parse(BasicResolver.java:541)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:278)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:554)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolverTest.testErrorReport(IBiblioResolverTest.java:208)}}
> {{Caused by: org.xml.sax.SAXParseException; systemId:
> file:/Users/antoine/dev/asf/ant-ivy/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original;
> lineNumber: 2; columnNumber: 10; Already seen doctype.}}
> {{at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)}}
> {{at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)}}
> {{at org.apache.ivy.util.XMLHelper.parseToDom(XMLHelper.java:220)}}
> {{at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:129)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:140)}}|
>
>
> When running IBiblioResolverTest#testErrorReport from within IntelliJ the
> logs contain this :
>
> {noformat}
> 0 = "4 test: no namespace defined: using system"
> 1 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
> build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
> 2 = "4 \t trying
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 3 = "3 \t\ttried
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 4 = "3 Execution environment profile JavaSE-1.2 loaded"
> 5 = "3 Execution environment profile JavaSE-1.3 loaded"
> 6 = "3 Execution environment profile JavaSE-1.4 loaded"
> 7 = "3 Execution environment profile JavaSE-1.5 loaded"
> 8 = "3 Execution environment profile JavaSE-1.6 loaded"
> 9 = "3 Execution environment profile JavaSE-1.7 loaded"
> 10 = "3 Execution environment profile OSGi/Minimum-1.1 loaded"
> 11 = "3 Execution environment profile JavaSE-1.8 loaded"
> 12 = "3 Execution environment profile CDC-1.0/Foundation-1.0 loaded"
> 13 = "3 Execution environment profile CDC-1.1/Foundation-1.1 loaded"
> 14 = "3 Execution environment profile OSGi/Minimum-1.2 loaded"
> 15 = "3 Execution environment profile OSGi/Minimum-1.0 loaded"
> 16 = "3 \ttest: found md file for org.apache#commons-fileupload;1.0"
> 17 = "3 \t\t=>
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
> (1.0)"
> 18 = "4 \tparser = pom parser"
> 19 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
> build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
> 20 = "3 downloading
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
> ..."
> 21 = "3 \ttest: downloading
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 22 = "4 \t\tto
> /Users/antoine/dev/asf/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original.part"
> 23 = "3 \t[SUCCESSFUL ]
> org.apache#commons-fileupload;1.0!commons-fileupload.pom(pom.original)
> (203ms)"
> 24 = "3 WARN: io problem while parsing ivy file:
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
> (java.net.MalformedURLException: null)"
> 25 = "4 java.
[jira] [Commented] (IVY-1597) IBiblioResolverTest#testErrorReport failing
[
https://issues.apache.org/jira/browse/IVY-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706500#comment-16706500
]
Antoine Levy-Lambert commented on IVY-1597:
---
Changing the DNS servers used on my home network fixes the problem.
I guess at some other level this issue could be dealt with by making a sort of
quality control on files downloaded to check that they do not have a tag
at the beginning when this is not expected.
> IBiblioResolverTest#testErrorReport failing
> ---
>
> Key: IVY-1597
> URL: https://issues.apache.org/jira/browse/IVY-1597
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Reporter: Antoine Levy-Lambert
>Priority: Major
>
> When building Ivy from source I am seeing this error :
>
> |estErrorReport|Error|Already seen doctype.
>
> {{java.text.ParseException: Already seen doctype.}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.newParserException(PomModuleDescriptorParser.java:470)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:326)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:841)}}
> {{at
> org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:858)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1362)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.parse(BasicResolver.java:541)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:278)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:554)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolverTest.testErrorReport(IBiblioResolverTest.java:208)}}
> {{Caused by: org.xml.sax.SAXParseException; systemId:
> file:/Users/antoine/dev/asf/ant-ivy/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original;
> lineNumber: 2; columnNumber: 10; Already seen doctype.}}
> {{at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)}}
> {{at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)}}
> {{at org.apache.ivy.util.XMLHelper.parseToDom(XMLHelper.java:220)}}
> {{at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:129)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:140)}}|
>
>
> When running IBiblioResolverTest#testErrorReport from within IntelliJ the
> logs contain this :
>
> {noformat}
> 0 = "4 test: no namespace defined: using system"
> 1 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
> build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
> 2 = "4 \t trying
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 3 = "3 \t\ttried
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 4 = "3 Execution environment profile JavaSE-1.2 loaded"
> 5 = "3 Execution environment profile JavaSE-1.3 loaded"
> 6 = "3 Execution environment profile JavaSE-1.4 loaded"
> 7 = "3 Execution environment profile JavaSE-1.5 loaded"
> 8 = "3 Execution environment profile JavaSE-1.6 loaded"
> 9 = "3 Execution environment profile JavaSE-1.7 loaded"
> 10 = "3 Execution environment profile OSGi/Minimum-1.1 loaded"
> 11 = "3 Execution environment profile JavaSE-1.8 loaded"
> 12 = "3 Execution environment profile CDC-1.0/Foundation-1.0 loaded"
> 13 = "3 Execution environment profile CDC-1.1/Foundation-1.1 loaded"
> 14 = "3 Execution environment profile OSGi/Minimum-1.2 loaded"
> 15 = "3 Execution environment profile OSGi/Minimum-1.0 loaded"
> 16 = "3 \ttest: found md file for org.apache#commons-fileupload;1.0"
> 17 = "3 \t\t=>
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
> (1.0)"
> 18 = "4 \tparser = pom parser"
> 19 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
> build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
> 20 = "3 downloading
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
> ..."
> 21 = "3 \ttest: downloading
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 22 = "4 \t\tto
> /Users/antoine/dev/asf/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original.part"
> 23
[jira] [Commented] (IVY-1597) IBiblioResolverTest#testErrorReport failing
[
https://issues.apache.org/jira/browse/IVY-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706498#comment-16706498
]
Antoine Levy-Lambert commented on IVY-1597:
---
OK this is caused by my ISP Verizon redirecting the NXDOMAIN requests such as
this unknownhost.comx URL. See
https://www.verizon.com/support/residential/internet/home-network/settings/opt-out-of-dns-assist
> IBiblioResolverTest#testErrorReport failing
> ---
>
> Key: IVY-1597
> URL: https://issues.apache.org/jira/browse/IVY-1597
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Reporter: Antoine Levy-Lambert
>Priority: Major
>
> When building Ivy from source I am seeing this error :
>
> |estErrorReport|Error|Already seen doctype.
>
> {{java.text.ParseException: Already seen doctype.}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.newParserException(PomModuleDescriptorParser.java:470)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:326)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:841)}}
> {{at
> org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:858)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1362)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.parse(BasicResolver.java:541)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:278)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:554)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolverTest.testErrorReport(IBiblioResolverTest.java:208)}}
> {{Caused by: org.xml.sax.SAXParseException; systemId:
> file:/Users/antoine/dev/asf/ant-ivy/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original;
> lineNumber: 2; columnNumber: 10; Already seen doctype.}}
> {{at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)}}
> {{at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)}}
> {{at org.apache.ivy.util.XMLHelper.parseToDom(XMLHelper.java:220)}}
> {{at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:129)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:140)}}|
>
>
> When running IBiblioResolverTest#testErrorReport from within IntelliJ the
> logs contain this :
>
> {noformat}
> 0 = "4 test: no namespace defined: using system"
> 1 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
> build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
> 2 = "4 \t trying
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 3 = "3 \t\ttried
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 4 = "3 Execution environment profile JavaSE-1.2 loaded"
> 5 = "3 Execution environment profile JavaSE-1.3 loaded"
> 6 = "3 Execution environment profile JavaSE-1.4 loaded"
> 7 = "3 Execution environment profile JavaSE-1.5 loaded"
> 8 = "3 Execution environment profile JavaSE-1.6 loaded"
> 9 = "3 Execution environment profile JavaSE-1.7 loaded"
> 10 = "3 Execution environment profile OSGi/Minimum-1.1 loaded"
> 11 = "3 Execution environment profile JavaSE-1.8 loaded"
> 12 = "3 Execution environment profile CDC-1.0/Foundation-1.0 loaded"
> 13 = "3 Execution environment profile CDC-1.1/Foundation-1.1 loaded"
> 14 = "3 Execution environment profile OSGi/Minimum-1.2 loaded"
> 15 = "3 Execution environment profile OSGi/Minimum-1.0 loaded"
> 16 = "3 \ttest: found md file for org.apache#commons-fileupload;1.0"
> 17 = "3 \t\t=>
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
> (1.0)"
> 18 = "4 \tparser = pom parser"
> 19 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
> build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
> 20 = "3 downloading
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
> ..."
> 21 = "3 \ttest: downloading
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 22 = "4 \t\tto
> /Users/antoine/dev/asf/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original.part"
> 23 = "3 \t[SUCCESSFUL ]
> org.apache#commons-fileupload;1.0!c
[jira] [Commented] (IVY-1597) IBiblioResolverTest#testErrorReport failing
[
https://issues.apache.org/jira/browse/IVY-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706489#comment-16706489
]
Antoine Levy-Lambert commented on IVY-1597:
---
It looks like this issue is caused by Ivy downloading web pages coming from my
Internet provider when trying to resolve a dummy host name. A file called
{code:java}
build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original.part{code}
{code:java}
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>http://searchassist.verizon.com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=http%3A%2F%2Funknown.host.comx%2Forg%2Fapache%2Fcommons-fileupload%2F1.0%2Fcommons-fileupload-1.0.pom&FailureMode=1&Implementation=&AddInType=4&Version=pywr1.0&ClientLocation=us"/>url="http://searchassist.verizon.com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=http%3A%2F%2Funknown.host.comx%2Forg%2Fapache%2Fcommons-fileupload%2F1.0%2Fcommons-fileupload-1.0.pom&FailureMode=1&Implementation=&AddInType=4&Version=pywr1.0&ClientLocation=us";if(top.location!=location){var
w=window,d=document,e=d.documentElement,b=d.body,x=w.innerWidth||e.clientWidth||b.clientWidth,y=w.innerHeight||e.clientHeight||b.clientHeight;url+="&w="+x+"&h="+y;}window.location.replace(url);{code}
> IBiblioResolverTest#testErrorReport failing
> ---
>
> Key: IVY-1597
> URL: https://issues.apache.org/jira/browse/IVY-1597
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Reporter: Antoine Levy-Lambert
>Priority: Major
>
> When building Ivy from source I am seeing this error :
>
> |estErrorReport|Error|Already seen doctype.
>
> {{java.text.ParseException: Already seen doctype.}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.newParserException(PomModuleDescriptorParser.java:470)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:326)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:841)}}
> {{at
> org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:858)}}
> {{at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1362)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.parse(BasicResolver.java:541)}}
> {{at
> org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:278)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:554)}}
> {{at
> org.apache.ivy.plugins.resolver.IBiblioResolverTest.testErrorReport(IBiblioResolverTest.java:208)}}
> {{Caused by: org.xml.sax.SAXParseException; systemId:
> file:/Users/antoine/dev/asf/ant-ivy/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original;
> lineNumber: 2; columnNumber: 10; Already seen doctype.}}
> {{at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)}}
> {{at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)}}
> {{at org.apache.ivy.util.XMLHelper.parseToDom(XMLHelper.java:220)}}
> {{at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:129)}}
> {{at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:140)}}|
>
>
> When running IBiblioResolverTest#testErrorReport from within IntelliJ the
> logs contain this :
>
> {noformat}
> 0 = "4 test: no namespace defined: using system"
> 1 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
> build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
> 2 = "4 \t trying
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 3 = "3 \t\ttried
> http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
> 4 = "3 Execution environment profile JavaSE-1.2 loaded"
> 5 = "3 Execution environment profile JavaSE-1.3 loaded"
> 6 = "3 Execution environment profile JavaSE-1.4 loaded"
> 7 = "3 Execution environment profile JavaSE-1.5 loaded"
> 8 = "3 Execution environment profile JavaSE-1.6 loaded"
> 9 = "3 Execution environment
[jira] [Created] (IVY-1597) IBiblioResolverTest#testErrorReport failing
Antoine Levy-Lambert created IVY-1597:
-
Summary: IBiblioResolverTest#testErrorReport failing
Key: IVY-1597
URL: https://issues.apache.org/jira/browse/IVY-1597
Project: Ivy
Issue Type: Bug
Components: Core
Reporter: Antoine Levy-Lambert
When building Ivy from source I am seeing this error :
|estErrorReport|Error|Already seen doctype.
{{java.text.ParseException: Already seen doctype.}}
{{at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.newParserException(PomModuleDescriptorParser.java:470)}}
{{at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:326)}}
{{at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)}}
{{at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:841)}}
{{at
org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)}}
{{at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:858)}}
{{at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1362)}}
{{at
org.apache.ivy.plugins.resolver.BasicResolver.parse(BasicResolver.java:541)}}
{{at
org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:278)}}
{{at
org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:554)}}
{{at
org.apache.ivy.plugins.resolver.IBiblioResolverTest.testErrorReport(IBiblioResolverTest.java:208)}}
{{Caused by: org.xml.sax.SAXParseException; systemId:
file:/Users/antoine/dev/asf/ant-ivy/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original;
lineNumber: 2; columnNumber: 10; Already seen doctype.}}
{{at
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)}}
{{at
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)}}
{{at org.apache.ivy.util.XMLHelper.parseToDom(XMLHelper.java:220)}}
{{at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:129)}}
{{at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:140)}}|
When running IBiblioResolverTest#testErrorReport from within IntelliJ the logs
contain this :
{noformat}
0 = "4 test: no namespace defined: using system"
1 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
2 = "4 \t trying
http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
3 = "3 \t\ttried
http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
4 = "3 Execution environment profile JavaSE-1.2 loaded"
5 = "3 Execution environment profile JavaSE-1.3 loaded"
6 = "3 Execution environment profile JavaSE-1.4 loaded"
7 = "3 Execution environment profile JavaSE-1.5 loaded"
8 = "3 Execution environment profile JavaSE-1.6 loaded"
9 = "3 Execution environment profile JavaSE-1.7 loaded"
10 = "3 Execution environment profile OSGi/Minimum-1.1 loaded"
11 = "3 Execution environment profile JavaSE-1.8 loaded"
12 = "3 Execution environment profile CDC-1.0/Foundation-1.0 loaded"
13 = "3 Execution environment profile CDC-1.1/Foundation-1.1 loaded"
14 = "3 Execution environment profile OSGi/Minimum-1.2 loaded"
15 = "3 Execution environment profile OSGi/Minimum-1.0 loaded"
16 = "3 \ttest: found md file for org.apache#commons-fileupload;1.0"
17 = "3 \t\t=>
http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
(1.0)"
18 = "4 \tparser = pom parser"
19 = "4 \tno ivy file in cache for org.apache#commons-fileupload;1.0: tried
build/cache/org.apache/commons-fileupload/ivy-1.0.xml"
20 = "3 downloading
http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
..."
21 = "3 \ttest: downloading
http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom";
22 = "4 \t\tto
/Users/antoine/dev/asf/build/cache/org.apache/commons-fileupload/ivy-1.0.xml.original.part"
23 = "3 \t[SUCCESSFUL ]
org.apache#commons-fileupload;1.0!commons-fileupload.pom(pom.original) (203ms)"
24 = "3 WARN: io problem while parsing ivy file:
http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupload-1.0.pom
(java.net.MalformedURLException: null)"
25 = "4 java.net.MalformedURLException\n\tat
java.net.URL.(URL.java:627)\n\tat java.net.URL.(URL.java:490)\n\tat
java.net.URL.(URL.java:439)\n\tat
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:620)\n\tat
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1304)\n\tat
com.sun.org.apache
[jira] [Resolved] (IVY-1486) Order-dependent resolution: exclude not respected
[ https://issues.apache.org/jira/browse/IVY-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Levy-Lambert resolved IVY-1486. --- Resolution: Fixed The commit by Gintas Grigeliionis on Tuesday August 14 should resolve the issue. It seems that a new release of ivy is needed though. > Order-dependent resolution: exclude not respected > - > > Key: IVY-1486 > URL: https://issues.apache.org/jira/browse/IVY-1486 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.5.0-rc1 >Reporter: David Turner >Assignee: Antoine Levy-Lambert >Priority: Major > Attachments: 0001-Fix-IVY-1486.patch, > 0001-Make-doesCallersExclude-check-only-callers-of-this-v.patch, ivy-4sq.xml, > ivy-exclude-finagle.xml, ivy-min2.xml > > > To repro, create an ivy.xml which looks like this (see the attached one for > an real-world example that you can test out): > dependency A 1.1 > dependency X 1.2 > exclude Y > --- > dependency A 1.1's depends on: >dependency X 1.1 > Dependency X 1.1's depends on: > dependency Y 1.1 > Dependency X 1.2's depends on: > dependency Y 1.2 > -- > In this case, we will get Y 1.2. But if we swap the order of the > dependencies in our ivy.xml, we'll get Y 1.1. I think 1.1 is correct, > because we've excluded 1.2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IVY-1486) Order-dependent resolution: exclude not respected
[ https://issues.apache.org/jira/browse/IVY-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Levy-Lambert reassigned IVY-1486: - Assignee: Antoine Levy-Lambert > Order-dependent resolution: exclude not respected > - > > Key: IVY-1486 > URL: https://issues.apache.org/jira/browse/IVY-1486 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: master >Reporter: David Turner >Assignee: Antoine Levy-Lambert > Attachments: 0001-Fix-IVY-1486.patch, > 0001-Make-doesCallersExclude-check-only-callers-of-this-v.patch, ivy-4sq.xml, > ivy-exclude-finagle.xml, ivy-min2.xml > > > To repro, create an ivy.xml which looks like this (see the attached one for > an real-world example that you can test out): > dependency A 1.1 > dependency X 1.2 > exclude Y > --- > dependency A 1.1's depends on: >dependency X 1.1 > Dependency X 1.1's depends on: > dependency Y 1.1 > Dependency X 1.2's depends on: > dependency Y 1.2 > -- > In this case, we will get Y 1.2. But if we swap the order of the > dependencies in our ivy.xml, we'll get Y 1.1. I think 1.1 is correct, > because we've excluded 1.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IVYDE-379) Syntax error in DOAP file release section
[ https://issues.apache.org/jira/browse/IVYDE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548029#comment-14548029 ] Antoine Levy-Lambert commented on IVYDE-379: Thanks Sebb. Where does files.xml live ? Is this a file that each ASF committer can change ? Ivyde migrated to git last year like all the Ant project family. > Syntax error in DOAP file release section > - > > Key: IVYDE-379 > URL: https://issues.apache.org/jira/browse/IVYDE-379 > Project: IvyDE > Issue Type: Bug > Environment: > http://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk/doap_IvyDE.rdf >Reporter: Sebb >Assignee: Nicolas Lalevée > > DOAP files can contain details of multiple release Versions, however each > must be listed in a separate release section, for example: > > > Apache XYZ > 2015-02-16 > 1.6.2 > > > > > Apache XYZ > 2014-09-24 > 1.6.1 > > > Please can the project DOAP be corrected accordingly? > Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IVYDE-379) Syntax error in DOAP file release section
[ https://issues.apache.org/jira/browse/IVYDE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547388#comment-14547388 ] Antoine Levy-Lambert commented on IVYDE-379: Updated doap file in git again, it should be all right now > Syntax error in DOAP file release section > - > > Key: IVYDE-379 > URL: https://issues.apache.org/jira/browse/IVYDE-379 > Project: IvyDE > Issue Type: Bug > Environment: > http://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk/doap_IvyDE.rdf >Reporter: Sebb >Assignee: Nicolas Lalevée > > DOAP files can contain details of multiple release Versions, however each > must be listed in a separate release section, for example: > > > Apache XYZ > 2015-02-16 > 1.6.2 > > > > > Apache XYZ > 2014-09-24 > 1.6.1 > > > Please can the project DOAP be corrected accordingly? > Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IVY-1197) OutOfMemoryError during ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491847#comment-14491847
]
Antoine Levy-Lambert commented on IVY-1197:
---
So now there is a common understanding that :
- when running ivy without commons-httpclient + commons-codec +
commons-logging, ivy is not able to upload files of more than 1 GB of size to
HTTP destinations requiring authentication. This is due to limitations of the
way the HttpUrlConnection is implemented in the JDK
- the workaround is to always use ivy with commons-httpclient, commons-codec
and commons-logging when the use case will involve uploading large files to
sites requiring authentication
- the change to do in the deliverables of ivy is to add this information to the
documentation
- trying to change
[choose-distrib.html|http://ant.apache.org/ivy/choose-distrib.html] currently
held by an issue with the script to generate the site - or my making an
unsupported change in the source html ?
> OutOfMemoryError during ivy:publish
> ---
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt, ivylarge.zip,
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around
> 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are
> published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message was sent by Atlassian JIR
[jira] [Commented] (IVY-1197) OutOfMemoryError during ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486535#comment-14486535
]
Antoine Levy-Lambert commented on IVY-1197:
---
I will work on this as soon as I can. Will write an email about this on the ivy
dev mailing list.
> OutOfMemoryError during ivy:publish
> ---
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt, ivylarge.zip,
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around
> 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are
> published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IVY-1197) OutOfMemoryError during ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386098#comment-14386098
]
Antoine Levy-Lambert commented on IVY-1197:
---
I have taken a look at the patch. The only difference I see with ivy's
FileUtil#copy is that FileUtil#copy is calling dest.flush() . Is that what is
causing the Out of Memory Exception ?
Also I would like to have a setup to reproduce the out of memory exception so
that we can be confident about the existence of the problem and of the fix.
> OutOfMemoryError during ivy:publish
> ---
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt,
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around
> 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are
> published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IVY-1197) OutOfMemoryError during ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Levy-Lambert updated IVY-1197:
--
Summary: OutOfMemoryError during ivy:publish (was: OutOfMemoryError
duriong ivy:publish)
> OutOfMemoryError during ivy:publish
> ---
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt,
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around
> 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are
> published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IVY-1197) OutOfMemoryError duriong ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375199#comment-14375199
]
Antoine Levy-Lambert commented on IVY-1197:
---
Hello Loren,
thanks for the patch, I will work on it as soon as I get a chance,
Antoine
> OutOfMemoryError duriong ivy:publish
>
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt,
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around
> 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are
> published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IVY-1197) OutOfMemoryError duriong ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319508#comment-14319508
]
Antoine Levy-Lambert commented on IVY-1197:
---
Loren can you provide a patch based on the current git HEAD ?
> OutOfMemoryError duriong ivy:publish
>
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt,
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around
> 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are
> published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IVY-1399) impossible to get artifacts when data has not been loaded.
[ https://issues.apache.org/jira/browse/IVY-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Levy-Lambert resolved IVY-1399. --- Resolution: Fixed Fix Version/s: 2.4.0 You may want to build ivy from trunk to crosscheck that it works for you > impossible to get artifacts when data has not been loaded. > -- > > Key: IVY-1399 > URL: https://issues.apache.org/jira/browse/IVY-1399 > Project: Ivy > Issue Type: Bug >Affects Versions: 2.3.0-RC2 >Reporter: Carl Lerche > Fix For: 2.4.0 > > Attachments: 0001-fix-IVY-1399.patch > > > I am getting the error "impossible to get artifacts when data has not been > loaded. IvyNode = com.google.guava#guava;r08" > This is happening with ivy 2.3.0-RC2. > I am unsure what the best information to provide is, so here is the verbose > output as well as ivy.xml > https://gist.github.com/ebc2b325d333b739d0b1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (IVY-1465) ModuleRules.getRule is O(n) leading to resolution slowness
[ https://issues.apache.org/jira/browse/IVY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982447#comment-13982447 ] Antoine Levy-Lambert commented on IVY-1465: --- Patch committed in ivy trunk, thanks. > ModuleRules.getRule is O(n) leading to resolution slowness > -- > > Key: IVY-1465 > URL: https://issues.apache.org/jira/browse/IVY-1465 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.3.0 > Environment: OpenJDK 6,7, MacOSX + Ubuntu >Reporter: Joshua Suereth >Priority: Minor > Labels: performance > > So, for the sbt project we noticed significant resolution time improvements > with the following patch: > https://github.com/sbt/ivy/pull/1 > The reasoning: > A lot of artifacts being resolved use Maven's "dependencyManagement" > conventions > Ivy appears to turn these into "exact matcher" rules > A ton of resolution time is spent filtering through these rules > The existing solution is O(n) for all overrides > What the patch does: > Creates a key'd store for all "exact matcher" rules > When executing rules, ensure that we only traverse what we have to > (non-exact, exact specific to our key and "default"). > As I said, this represents a significant speed bump for sbt builds using Ivy. > All existing tests pass, and I think they cover this aspect of ivy pretty > well, from what I could see. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (IVY-1399) impossible to get artifacts when data has not been loaded.
[ https://issues.apache.org/jira/browse/IVY-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982415#comment-13982415 ] Antoine Levy-Lambert commented on IVY-1399: --- Patch submitted, thanks. > impossible to get artifacts when data has not been loaded. > -- > > Key: IVY-1399 > URL: https://issues.apache.org/jira/browse/IVY-1399 > Project: Ivy > Issue Type: Bug >Affects Versions: 2.3.0-RC2 >Reporter: Carl Lerche > Attachments: 0001-fix-IVY-1399.patch > > > I am getting the error "impossible to get artifacts when data has not been > loaded. IvyNode = com.google.guava#guava;r08" > This is happening with ivy 2.3.0-RC2. > I am unsure what the best information to provide is, so here is the verbose > output as well as ivy.xml > https://gist.github.com/ebc2b325d333b739d0b1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (IVY-1197) OutOfMemoryError duriong ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975028#comment-13975028
]
Antoine Levy-Lambert commented on IVY-1197:
---
I have tried to reproduce the problem using ivy 2.4.0-rc1 with its dependencies.
I have used JDK 1.6.0 and a URL resolver
http://localhost/webdav/[organisation]/[module]/[revision]/ivy.xml"; />
http://localhost/webdav/[organisation]/[module]/[revision]/[artifact].[ext]";
/>
I am able to upload an artifact of 600 GB without exceptions. My problem is
that ivy does not seem to know how to create the folders [organisation],
[module], and [revision]. On the server side I have activated the WebDAV module
of the httpd server of my Mac. Maybe some WebDAV servers automatically create
folders when they get a PUT request ?. If I create these folders by hand the
upload of the 600 GB file works.
I also tried to use the VFS resolver with WebDAV but had no luck. With the
vfs-1.0 which ships with ivy I got this exception :
Users/antoine/dev/ivy-1197/project/build.xml:31: impossible to publish
artifacts for myorg#mymodule;03_apr_2014: java.lang.IllegalArgumentException:
invalid vfs uri webdav://localhost:80/webdav/myorg/mymodule/03_apr_2014/aa.zip
to put data to: resource has no content
vfs-2.x does not work with ivy 2.4. because vfs has renamed its classes between
1.x and 2.x
> OutOfMemoryError duriong ivy:publish
>
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt,
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
>
[jira] [Commented] (IVY-1197) OutOfMemoryError duriong ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959530#comment-13959530
]
Antoine Levy-Lambert commented on IVY-1197:
---
I agree that it is a major problem. The solution provided by Loren Kratzke
above looks simple enough, a patch would not hurt though.
> OutOfMemoryError duriong ivy:publish
>
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0
>Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to
>
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152:
> The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at
> org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at
> org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at
> org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at
> org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around
> 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are
> published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (IVY-1374) ssh connection sometimes fails
[ https://issues.apache.org/jira/browse/IVY-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590191#comment-13590191 ] Antoine Levy-Lambert commented on IVY-1374: --- Atsuhiko Yamanaka wrote : It seems JCE included in Java7u6(and later) has suddenly changed its behavior. Please try following version, http://jcraft.com/jsch/jsch-0.1.50-rc1.zip We have confirmed this version can make 10,000 connections without "verify: false" errors on Java7u15. > ssh connection sometimes fails > -- > > Key: IVY-1374 > URL: https://issues.apache.org/jira/browse/IVY-1374 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.3.0-RC1 > Environment: ubuntu 12.04, jdk7.06/32bits, jenkins, jsch 0.1.84, > "OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012" >Reporter: Simon IJskes >Assignee: Maarten Coene >Priority: Minor > Fix For: 2.4.0 > > > when the sftp resolver connects to a remote repository, it sometimes fails to > fetch the artifacts. > This is accompanied by a log entry in the /var/log/auth.log on the server > side: > Aug 30 10:36:02 zzz sshd[1371]: Received disconnect from zzz.zzz.zzz.zzz: 3: > com.jcraft.jsch.JSchException: verify: false [preauth] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (IVY-1374) ssh connection sometimes fails
[ https://issues.apache.org/jira/browse/IVY-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582855#comment-13582855 ] Antoine Levy-Lambert commented on IVY-1374: --- I have the same errors using Ant + jsch + Java 1.7. I have entered a bug report in the tracker of jsch at sourceforge : https://sourceforge.net/tracker/?func=detail&aid=3605486&group_id=64920&atid=509122 . The combo jsch + java 1.7 seems to be causing the problem which is not experienced with Java 1.6. > ssh connection sometimes fails > -- > > Key: IVY-1374 > URL: https://issues.apache.org/jira/browse/IVY-1374 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.3.0-RC1 > Environment: ubuntu 12.04, jdk7.06/32bits, jenkins, jsch 0.1.84, > "OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012" >Reporter: Simon IJskes >Priority: Minor > > when the sftp resolver connects to a remote repository, it sometimes fails to > fetch the artifacts. > This is accompanied by a log entry in the /var/log/auth.log on the server > side: > Aug 30 10:36:02 zzz sshd[1371]: Received disconnect from zzz.zzz.zzz.zzz: 3: > com.jcraft.jsch.JSchException: verify: false [preauth] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (IVY-1195) feature request: retrying resolver wrapper
[
https://issues.apache.org/jira/browse/IVY-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878164#action_12878164
]
Antoine Levy-Lambert commented on IVY-1195:
---
I agree with Maarten that the proper ordering of the builds should be done
within the buildserver process space.
The project for which I work uses a plugin for CruiseControl which builds ivy
based projects in the proper order.
I guess I should contribute this to CruiseControl.
> feature request: retrying resolver wrapper
> --
>
> Key: IVY-1195
> URL: https://issues.apache.org/jira/browse/IVY-1195
> Project: Ivy
> Issue Type: New Feature
> Components: Core
>Affects Versions: 2.1.0
>Reporter: Stepan Koltsov
>
> I'm requesting a retrying resolver.
> *description*
> Retrying resolver delegates resolution to configured child resolver. If child
> resolver fails, if requests child to perform a resolution again after some
> time.
> *example*
> {code}
>
>
>
>
>
> {code}
> In the example above, "default" resolver will try call SVN resolver to
> resolve dependencies, if SVN resolver fails, it will be called again after
> 10s, then after 15s, then after 27s, and so on, but not after 5 minutes after
> resolver start.
> *motivation*
> We have build server, that builds projects right after commit. Projects
> depend on concrete revisions of another projects, revisions are specified in
> ivy.xml (say, "app" depends on "lib"). Sometimes developers commit to
> dependent project "app" immediately after commit to the base project "lib".
> And in this case there is a high chance, that base project "lib" is not yet
> built (so artifact is not published) at the time of dependent project "app"
> ivy:resolve task run. So build of dependent project "app" fails.
> Retry task could resolve this situation: dependent project "app" build start
> will be delayed until completion of "lib" build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-1193) Trying to move Ivy to an HTTP-based publish model, we discovered that it doesn't perform a MKCOL before doing a PUT.
[ https://issues.apache.org/jira/browse/IVY-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871381#action_12871381 ] Antoine Levy-Lambert commented on IVY-1193: --- Hi, using WebDAV is possible using the vfs resolver. In my project we are using the vfs resolver and a vfs provider that we wrote ourselves based on jackrabbit. My colleague who wrote the vfs provider tells me that vfs ships with another webdav provider now. This was not the case when we did our development obviously. You should try the vfs solution. If you have issues, write it in this ticket. The url resolver is not doing MKCOL operations, maybe it is thought for servers which do not implement the full WebDAV spec but which have upload servlets. Regards, Antoine > Trying to move Ivy to an HTTP-based publish model, we discovered that it > doesn't perform a MKCOL before doing a PUT. > > > Key: IVY-1193 > URL: https://issues.apache.org/jira/browse/IVY-1193 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.1.0 > Environment: All environments. >Reporter: Ervin Beba > > The problem is that when Ivy attempts to publish to a URL resolver via HTTP, > it does not adhere to the WebDav requirement that you create the parent path > (parent collections) with a MKCOL command before the PUT command. Ivy > incorrectly just attempts to PUT artifacts to a path which hasn't been > created. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-1044) retrieve doesn't retrive files if the current one is more recent
[ https://issues.apache.org/jira/browse/IVY-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865960#action_12865960 ] Antoine Levy-Lambert commented on IVY-1044: --- Thanks Maarten. I will try this. Antoine > retrieve doesn't retrive files if the current one is more recent > > > Key: IVY-1044 > URL: https://issues.apache.org/jira/browse/IVY-1044 > Project: Ivy > Issue Type: Improvement > Components: Ant, Core >Affects Versions: 2.0 > Environment: Win XP, J2SE 1.6.0_11-b03 >Reporter: Daniel Dekany >Assignee: Maarten Coene > Fix For: 2.2.0-RC1 > > > The "retrieve" task will not retrieve files (artifacts) whose file > modification date is greater than of the file in the repository (in the > "resolver"), not even if sync="true". This way the target directory goes out > of sync if (a) the module is downgraded in the repository or (b) the > developer has overwritten the artifact manually when experiencing with > something. Thus the only way to keep the target directory in sync is deleting > it before retrieving, but of course that means suboptimal performance, and > makes sync="true" useless anyway. Simply, a file should be retrieved if the > date (or size!) is *different* than in the repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-1127) branch field of dependencies is null after doing programmatic parsing of a module descriptor
[
https://issues.apache.org/jira/browse/IVY-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Levy-Lambert resolved IVY-1127.
---
Resolution: Invalid
I found out that the branch is found out from settings which are themselves
found in a static class IvyContext ...
this is in ModuleRevisionId.java :
this.branch = (replaceNullBranchWithDefault && branch == null)
// we test if there's already an Ivy instance loaded, to avoid
loading a default one
// just to get the default branch
? (context.peekIvy() == null ? null :
context.getSettings().getDefaultBranch(moduleId))
: branch;
So adding these lines after the creation of my "IvySettings" fixed the issue :
// these lines allow the settings, including the branch, to be
found
IvyContext.pushNewCopyContext();
IvyContext.getContext().setIvy(ivy);
> branch field of dependencies is null after doing programmatic parsing of a
> module descriptor
>
>
> Key: IVY-1127
> URL: https://issues.apache.org/jira/browse/IVY-1127
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.1.0-RC2
> Environment: Win 32/Java 1.5
>Reporter: Antoine Levy-Lambert
>
> ModuleDescriptorParserRegistry mdpr =
> ModuleDescriptorParserRegistry
> .getInstance();
> ModuleDescriptor md = mdpr.parseDescriptor(ivy.getSettings(),
> ivyFile
> .toURL(), true);
>DependencyDescriptor[] dependencies = md.getDependencies();
>for (int i = 0; i < dependencies.length; i++) {
> DependencyDescriptor dependency =
> dependencies[i];
> ModuleRevisionId depMrid =
> dependency.getDependencyRevisionId();
> if (depMrid.getRevision().startsWith("latest"))
> {
>
> String depModule = depMrid.getName();
> String depOrganisation =
> depMrid.getOrganisation();
> String depRevision =
> depMrid.getRevision();
> // I am getting null here
> String depBranch = depMrid.getBranch();
>}
>}
> Any idea what is going on here ? It looks a bit similar to IVY-1087
> Regards,
> Antoine
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-1127) branch field of dependencies is null after doing programmatic parsing of a module descriptor
branch field of dependencies is null after doing programmatic parsing of a
module descriptor
Key: IVY-1127
URL: https://issues.apache.org/jira/browse/IVY-1127
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.1.0-RC2
Environment: Win 32/Java 1.5
Reporter: Antoine Levy-Lambert
ModuleDescriptorParserRegistry mdpr =
ModuleDescriptorParserRegistry
.getInstance();
ModuleDescriptor md = mdpr.parseDescriptor(ivy.getSettings(),
ivyFile
.toURL(), true);
DependencyDescriptor[] dependencies = md.getDependencies();
for (int i = 0; i < dependencies.length; i++) {
DependencyDescriptor dependency =
dependencies[i];
ModuleRevisionId depMrid =
dependency.getDependencyRevisionId();
if (depMrid.getRevision().startsWith("latest"))
{
String depModule = depMrid.getName();
String depOrganisation =
depMrid.getOrganisation();
String depRevision =
depMrid.getRevision();
// I am getting null here
String depBranch = depMrid.getBranch();
}
}
Any idea what is going on here ? It looks a bit similar to IVY-1087
Regards,
Antoine
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-814) Filesystem resolver does not work with branches
[
https://issues.apache.org/jira/browse/IVY-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594245#action_12594245
]
Antoine Levy-Lambert commented on IVY-814:
--
This is a blocker for our project to upgrade from 2.0.0-alpha2.
> Filesystem resolver does not work with branches
> ---
>
> Key: IVY-814
> URL: https://issues.apache.org/jira/browse/IVY-814
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-beta-1, 2.0.0-beta-2, 2.0-RC1
> Environment: Found on Mac OS X, but should be reproduced everywhere
>Reporter: Ivan "Rambius" Ivanov
> Attachments: FileSystemResolver.diff, IVY-814.zip
>
>
> I have the following settings file
> {noformat}
>
>
>
>
>
>pattern="${repository.dir}/[organisation]/[module]/[branch]/[revision]/ivy.xml"/>
>pattern="${repository.dir}/[organisation]/[module]/[branch]/[revision]/[artifact].[ext]"/>
>
>
>
>
>
>
> {noformat}
> For all project in my organisation I want to use branch br-1. However, after
> I configure ivy, download the dependencies, build my project and I attempt to
> publish it, I receive the following output:
> {noformat}
> :: publishing :: claudia.homeunix.net#hwlib
> published hwlib to
> /Users/rambus/.ivyrepo/claudia.homeunix.net/hwlib/br-1/1.0.part/hwlib.jar
> published ivy to
> /Users/rambus/.ivyrepo/claudia.homeunix.net/hwlib/br-1/1.0.part/ivy.xml
> publish commited: moved
> /Users/rambus/.ivyrepo/claudia.homeunix.net/hwlib/1.0.part
> to /Users/rambus/.ivyrepo/claudia.homeunix.net/hwlib/1.0
> {noformat}
> I use the latest from trunk updated today.
> As it can be seen the artifacts are published to the repository, but when
> they are committed the branch is skipped from the URL - the directory
> /Users/rambus/.ivyrepo/claudia.homeunix.net/hwlib/1.0 does not exist at all.
> I traced the reason of this behaviour down to
> FileSystemResolver.initTransaction(ModuleRevisionId module). There it
> initializes from the artifact pattern defined in the settings file the
> transaction's temporary directory and the transaction's destination
> directory, respectively the String variables transactionTempDir and
> transactionDestDir. The patterns are substituted using
> IvyPatternHelper.substitute(String pattern, ModuleRevisionId moduleRevision)
> and the problem lies in this method - it does not use the branch.
> I am submitting a patch of FileSystemResolver that uses
> IvyPatternHelper.substitute(String pattern, String org, String module, String
> branch, String revision, String artifact, String type, String ext, String
> conf, ArtifactOrigin origin, Map extraAttributes)
> as this is the only method that uses the branch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches
[ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565941#action_12565941 ] Antoine Levy-Lambert commented on IVY-717: -- Hello Maarten, how do I specify my cache patterns ? Also, I found out that we have published in the branch 1 something which mentions a dependency to a module which is new in branch 2. This is the root cause of what I am explaining above. Cleaning the cache in this case does not help unfortunately. Regards, Antoine > ivy-resolve fails when a project has different dependencies in different > branches > - > > Key: IVY-717 > URL: https://issues.apache.org/jira/browse/IVY-717 > Project: Ivy > Issue Type: Bug > Components: Ant > Environment: Solaris, JDK 1.5 >Reporter: Antoine Levy-Lambert > Fix For: 2.0.0-alpha-2 > > > The scenario is the following : > we build on the same server the project foo or the organization wombat in two > branches called 1 and 2 > in branch 2 foo is dependent upon bar which is also from the organization > wombat > in branch 1 foo has no dependencies > if we do a build in the branch 2, then attempt to build in branch 1 without > cleaning the cache, we are getting an unresolved dependency to bar, which > does not exist in the branch 1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches
ivy-resolve fails when a project has different dependencies in different branches - Key: IVY-717 URL: https://issues.apache.org/jira/browse/IVY-717 Project: Ivy Issue Type: Bug Components: Ant Environment: Solaris, JDK 1.5 Reporter: Antoine Levy-Lambert Fix For: 2.0.0-alpha-2 The scenario is the following : we build on the same server the project foo or the organization wombat in two branches called 1 and 2 in branch 2 foo is dependent upon bar which is also from the organization wombat in branch 1 foo has no dependencies if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-716) repreport task not working against a repository structured by branches
[
https://issues.apache.org/jira/browse/IVY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565846#action_12565846
]
Antoine Levy-Lambert commented on IVY-716:
--
I think you might need a new class having as attributes the organization, the
module and the branch and use this one in the SearchEngine. What about
ModuleBranchId extends ModuleId ?
> repreport task not working against a repository structured by branches
> --
>
> Key: IVY-716
> URL: https://issues.apache.org/jira/browse/IVY-716
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-alpha-2
> Environment: Windows XP, IBM JDK 1.5
>Reporter: Antoine Levy-Lambert
>Assignee: Maarten Coene
>
> I am trying to use the repreport task like this
> revision="FOO_5.1.0.413" matcher="glob" />
> here are my settings :
>
> defaultBranch="${ivy.branch}"/>
>
>
>pattern="${repository.http.url}/[organisation]/[module]/[revision]/ivy.xml"/>
>pattern="${repository.http.url}/[organisation]/[module]/[revision]/[artifact].[ext]"/>
>
>
>pattern="${repository.http.url}/[organisation]/[branch]/[module]/[revision]/ivy.xml"/>
>pattern="${repository.http.url}/[organisation]/[branch]/[module]/[revision]/[artifact].[ext]"/>
>
>
>
>
>
>
> I see the following standard out :
> [ivy:repreport] :: problems summary ::
> [ivy:repreport] WARNINGS
> [ivy:repreport] problem while listing resources in
> http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri
> 'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
> [ivy:repreport] problem while listing resources in
> http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri
> 'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
> [ivy:repreport] problem while listing resources in
> http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri
> 'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
> [ivy:repreport] problem while listing resources in
> http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri
> 'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
> [ivy:repreport]
> Replacing [branch] by its value in my settings file is a workaround.
> Looking at the source code from SVN, it looks like public ModuleId[]
> listModules(ModuleId criteria, PatternMatcher matcher) {
> in org.apache.ivy.core.search.SearchEngine is involved in the work.
> Should a new version of listModules be created, having also a branch as
> parameter ?
> A more powerful solution might be to create a new class extending ModuleId,
> adding a branch field to the instance variables, and to code using this class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-716) repreport task not working against a repository structured by branches
repreport task not working against a repository structured by branches
--
Key: IVY-716
URL: https://issues.apache.org/jira/browse/IVY-716
Project: Ivy
Issue Type: Bug
Components: Ant
Affects Versions: 2.0.0-alpha-2
Environment: Windows XP, IBM JDK 1.5
Reporter: Antoine Levy-Lambert
I am trying to use the repreport task like this
here are my settings :
I see the following standard out :
[ivy:repreport] :: problems summary ::
[ivy:repreport] WARNINGS
[ivy:repreport] problem while listing resources in
http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
[ivy:repreport] java.lang.IllegalArgumentException Invalid uri
'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
[ivy:repreport] problem while listing resources in
http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
[ivy:repreport] java.lang.IllegalArgumentException Invalid uri
'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
[ivy:repreport] problem while listing resources in
http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
[ivy:repreport] java.lang.IllegalArgumentException Invalid uri
'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
[ivy:repreport] problem while listing resources in
http://ivyrepo:8060/ivyrepo/saic/[branch]/ with http-branch-resolver:
[ivy:repreport] java.lang.IllegalArgumentException Invalid uri
'http://ivyrepo:8060/ivyrepo/saic/[branch]/': escaped absolute path not valid
[ivy:repreport]
Replacing [branch] by its value in my settings file is a workaround.
Looking at the source code from SVN, it looks like public ModuleId[]
listModules(ModuleId criteria, PatternMatcher matcher) {
in org.apache.ivy.core.search.SearchEngine is involved in the work.
Should a new version of listModules be created, having also a branch as
parameter ?
A more powerful solution might be to create a new class extending ModuleId,
adding a branch field to the instance variables, and to code using this class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
