[jira] [Commented] (IVY-1502) Be a nice freedesktop citizen, move the ~/.ivy to the appropriate location
[ https://issues.apache.org/jira/browse/IVY-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844644#comment-17844644 ] Jaikiran Pai commented on IVY-1502: --- Just a note - the chances of any new features or enhancements or even regular bug fixes are very remote for reasons stated in https://www.mail-archive.com/dev@ant.apache.org/msg49479.html > Be a nice freedesktop citizen, move the ~/.ivy to the appropriate location > > > Key: IVY-1502 > URL: https://issues.apache.org/jira/browse/IVY-1502 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.3.0 > Environment: linux >Reporter: PerfectCarl >Priority: Minor > > According to the XDG specification [1], there is a better way to store the > user specific data of an application by dumping in new hidden folder in ~/. > More information about it can be found [2] > The specification defines places to store the data so that the user profile > can be updated and moved properly while reducing some weird bugs. > Those places would be ~/.local/ivy or ~/.cache/ivy and other (depending on > the data stored) > [1]: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html > [2]: https://ploum.net/207-modify-your-application-to-use-xdg-folders/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1502) Be a nice freedesktop citizen, move the ~/.ivy to the appropriate location
[ https://issues.apache.org/jira/browse/IVY-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843840#comment-17843840 ] Ignacio Taranto commented on IVY-1502: -- Until this is properly implemented, is there any config flag I can add to `JAVA_TOOL_OPTIONS` (or similar) to change ivy's directory? > Be a nice freedesktop citizen, move the ~/.ivy to the appropriate location > > > Key: IVY-1502 > URL: https://issues.apache.org/jira/browse/IVY-1502 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.3.0 > Environment: linux >Reporter: PerfectCarl >Priority: Minor > > According to the XDG specification [1], there is a better way to store the > user specific data of an application by dumping in new hidden folder in ~/. > More information about it can be found [2] > The specification defines places to store the data so that the user profile > can be updated and moved properly while reducing some weird bugs. > Those places would be ~/.local/ivy or ~/.cache/ivy and other (depending on > the data stored) > [1]: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html > [2]: https://ploum.net/207-modify-your-application-to-use-xdg-folders/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1651) Augment 'Child elements’ section of 'File System Resolver' documentation
[ https://issues.apache.org/jira/browse/IVY-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826781#comment-17826781 ] Lewis John McGibbney commented on IVY-1651: --- PR available at [https://github.com/apache/ant-ivy/pull/101] > Augment 'Child elements’ section of 'File System Resolver' documentation > > > Key: IVY-1651 > URL: https://issues.apache.org/jira/browse/IVY-1651 > Project: Ivy > Issue Type: Improvement > Components: Documentation, Maven Compatibility >Reporter: Lewis John McGibbney >Priority: Trivial > Fix For: 2.5.3 > > Time Spent: 10m > Remaining Estimate: 0h > > I [recently encountered some > confusion|[https://lists.apache.org/thread/tzvtw4j2d9pcxhqjxyb2dwnsk50t47b5]] > when upgrading from Ivy 2.5.0 —> 2.5.2. > I think the documentation at > [https://ant.apache.org/ivy/history/2.5.2/resolver/filesystem.html#_child_elements] > could be augmented to atleast link back to the [Maven > documentation|[https://maven.apache.org/pom.html#dependencies]] which > explicitly references acceptable constituent values for the resolver pattern. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVY-1651) Augment 'Child elements’ section of 'File System Resolver' documentation
Lewis John McGibbney created IVY-1651: - Summary: Augment 'Child elements’ section of 'File System Resolver' documentation Key: IVY-1651 URL: https://issues.apache.org/jira/browse/IVY-1651 Project: Ivy Issue Type: Improvement Components: Documentation, Maven Compatibility Reporter: Lewis John McGibbney Fix For: 2.5.3 I [recently encountered some confusion|[https://lists.apache.org/thread/tzvtw4j2d9pcxhqjxyb2dwnsk50t47b5]] when upgrading from Ivy 2.5.0 —> 2.5.2. I think the documentation at [https://ant.apache.org/ivy/history/2.5.2/resolver/filesystem.html#_child_elements] could be augmented to atleast link back to the [Maven documentation|[https://maven.apache.org/pom.html#dependencies]] which explicitly references acceptable constituent values for the resolver pattern. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1649) Caching is broken when using ibiblio resolver with usepoms="false" or url resolver in combination with classifiers
[
https://issues.apache.org/jira/browse/IVY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817713#comment-17817713
]
Moritz Baumann commented on IVY-1649:
-
PR: https://github.com/apache/ant-ivy/pull/100
> Caching is broken when using ibiblio resolver with usepoms="false" or url
> resolver in combination with classifiers
> --
>
> Key: IVY-1649
> URL: https://issues.apache.org/jira/browse/IVY-1649
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Moritz Baumann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I'm trying to use Ivy as a standalone tool from a custom build system. One of
> my use cases requires me to download certain artifacts from Maven
> repositories *without* performing dependency resolution. To avoid any
> unnecessary HTTP traffic, I tried using a settings file similar to the
> following:
> {code:xml}
>
>
> root="https://repo1.maven.org/maven2/"/>
>
>
>
> {code}
> Let's assume a simple ivy.xml:
> {code:xml}
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;
> xmlns:m="http://ant.apache.org/ivy/maven;>
>
>
>
>
>
>
>
> {code}
> The first execution of ivy looks okay, but subsequent invocations still
> access the repository:
> {noformat}
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
> :: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
> :: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
> confs: [default]
> found junit#junit;4.13.2 in maven2
> downloading
> https://repo1.maven.org/maven2/junit/junit/4.13.2/junit-4.13.2-javadoc.jar ...
> .
> (1635kB)
> .. (0kB)
> [SUCCESSFUL ] junit#junit;4.13.2!junit.jar (305ms)
> :: resolution report :: resolve 554ms :: artifacts dl 306ms
> -
> | |modules|| artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 1 | 0 | 0 || 1 | 1 |
> -
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
> :: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
> :: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
> confs: [default]
> found junit#junit;4.13.2 in maven2
> :: resolution report :: resolve 337ms :: artifacts dl 3ms
> -
> | |modules|| artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 1 | 0 | 0 || 1 | 0 |
>
> -{noformat}
> Without internet access (offline build), dependency resolution fails despite
> all dependencies being in the cache, and running ivy with debug messages
> enabled reveals the culprit:
> {noformat}
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml -debug
> […]
> No entry is found in the ModuleDescriptorCache :
> /home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
> post 1.3 ivy file: using exact as default matcher
> problem while parsing cached ivy file for: junit#junit;4.13.2
> (java.text.ParseException: [xml parsing: ivy-4.13.2.xml:14:84:
> cvc-complex-type.3.2.2: Attribute 'classifier' is not allowed to appear in
> element 'artifact'. in file:/home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
> ])
> java.text.ParseException: [xml parsing: ivy-4.13.2.xml:14:84:
> cvc-complex-type.3.2.2: Attribute 'classifier' is not allowed to appear in
> element 'artifact'. in file:/home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
> ]
> at
> org.apache.ivy.plugins.parser.
[jira] [Commented] (IVY-1649) Caching is broken when using ibiblio resolver with usepoms="false" or url resolver in combination with classifiers
[
https://issues.apache.org/jira/browse/IVY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817701#comment-17817701
]
Moritz Baumann commented on IVY-1649:
-
After replacing {{artifact.getExtraAttributes()}} with
{{artifact.getQualifiedExtraAttributes()}} in
{{DefaultModuleDescriptor#newDefaultInstance}}, only IVY-1650 remains, which is
easy to work around. With that patch applied, all that's left to figure out is
how to properly pass through all attribute namespaces - those are already
forgotten by the time {{DefaultModuleDescriptor#newDefaultInstance}} gets
called.
> Caching is broken when using ibiblio resolver with usepoms="false" or url
> resolver in combination with classifiers
> --
>
> Key: IVY-1649
> URL: https://issues.apache.org/jira/browse/IVY-1649
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Moritz Baumann
>Priority: Major
>
> I'm trying to use Ivy as a standalone tool from a custom build system. One of
> my use cases requires me to download certain artifacts from Maven
> repositories *without* performing dependency resolution. To avoid any
> unnecessary HTTP traffic, I tried using a settings file similar to the
> following:
> {code:xml}
>
>
> root="https://repo1.maven.org/maven2/"/>
>
>
>
> {code}
> Let's assume a simple ivy.xml:
> {code:xml}
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;
> xmlns:m="http://ant.apache.org/ivy/maven;>
>
>
>
>
>
>
>
> {code}
> The first execution of ivy looks okay, but subsequent invocations still
> access the repository:
> {noformat}
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
> :: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
> :: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
> confs: [default]
> found junit#junit;4.13.2 in maven2
> downloading
> https://repo1.maven.org/maven2/junit/junit/4.13.2/junit-4.13.2-javadoc.jar ...
> .
> (1635kB)
> .. (0kB)
> [SUCCESSFUL ] junit#junit;4.13.2!junit.jar (305ms)
> :: resolution report :: resolve 554ms :: artifacts dl 306ms
> -
> | |modules|| artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 1 | 0 | 0 || 1 | 1 |
> -
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
> :: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
> :: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
> confs: [default]
> found junit#junit;4.13.2 in maven2
> :: resolution report :: resolve 337ms :: artifacts dl 3ms
> -
> | |modules|| artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 1 | 0 | 0 || 1 | 0 |
>
> -{noformat}
> Without internet access (offline build), dependency resolution fails despite
> all dependencies being in the cache, and running ivy with debug messages
> enabled reveals the culprit:
> {noformat}
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml -debug
> […]
> No entry is found in the ModuleDescriptorCache :
> /home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
> post 1.3 ivy file: using exact as default matcher
> problem while parsing cached ivy file for: junit#junit;4.13.2
> (java.text.ParseException: [xml parsing: ivy-4.13.2.xml:14:84:
> cvc-complex-type.3.2.2: Attribute 'classifier' is not allowed to appear in
> element
[jira] [Commented] (IVY-1649) Caching is broken when using ibiblio resolver with usepoms="false" or url resolver in combination with classifiers
[
https://issues.apache.org/jira/browse/IVY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817697#comment-17817697
]
Moritz Baumann commented on IVY-1649:
-
The source of the bug is in
{{org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor#newDefaultInstance(org.apache.ivy.core.module.id.ModuleRevisionId,
org.apache.ivy.core.module.descriptor.DependencyArtifactDescriptor[])}}. When
converting a
{{org.apache.ivy.core.module.descriptor.DependencyArtifactDescriptor}} to a
{{org.apache.ivy.core.module.descriptor.MDArtifact}}, the namespaces of the
extra attributes are forgotten, so the
{{org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorWriter}} cannot write a
correct module descriptor to the cache despite its best efforts.
> Caching is broken when using ibiblio resolver with usepoms="false" or url
> resolver in combination with classifiers
> --
>
> Key: IVY-1649
> URL: https://issues.apache.org/jira/browse/IVY-1649
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Moritz Baumann
>Priority: Major
>
> I'm trying to use Ivy as a standalone tool from a custom build system. One of
> my use cases requires me to download certain artifacts from Maven
> repositories *without* performing dependency resolution. To avoid any
> unnecessary HTTP traffic, I tried using a settings file similar to the
> following:
> {code:xml}
>
>
> root="https://repo1.maven.org/maven2/"/>
>
>
>
> {code}
> Let's assume a simple ivy.xml:
> {code:xml}
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;
> xmlns:m="http://ant.apache.org/ivy/maven;>
>
>
>
>
>
>
>
> {code}
> The first execution of ivy looks okay, but subsequent invocations still
> access the repository:
> {noformat}
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
> :: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
> :: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
> confs: [default]
> found junit#junit;4.13.2 in maven2
> downloading
> https://repo1.maven.org/maven2/junit/junit/4.13.2/junit-4.13.2-javadoc.jar ...
> .
> (1635kB)
> .. (0kB)
> [SUCCESSFUL ] junit#junit;4.13.2!junit.jar (305ms)
> :: resolution report :: resolve 554ms :: artifacts dl 306ms
> -
> | |modules|| artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 1 | 0 | 0 || 1 | 1 |
> -
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
> :: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
> :: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
> confs: [default]
> found junit#junit;4.13.2 in maven2
> :: resolution report :: resolve 337ms :: artifacts dl 3ms
> -
> | |modules|| artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 1 | 0 | 0 || 1 | 0 |
>
> -{noformat}
> Without internet access (offline build), dependency resolution fails despite
> all dependencies being in the cache, and running ivy with debug messages
> enabled reveals the culprit:
> {noformat}
> ❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml -debug
> […]
> No entry is found in the ModuleDescriptorCache :
> /home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
> post 1.3 ivy file: using exact as default matcher
> problem while parsing cached ivy file for: junit#junit;4.13.2
> (java.text.ParseException: [xml parsing: ivy-4.13.2.xml:14:84:
[jira] [Created] (IVY-1650) Caching is broken when using custom attributes from the http://ant.apache.org/ivy/extra namespace
Moritz Baumann created IVY-1650:
---
Summary: Caching is broken when using custom attributes from the
http://ant.apache.org/ivy/extra namespace
Key: IVY-1650
URL: https://issues.apache.org/jira/browse/IVY-1650
Project: Ivy
Issue Type: Bug
Affects Versions: 2.5.2
Reporter: Moritz Baumann
This bug is similar to IVY-1649.
I'm trying to use Ivy as a standalone tool from a custom build system. While
most of the artifacts I want to download are located in Maven repositories, I
also need to download some npm artifacts. To avoid having to invoke npm just
for those few artifacts, I defined a url resolver for npm artifacts, similar to
the following:
{code:xml}
https://repo1.maven.org/maven2/"/>
https://registry.npmjs.org/([organisation]/)[module]/-/[artifact]-[revision].[ext]"/>
{code}
For npm artifacts, I specify the custom repotype attribute to make sure the
correct resolver is chosen:
{code:xml}
http://www.w3.org/2001/XMLSchema-instance;
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;
xmlns:e="http://ant.apache.org/ivy/extra;>
{code}
Like in IVY-1649, the first execution of ivy looks okay, but subsequent
invocations still access the repository:
{noformat}
❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
:: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
:: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
confs: [default]
found @cap-js#cds-types;0.2.0 in npm
downloading https://registry.npmjs.org/@cap-js/cds-types/-/cds-types-0.2.0.tgz
...
.. (22kB)
[SUCCESSFUL ] @cap-js#cds-types;0.2.0!cds-types.tgz (444ms)
:: resolution report :: resolve 1132ms :: artifacts dl 447ms
-
| |modules|| artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
-
| default | 1 | 1 | 0 | 0 || 1 | 1 |
-
❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
:: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
:: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
confs: [default]
found @cap-js#cds-types;0.2.0 in npm
:: resolution report :: resolve 423ms :: artifacts dl 2ms
-
| |modules|| artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
-
| default | 1 | 1 | 0 | 0 || 1 | 0 |
-
{noformat}
Offline builds fail even with a populated cache. The root cause is very similar
to the one in IVY-1649:
{noformat}
❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml -debug
[…]
No entry is found in the ModuleDescriptorCache :
/home/mb-sc/.ivy2/cache/@cap-js/cds-types/ivy-0.2.0.xml
post 1.3 ivy file: using exact as default matcher
problem while parsing cached ivy file for: @cap-js#cds-types;0.2.0
(java.text.ParseException: [[Fatal Error] ivy-0.2.0.xml:10:4: The prefix "e"
for attribute "e:repotype" associated with an element type "info" is not bound.
in file:/home/mb-sc/.ivy2/cache/@cap-js/cds-types/ivy-0.2.0.xml
])
java.text.ParseException: [[Fatal Error] ivy-0.2.0.xml:10:4: The prefix "e" for
attribute "e:repotype" associated with an element type "info" is not bound. in
file:/home/mb-sc/.ivy2/cache/@cap-js/cds-types/ivy-0.2.0.xml
]
at
org.apache.ivy.plugins.parser.AbstractModuleDescriptorParser$AbstractParser.checkErrors(AbstractModuleDescriptorParser.java:90)
at
org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser$Parser.parse(XmlModuleDescriptorParser.java:337)
at
org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser.parseDescriptor(XmlModuleDescriptorParser.java:128)
at
org.apache.ivy.plugins.parser.AbstractModuleDescriptorParser.parseDescriptor(AbstractModuleDescriptorParser.java:50)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:846)
at
org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)
at
org.
[jira] [Created] (IVY-1649) Caching is broken when using ibiblio resolver with usepoms="false" or url resolver in combination with classifiers
Moritz Baumann created IVY-1649:
---
Summary: Caching is broken when using ibiblio resolver with
usepoms="false" or url resolver in combination with classifiers
Key: IVY-1649
URL: https://issues.apache.org/jira/browse/IVY-1649
Project: Ivy
Issue Type: Bug
Affects Versions: 2.5.2
Reporter: Moritz Baumann
I'm trying to use Ivy as a standalone tool from a custom build system. One of
my use cases requires me to download certain artifacts from Maven repositories
*without* performing dependency resolution. To avoid any unnecessary HTTP
traffic, I tried using a settings file similar to the following:
{code:xml}
https://repo1.maven.org/maven2/"/>
{code}
Let's assume a simple ivy.xml:
{code:xml}
http://www.w3.org/2001/XMLSchema-instance;
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd;
xmlns:m="http://ant.apache.org/ivy/maven;>
{code}
The first execution of ivy looks okay, but subsequent invocations still access
the repository:
{noformat}
❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
:: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
:: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
confs: [default]
found junit#junit;4.13.2 in maven2
downloading
https://repo1.maven.org/maven2/junit/junit/4.13.2/junit-4.13.2-javadoc.jar ...
.
(1635kB)
.. (0kB)
[SUCCESSFUL ] junit#junit;4.13.2!junit.jar (305ms)
:: resolution report :: resolve 554ms :: artifacts dl 306ms
-
| |modules|| artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
-
| default | 1 | 1 | 0 | 0 || 1 | 1 |
-
❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml
:: loading settings :: file = /home/mb-sc/ivy-test/ivysettings.xml
:: resolving dependencies :: mb-sc#demo;working@W-GNV1FB3
confs: [default]
found junit#junit;4.13.2 in maven2
:: resolution report :: resolve 337ms :: artifacts dl 3ms
-
| |modules|| artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
-
| default | 1 | 1 | 0 | 0 || 1 | 0 |
-{noformat}
Without internet access (offline build), dependency resolution fails despite
all dependencies being in the cache, and running ivy with debug messages
enabled reveals the culprit:
{noformat}
❯ java -jar apache-ivy-2.5.2/ivy-2.5.2.jar -settings ivysettings.xml -debug
[…]
No entry is found in the ModuleDescriptorCache :
/home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
post 1.3 ivy file: using exact as default matcher
problem while parsing cached ivy file for: junit#junit;4.13.2
(java.text.ParseException: [xml parsing: ivy-4.13.2.xml:14:84:
cvc-complex-type.3.2.2: Attribute 'classifier' is not allowed to appear in
element 'artifact'. in file:/home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
])
java.text.ParseException: [xml parsing: ivy-4.13.2.xml:14:84:
cvc-complex-type.3.2.2: Attribute 'classifier' is not allowed to appear in
element 'artifact'. in file:/home/mb-sc/.ivy2/cache/junit/junit/ivy-4.13.2.xml
]
at
org.apache.ivy.plugins.parser.AbstractModuleDescriptorParser$AbstractParser.checkErrors(AbstractModuleDescriptorParser.java:90)
at
org.apache.ivy.plugins.parser.AbstractModuleDescriptorParser$AbstractParser.getModuleDescriptor(AbstractModuleDescriptorParser.java:343)
at
org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser$Parser.getModuleDescriptor(XmlModuleDescriptorParser.java:189)
at
org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser.parseDescriptor(XmlModuleDescriptorParser.java:129)
at
org.apache.ivy.plugins.parser.AbstractModuleDescriptorParser.parseDescriptor(AbstractModuleDescriptorParser.java:50)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:846)
at
org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(Modu
[jira] [Updated] (IVYDE-397) IvyDE Updatesite Jenkins job broken and documentation out of date
[ https://issues.apache.org/jira/browse/IVYDE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathon Lamon updated IVYDE-397: - Description: The Jenkins job for the IvyDE update site has been broken for awhile. It appears to be broken due to the reorganization of things on the Jenkins site. All the documentation pointing to the old build is now incorrect. There has been no successful build since the reorganization, so it is impossible to download 2.3.0-rc1 plugin. was: The Jenkins job for the IvyDE update site has been broken for awhile. It appears to be broken due to the reorganization of things on the Jenkins site. All the documentation pointing to the old build is now incorrect. There has been no successful build since the reorganization, so it is impossible to download 2.6.0-rc1 plugin. > IvyDE Updatesite Jenkins job broken and documentation out of date > - > > Key: IVYDE-397 > URL: https://issues.apache.org/jira/browse/IVYDE-397 > Project: IvyDE > Issue Type: Bug >Affects Versions: master >Reporter: Jonathon Lamon >Priority: Major > Fix For: master > > > The Jenkins job for the IvyDE update site has been broken for awhile. It > appears to be broken due to the reorganization of things on the Jenkins site. > > All the documentation pointing to the old build is now incorrect. > > There has been no successful build since the reorganization, so it is > impossible to download 2.3.0-rc1 plugin. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVYDE-397) IvyDE Updatesite Jenkins job broken and documentation out of date
Jonathon Lamon created IVYDE-397: Summary: IvyDE Updatesite Jenkins job broken and documentation out of date Key: IVYDE-397 URL: https://issues.apache.org/jira/browse/IVYDE-397 Project: IvyDE Issue Type: Bug Affects Versions: master Reporter: Jonathon Lamon Fix For: master The Jenkins job for the IvyDE update site has been broken for awhile. It appears to be broken due to the reorganization of things on the Jenkins site. All the documentation pointing to the old build is now incorrect. There has been no successful build since the reorganization, so it is impossible to download 2.6.0-rc1 plugin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1647) Setting features and properties for XMLReader may throw
[ https://issues.apache.org/jira/browse/IVY-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765728#comment-17765728 ] Antoine POURCHEZ commented on IVY-1647: --- Thank you so much [~bodewig] ! > Setting features and properties for XMLReader may throw > --- > > Key: IVY-1647 > URL: https://issues.apache.org/jira/browse/IVY-1647 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.5.2 >Reporter: Stefan Bodewig >Assignee: Stefan Bodewig >Priority: Major > Fix For: 2.5.3 > > > see > https://github.com/apache/ant-ivy/commit/2be17bc18b0e1d4123007d579e43ba1a4b6fab3d#commitcomment-127113717 > setting the features and properties for XMLReader may need to be protected in > a way similar to the code setting features and attributes for factories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IVY-1648) Some Unit Tests fail on Java8
[ https://issues.apache.org/jira/browse/IVY-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved IVY-1648. - Resolution: Fixed see https://github.com/apache/ant-ivy/commit/503aafc594b777ffb035a457ed341e31334c23a4 > Some Unit Tests fail on Java8 > - > > Key: IVY-1648 > URL: https://issues.apache.org/jira/browse/IVY-1648 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.5.2 >Reporter: Stefan Bodewig >Priority: Major > Fix For: 2.5.3 > > > While porting changes from Ivy to SBT's fork Adrien Piquerez found some > issues with running tests on Java8 (see https://github.com/sbt/ivy/pull/46 ). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVY-1648) Some Unit Tests fail on Java8
Stefan Bodewig created IVY-1648: --- Summary: Some Unit Tests fail on Java8 Key: IVY-1648 URL: https://issues.apache.org/jira/browse/IVY-1648 Project: Ivy Issue Type: Bug Components: Core Affects Versions: 2.5.2 Reporter: Stefan Bodewig Fix For: 2.5.3 While porting changes from Ivy to SBT's fork Adrien Piquerez found some issues with running tests on Java8 (see https://github.com/sbt/ivy/pull/46 ). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IVY-1647) Setting features and properties for XMLReader may throw
[ https://issues.apache.org/jira/browse/IVY-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved IVY-1647. - Resolution: Fixed fixed with https://github.com/apache/ant-ivy/commit/5d69c9a5447d32780e5c11f65a44b853647abdf4 > Setting features and properties for XMLReader may throw > --- > > Key: IVY-1647 > URL: https://issues.apache.org/jira/browse/IVY-1647 > Project: Ivy > Issue Type: Bug > Components: Core >Affects Versions: 2.5.2 >Reporter: Stefan Bodewig >Assignee: Stefan Bodewig >Priority: Major > Fix For: 2.5.3 > > > see > https://github.com/apache/ant-ivy/commit/2be17bc18b0e1d4123007d579e43ba1a4b6fab3d#commitcomment-127113717 > setting the features and properties for XMLReader may need to be protected in > a way similar to the code setting features and attributes for factories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVY-1647) Setting features and properties for XMLReader may throw
Stefan Bodewig created IVY-1647: --- Summary: Setting features and properties for XMLReader may throw Key: IVY-1647 URL: https://issues.apache.org/jira/browse/IVY-1647 Project: Ivy Issue Type: Bug Components: Core Affects Versions: 2.5.2 Reporter: Stefan Bodewig Assignee: Stefan Bodewig Fix For: 2.5.3 see https://github.com/apache/ant-ivy/commit/2be17bc18b0e1d4123007d579e43ba1a4b6fab3d#commitcomment-127113717 setting the features and properties for XMLReader may need to be protected in a way similar to the code setting features and attributes for factories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IVY-1646) Redundant codes in VsftpRepository.sendCommand?
[
https://issues.apache.org/jira/browse/IVY-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Letian Yuan closed IVY-1646.
Resolution: Not A Problem
"use of alone commands does not work properly due to a long delay between end
of process and end of stream..."
Fine, it aims to deal with some extreme cases.
> Redundant codes in VsftpRepository.sendCommand?
>
>
> Key: IVY-1646
> URL: https://issues.apache.org/jira/browse/IVY-1646
> Project: Ivy
> Issue Type: Question
> Components: Core, Maven Compatibility
>Reporter: Letian Yuan
>Priority: Major
> Attachments: 1.png
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> There's a method
> {*}org.apache.ivy.plugins.repository.vsftp.VsftpRepository.sendCommand(String,
> boolean, boolean, long){*}.
> !1.png!
> My question is, under what circumstances, *this.sendSingleCommand(command)*
> will be executed. It seems variable *single* is always false.
>
> So, are these redundant codes or am I wrong?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1646) Redundant codes in VsftpRepository.sendCommand?
[
https://issues.apache.org/jira/browse/IVY-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Letian Yuan updated IVY-1646:
-
Component/s: Core
Maven Compatibility
> Redundant codes in VsftpRepository.sendCommand?
>
>
> Key: IVY-1646
> URL: https://issues.apache.org/jira/browse/IVY-1646
> Project: Ivy
> Issue Type: Question
> Components: Core, Maven Compatibility
>Reporter: Letian Yuan
>Priority: Major
> Attachments: 1.png
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> There's a method
> {*}org.apache.ivy.plugins.repository.vsftp.VsftpRepository.sendCommand(String,
> boolean, boolean, long){*}.
> !1.png!
> My question is, under what circumstances, *this.sendSingleCommand(command)*
> will be executed. It seems variable *single* is always false.
>
> So, are these redundant codes or am I wrong?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1646) Redundant codes in VsftpRepository.sendCommand?
[
https://issues.apache.org/jira/browse/IVY-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Letian Yuan updated IVY-1646:
-
Priority: Major (was: Minor)
> Redundant codes in VsftpRepository.sendCommand?
>
>
> Key: IVY-1646
> URL: https://issues.apache.org/jira/browse/IVY-1646
> Project: Ivy
> Issue Type: Question
>Reporter: Letian Yuan
>Priority: Major
> Attachments: 1.png
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> There's a method
> {*}org.apache.ivy.plugins.repository.vsftp.VsftpRepository.sendCommand(String,
> boolean, boolean, long){*}.
> !1.png!
> My question is, under what circumstances, *this.sendSingleCommand(command)*
> will be executed. It seems variable *single* is always false.
>
> So, are these redundant codes or am I wrong?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IVY-1646) Redundant codes in VsftpRepository.sendCommand?
Letian Yuan created IVY-1646:
Summary: Redundant codes in VsftpRepository.sendCommand?
Key: IVY-1646
URL: https://issues.apache.org/jira/browse/IVY-1646
Project: Ivy
Issue Type: Question
Reporter: Letian Yuan
Attachments: 1.png
There's a method
{*}org.apache.ivy.plugins.repository.vsftp.VsftpRepository.sendCommand(String,
boolean, boolean, long){*}.
!1.png!
My question is, under what circumstances, *this.sendSingleCommand(command)*
will be executed. It seems variable *single* is always false.
So, are these redundant codes or am I wrong?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1645) Ivy does not support programmatically resolving artifacts from private maven repositories
[ https://issues.apache.org/jira/browse/IVY-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] junyuc25 updated IVY-1645: -- Description: While we could use IBiblioResolver to retrieve artifacts from Maven central programmatically ([example here|https://stackoverflow.com/questions/15598612/simplest-ivy-code-to-programmatically-retrieve-dependency-from-maven-central]), Ivy does not seem to support retrieving dependencies from private Maven repository owned by organizations which are usually protected with user name and password. It would be great if Ivy could add support for such use cases. (was: While we could use IBiblioResolver to retrieve artifacts from Maven central ([example here|https://stackoverflow.com/questions/15598612/simplest-ivy-code-to-programmatically-retrieve-dependency-from-maven-central]), Ivy does not seem to support retrieving dependencies from private Maven repository owned by organizations which are usually protected with user name and password. It would be great if Ivy could add support for such use cases.) > Ivy does not support programmatically resolving artifacts from private maven > repositories > -- > > Key: IVY-1645 > URL: https://issues.apache.org/jira/browse/IVY-1645 > Project: Ivy > Issue Type: Improvement > Components: Core, Maven Compatibility >Affects Versions: 2.5.1 >Reporter: junyuc25 >Priority: Major > > While we could use IBiblioResolver to retrieve artifacts from Maven central > programmatically ([example > here|https://stackoverflow.com/questions/15598612/simplest-ivy-code-to-programmatically-retrieve-dependency-from-maven-central]), > Ivy does not seem to support retrieving dependencies from private Maven > repository owned by organizations which are usually protected with user name > and password. It would be great if Ivy could add support for such use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVY-1645) Ivy does not support programmatically resolving artifacts from private maven repositories
[ https://issues.apache.org/jira/browse/IVY-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] junyuc25 updated IVY-1645: -- Description: While we could use IBiblioResolver to retrieve artifacts from Maven central programmatically ([example here|https://stackoverflow.com/questions/15598612/simplest-ivy-code-to-programmatically-retrieve-dependency-from-maven-central]), Ivy does not seem to support retrieving dependencies from private Maven repository owned by organizations, which are usually protected with user name and password. It would be great if Ivy could add support for such use cases. (was: While we could use IBiblioResolver to retrieve artifacts from Maven central programmatically ([example here|https://stackoverflow.com/questions/15598612/simplest-ivy-code-to-programmatically-retrieve-dependency-from-maven-central]), Ivy does not seem to support retrieving dependencies from private Maven repository owned by organizations which are usually protected with user name and password. It would be great if Ivy could add support for such use cases.) > Ivy does not support programmatically resolving artifacts from private maven > repositories > -- > > Key: IVY-1645 > URL: https://issues.apache.org/jira/browse/IVY-1645 > Project: Ivy > Issue Type: Improvement > Components: Core, Maven Compatibility >Affects Versions: 2.5.1 >Reporter: junyuc25 >Priority: Major > > While we could use IBiblioResolver to retrieve artifacts from Maven central > programmatically ([example > here|https://stackoverflow.com/questions/15598612/simplest-ivy-code-to-programmatically-retrieve-dependency-from-maven-central]), > Ivy does not seem to support retrieving dependencies from private Maven > repository owned by organizations, which are usually protected with user name > and password. It would be great if Ivy could add support for such use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVY-1645) Ivy does not support programmatically resolving artifacts from private maven repositories
junyuc25 created IVY-1645: - Summary: Ivy does not support programmatically resolving artifacts from private maven repositories Key: IVY-1645 URL: https://issues.apache.org/jira/browse/IVY-1645 Project: Ivy Issue Type: Improvement Components: Core, Maven Compatibility Affects Versions: 2.5.1 Reporter: junyuc25 While we could use IBiblioResolver to retrieve artifacts from Maven central ([example here|https://stackoverflow.com/questions/15598612/simplest-ivy-code-to-programmatically-retrieve-dependency-from-maven-central]), Ivy does not seem to support retrieving dependencies from private Maven repository owned by organizations which are usually protected with user name and password. It would be great if Ivy could add support for such use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IVY-1644) Upgrade httpclient to 4.5.13
[ https://issues.apache.org/jira/browse/IVY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved IVY-1644. -- Resolution: Fixed > Upgrade httpclient to 4.5.13 > > > Key: IVY-1644 > URL: https://issues.apache.org/jira/browse/IVY-1644 > Project: Ivy > Issue Type: Dependency upgrade > Components: Core >Affects Versions: 2.5.1 >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.5.2 > > > The apache ivy 4.5.1 release comes with 4.5.10 version of the http client > httpclient-4.5.10.jar > httpcore-4.4.12.jar > > org.apache.httpcomponents > httpclient > 4.5.10 > > It would be good to upgrade to 4.5.13 to fix CVEs > If you manual upgrade then you have an ugly WARN from apache ivy > Exception in thread "ivy-httpclient-shutdown-handler" > java.lang.NoClassDefFoundError: > org/apache/http/impl/conn/PoolingHttpClientConnectionManager$2 > at > org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:413) > at > org.apache.http.impl.client.HttpClientBuilder$2.close(HttpClientBuilder.java:1244) > at > org.apache.http.impl.client.InternalHttpClient.close(InternalHttpClient.java:201) > at > org.apache.ivy.util.url.HttpClientHandler.close(HttpClientHandler.java:357) > at > org.apache.ivy.util.url.HttpClientHandler$1.run(HttpClientHandler.java:84) > at java.base/java.lang.Thread.run(Thread.java:833) > Caused by: java.lang.ClassNotFoundException: > org.apache.http.impl.conn.PoolingHttpClientConnectionManager$2 > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1644) Upgrade httpclient to 4.5.13
[ https://issues.apache.org/jira/browse/IVY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735669#comment-17735669 ] Claus Ibsen commented on IVY-1644: -- Thanks Stefan for the heads up. Looking forward to a 2.5.2 release, thanks. > Upgrade httpclient to 4.5.13 > > > Key: IVY-1644 > URL: https://issues.apache.org/jira/browse/IVY-1644 > Project: Ivy > Issue Type: Dependency upgrade > Components: Core >Affects Versions: 2.5.1 >Reporter: Claus Ibsen >Priority: Major > > The apache ivy 4.5.1 release comes with 4.5.10 version of the http client > httpclient-4.5.10.jar > httpcore-4.4.12.jar > > org.apache.httpcomponents > httpclient > 4.5.10 > > It would be good to upgrade to 4.5.13 to fix CVEs > If you manual upgrade then you have an ugly WARN from apache ivy > Exception in thread "ivy-httpclient-shutdown-handler" > java.lang.NoClassDefFoundError: > org/apache/http/impl/conn/PoolingHttpClientConnectionManager$2 > at > org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:413) > at > org.apache.http.impl.client.HttpClientBuilder$2.close(HttpClientBuilder.java:1244) > at > org.apache.http.impl.client.InternalHttpClient.close(InternalHttpClient.java:201) > at > org.apache.ivy.util.url.HttpClientHandler.close(HttpClientHandler.java:357) > at > org.apache.ivy.util.url.HttpClientHandler$1.run(HttpClientHandler.java:84) > at java.base/java.lang.Thread.run(Thread.java:833) > Caused by: java.lang.ClassNotFoundException: > org.apache.http.impl.conn.PoolingHttpClientConnectionManager$2 > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVY-1644) Upgrade httpclient to 4.5.13
[ https://issues.apache.org/jira/browse/IVY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated IVY-1644: - Fix Version/s: 2.5.2 > Upgrade httpclient to 4.5.13 > > > Key: IVY-1644 > URL: https://issues.apache.org/jira/browse/IVY-1644 > Project: Ivy > Issue Type: Dependency upgrade > Components: Core >Affects Versions: 2.5.1 >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.5.2 > > > The apache ivy 4.5.1 release comes with 4.5.10 version of the http client > httpclient-4.5.10.jar > httpcore-4.4.12.jar > > org.apache.httpcomponents > httpclient > 4.5.10 > > It would be good to upgrade to 4.5.13 to fix CVEs > If you manual upgrade then you have an ugly WARN from apache ivy > Exception in thread "ivy-httpclient-shutdown-handler" > java.lang.NoClassDefFoundError: > org/apache/http/impl/conn/PoolingHttpClientConnectionManager$2 > at > org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:413) > at > org.apache.http.impl.client.HttpClientBuilder$2.close(HttpClientBuilder.java:1244) > at > org.apache.http.impl.client.InternalHttpClient.close(InternalHttpClient.java:201) > at > org.apache.ivy.util.url.HttpClientHandler.close(HttpClientHandler.java:357) > at > org.apache.ivy.util.url.HttpClientHandler$1.run(HttpClientHandler.java:84) > at java.base/java.lang.Thread.run(Thread.java:833) > Caused by: java.lang.ClassNotFoundException: > org.apache.http.impl.conn.PoolingHttpClientConnectionManager$2 > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1644) Upgrade httpclient to 4.5.13
[ https://issues.apache.org/jira/browse/IVY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735667#comment-17735667 ] Stefan Bodewig commented on IVY-1644: - Thank you Claus, Ivy's master already uses HttpClient 4.5.13 (see https://github.com/apache/ant-ivy/blob/master/version.properties ) . There is no explicit dependency in either commons-codec nor httpcore AFAICS, so we transitively get whatever httpclient depends on, I guess. > Upgrade httpclient to 4.5.13 > > > Key: IVY-1644 > URL: https://issues.apache.org/jira/browse/IVY-1644 > Project: Ivy > Issue Type: Dependency upgrade > Components: Core >Affects Versions: 2.5.1 >Reporter: Claus Ibsen >Priority: Major > > The apache ivy 4.5.1 release comes with 4.5.10 version of the http client > httpclient-4.5.10.jar > httpcore-4.4.12.jar > > org.apache.httpcomponents > httpclient > 4.5.10 > > It would be good to upgrade to 4.5.13 to fix CVEs > If you manual upgrade then you have an ugly WARN from apache ivy > Exception in thread "ivy-httpclient-shutdown-handler" > java.lang.NoClassDefFoundError: > org/apache/http/impl/conn/PoolingHttpClientConnectionManager$2 > at > org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:413) > at > org.apache.http.impl.client.HttpClientBuilder$2.close(HttpClientBuilder.java:1244) > at > org.apache.http.impl.client.InternalHttpClient.close(InternalHttpClient.java:201) > at > org.apache.ivy.util.url.HttpClientHandler.close(HttpClientHandler.java:357) > at > org.apache.ivy.util.url.HttpClientHandler$1.run(HttpClientHandler.java:84) > at java.base/java.lang.Thread.run(Thread.java:833) > Caused by: java.lang.ClassNotFoundException: > org.apache.http.impl.conn.PoolingHttpClientConnectionManager$2 > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1644) Upgrade httpclient to 4.5.13
[ https://issues.apache.org/jira/browse/IVY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733755#comment-17733755 ] Claus Ibsen commented on IVY-1644: -- And httpcore to 4.4.16 > Upgrade httpclient to 4.5.13 > > > Key: IVY-1644 > URL: https://issues.apache.org/jira/browse/IVY-1644 > Project: Ivy > Issue Type: Dependency upgrade > Components: Core >Affects Versions: 2.5.1 >Reporter: Claus Ibsen >Priority: Major > > The apache ivy 4.5.1 release comes with 4.5.10 version of the http client > httpclient-4.5.10.jar > httpcore-4.4.12.jar > > org.apache.httpcomponents > httpclient > 4.5.10 > > It would be good to upgrade to 4.5.13 to fix CVEs > If you manual upgrade then you have an ugly WARN from apache ivy > Exception in thread "ivy-httpclient-shutdown-handler" > java.lang.NoClassDefFoundError: > org/apache/http/impl/conn/PoolingHttpClientConnectionManager$2 > at > org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:413) > at > org.apache.http.impl.client.HttpClientBuilder$2.close(HttpClientBuilder.java:1244) > at > org.apache.http.impl.client.InternalHttpClient.close(InternalHttpClient.java:201) > at > org.apache.ivy.util.url.HttpClientHandler.close(HttpClientHandler.java:357) > at > org.apache.ivy.util.url.HttpClientHandler$1.run(HttpClientHandler.java:84) > at java.base/java.lang.Thread.run(Thread.java:833) > Caused by: java.lang.ClassNotFoundException: > org.apache.http.impl.conn.PoolingHttpClientConnectionManager$2 > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IVY-1644) Upgrade httpclient to 4.5.13
[ https://issues.apache.org/jira/browse/IVY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733754#comment-17733754 ] Claus Ibsen commented on IVY-1644: -- PS: Upgrading commons-codec to 1.15 would also be good as there are CVEs in the older versions > Upgrade httpclient to 4.5.13 > > > Key: IVY-1644 > URL: https://issues.apache.org/jira/browse/IVY-1644 > Project: Ivy > Issue Type: Dependency upgrade > Components: Core >Affects Versions: 2.5.1 >Reporter: Claus Ibsen >Priority: Major > > The apache ivy 4.5.1 release comes with 4.5.10 version of the http client > httpclient-4.5.10.jar > httpcore-4.4.12.jar > > org.apache.httpcomponents > httpclient > 4.5.10 > > It would be good to upgrade to 4.5.13 to fix CVEs > If you manual upgrade then you have an ugly WARN from apache ivy > Exception in thread "ivy-httpclient-shutdown-handler" > java.lang.NoClassDefFoundError: > org/apache/http/impl/conn/PoolingHttpClientConnectionManager$2 > at > org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:413) > at > org.apache.http.impl.client.HttpClientBuilder$2.close(HttpClientBuilder.java:1244) > at > org.apache.http.impl.client.InternalHttpClient.close(InternalHttpClient.java:201) > at > org.apache.ivy.util.url.HttpClientHandler.close(HttpClientHandler.java:357) > at > org.apache.ivy.util.url.HttpClientHandler$1.run(HttpClientHandler.java:84) > at java.base/java.lang.Thread.run(Thread.java:833) > Caused by: java.lang.ClassNotFoundException: > org.apache.http.impl.conn.PoolingHttpClientConnectionManager$2 > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVY-1644) Upgrade httpclient to 4.5.13
Claus Ibsen created IVY-1644: Summary: Upgrade httpclient to 4.5.13 Key: IVY-1644 URL: https://issues.apache.org/jira/browse/IVY-1644 Project: Ivy Issue Type: Dependency upgrade Components: Core Affects Versions: 2.5.1 Reporter: Claus Ibsen The apache ivy 4.5.1 release comes with 4.5.10 version of the http client httpclient-4.5.10.jar httpcore-4.4.12.jar org.apache.httpcomponents httpclient 4.5.10 It would be good to upgrade to 4.5.13 to fix CVEs If you manual upgrade then you have an ugly WARN from apache ivy Exception in thread "ivy-httpclient-shutdown-handler" java.lang.NoClassDefFoundError: org/apache/http/impl/conn/PoolingHttpClientConnectionManager$2 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:413) at org.apache.http.impl.client.HttpClientBuilder$2.close(HttpClientBuilder.java:1244) at org.apache.http.impl.client.InternalHttpClient.close(InternalHttpClient.java:201) at org.apache.ivy.util.url.HttpClientHandler.close(HttpClientHandler.java:357) at org.apache.ivy.util.url.HttpClientHandler$1.run(HttpClientHandler.java:84) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.lang.ClassNotFoundException: org.apache.http.impl.conn.PoolingHttpClientConnectionManager$2 at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVY-1643) Better feedback when uploading with incorrect sonatype credentials
Arnout Engelen created IVY-1643: --- Summary: Better feedback when uploading with incorrect sonatype credentials Key: IVY-1643 URL: https://issues.apache.org/jira/browse/IVY-1643 Project: Ivy Issue Type: Improvement Components: Core Reporter: Arnout Engelen When uploading to Sonatype with incorrect credentials, the user gets a "Server redirected too many times" error - for example (from [https://github.com/sbt/sbt-pgp/issues/182]): error] java.net.ProtocolException: Server redirected too many times (20) [error] at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [error] at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [error] at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [error] at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) [error] at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1974) [error] at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1969) [error] at java.base/java.security.AccessController.doPrivileged(Native Method) [error] at java.base/sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1968) [error] at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1536) [error] at java.base/sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1512) [error] at java.base/sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1510) [error] at java.base/java.security.AccessController.doPrivileged(Native Method) [error] at java.base/java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:795) [error] at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1509) [error] at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250) [error] at org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:285) [error] at org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82) [error] at org.apache.ivy.util.FileUtil.copy(FileUtil.java:150) [error] at org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:84) [error] at sbt.internal.librarymanagement.ConvertResolver$LocalIfFileRepo.put(ConvertResolver.scala:368) [error] at org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130) [error] at sbt.internal.librarymanagement.ConvertResolver$ChecksumFriendlyURLResolver.put(ConvertResolver.scala:118) [error] at sbt.internal.librarymanagement.ConvertResolver$ChecksumFriendlyURLResolver.put$(ConvertResolver.scala:105) [error] at sbt.internal.librarymanagement.ConvertResolver$$anonfun$defaultConvert$lzycompute$1$PluginCapableResolver$1.put(ConvertResolver.scala:165) [error] at org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:216) [error] at sbt.internal.librarymanagement.IvyActions$.$anonfun$publish$5(IvyActions.scala:501) [error] at sbt.internal.librarymanagement.IvyActions$.$anonfun$publish$5$adapted(IvyActions.scala:500) [error] at scala.collection.TraversableLike$WithFilter.$anonfun$foreach$1(TraversableLike.scala:877) [error] at scala.collection.Iterator.foreach(Iterator.scala:941) [error] at scala.collection.Iterator.foreach$(Iterator.scala:941) [error] at scala.collection.AbstractIterator.foreach(Iterator.scala:1429) [error] at scala.collection.IterableLike.foreach(IterableLike.scala:74) [error] at scala.collection.IterableLike.foreach$(IterableLike.scala:73) [error] at scala.collection.AbstractIterable.foreach(Iterable.scala:56) [error] at scala.collection.TraversableLike$WithFilter.foreach(TraversableLike.scala:876) [error] at sbt.internal.librarymanagement.IvyActions$.publish(IvyActions.scala:500) [error] at sbt.internal.librarymanagement.IvyActions$.$anonfun$publish$3(IvyActions.scala:142) [error] at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23) [error] at sbt.internal.librarymanagement.IvyActions$.withChecksums(IvyActions.scala:156) [error] at sbt.internal.librarymanagement.IvyActions$.withChecksums(IvyActions.scala:149) [error] at sbt.internal.librarymanagement.IvyActions$.$anonfun$publish$1(IvyActions.scala:142) [error] at sbt.internal.librarymanagement.IvyActions
[jira] [Resolved] (IVY-1641) NullPointerException when using Basic Auth for repository together with Apache HttpClient
[
https://issues.apache.org/jira/browse/IVY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved IVY-1641.
-
Resolution: Fixed
> NullPointerException when using Basic Auth for repository together with
> Apache HttpClient
> -
>
> Key: IVY-1641
> URL: https://issues.apache.org/jira/browse/IVY-1641
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.5.1
>Reporter: Stefan Bodewig
>Assignee: Stefan Bodewig
>Priority: Major
> Fix For: 2.5.2
>
> Attachments: build.xml, ivy.xml, ivysettings.xml
>
>
> For context see
> https://lists.apache.org/thread/9qk9z7h1xn7xs4ngyfhgcd9d1wjwb36r
> Full Stack Trace:
> {code}
> java.lang.NullPointerException: Cannot invoke
> "java.nio.charset.Charset.name()" because "charSet" is null
> at
> org.apache.ivy.util.url.HttpClientHandler.getURLInfo(HttpClientHandler.java:243)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.getURLInfo(URLHandlerDispatcher.java:122)
> at
> org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:82)
> at
> org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:101)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:102)
> at
> org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:94)
> at
> org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findArtifactRef(AbstractPatternsBasedResolver.java:74)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1029)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:966)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:247)
> at
> org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:101)
> at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:191)
> at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
> at
> org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:722)
> at
> org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:801)
> at
> org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:729)
> at
> org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:607)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:250)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:206)
> at org.apache.ivy.Ivy.resolve(Ivy.java:507)
> at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:328)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
> at
> org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:229)
> at
> org.apache.ivy.ant.IvyPostResolveTask.prepareAndCheck(IvyPostResolveTask.java:183)
> at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:92)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
> at org.apache.tools.ant.Task.perform(Task.java:350)
> at org.apache.tools.ant.Target.execute(Target.java:449)
> at org.apache.tools.ant.Target.performTasks(Target.java:470)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
> at org.apache.tools.ant.Main.runBuild(Main.java:818)
> at org.apache.tools.ant.Main.startAnt(Main.java:223)
> at org.apache.tools.ant.launch.Launcher.run
[jira] [Resolved] (IVY-1642) PomModuleDescriptorBuilder may lose dependencies in translation
[
https://issues.apache.org/jira/browse/IVY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved IVY-1642.
-
Fix Version/s: 2.5.2
Resolution: Fixed
fixed with
https://github.com/apache/ant-ivy/commit/5f11f05fe38b2fc3779d5bec6287505798bc701c
> PomModuleDescriptorBuilder may lose dependencies in translation
> ---
>
> Key: IVY-1642
> URL: https://issues.apache.org/jira/browse/IVY-1642
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Stefan Bodewig
>Assignee: Stefan Bodewig
>Priority: Major
> Fix For: 2.5.2
>
>
> https://github.com/Fernal73/CheckStyleSample/ shows an example where I fails
> to resolve one of the dependencies of Saxon-H2.
> Saxon-H2's POM says
> {code}
>
> org.xmlresolver
> xmlresolver
> 5.1.1
>
>
> org.xmlresolver
> xmlresolver
> 5.1.1
> data
>
> {code}
> but when translated to an ivy.xml file we only have
> {code}
> conf="compile->compile(*),\
> master(*);runtime->runtime(*)">
>
> m:classifier="data"/>
>
> {code}
> It looks as if {{PomModuleDescriptorBuilder}} was merging the two
> dependencies into one rather than creating two artifacts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IVY-1642) PomModuleDescriptorBuilder may lose dependencies in translation
[
https://issues.apache.org/jira/browse/IVY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17712051#comment-17712051
]
Stefan Bodewig commented on IVY-1642:
-
on first glance this is a duplicate of IVY-1580 but it seems the fix back then
has been incomplete.
> PomModuleDescriptorBuilder may lose dependencies in translation
> ---
>
> Key: IVY-1642
> URL: https://issues.apache.org/jira/browse/IVY-1642
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Stefan Bodewig
>Assignee: Stefan Bodewig
>Priority: Major
>
> https://github.com/Fernal73/CheckStyleSample/ shows an example where I fails
> to resolve one of the dependencies of Saxon-H2.
> Saxon-H2's POM says
> {code}
>
> org.xmlresolver
> xmlresolver
> 5.1.1
>
>
> org.xmlresolver
> xmlresolver
> 5.1.1
> data
>
> {code}
> but when translated to an ivy.xml file we only have
> {code}
> conf="compile->compile(*),\
> master(*);runtime->runtime(*)">
>
> m:classifier="data"/>
>
> {code}
> It looks as if {{PomModuleDescriptorBuilder}} was merging the two
> dependencies into one rather than creating two artifacts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1642) PomModuleDescriptorBuilder may lose dependencies in translation
[
https://issues.apache.org/jira/browse/IVY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1642:
Summary: PomModuleDescriptorBuilder may lose dependencies in translation
(was: PomModuleDescriptorBuilder may lose depndencies in translation)
> PomModuleDescriptorBuilder may lose dependencies in translation
> ---
>
> Key: IVY-1642
> URL: https://issues.apache.org/jira/browse/IVY-1642
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Stefan Bodewig
>Assignee: Stefan Bodewig
>Priority: Major
>
> https://github.com/Fernal73/CheckStyleSample/ shows an example where I fails
> to resolve one of the dependencies of Saxon-H2.
> Saxon-H2's POM says
> {code}
>
> org.xmlresolver
> xmlresolver
> 5.1.1
>
>
> org.xmlresolver
> xmlresolver
> 5.1.1
> data
>
> {code}
> but when translated to an ivy.xml file we only have
> {code}
> conf="compile->compile(*),\
> master(*);runtime->runtime(*)">
>
> m:classifier="data"/>
>
> {code}
> It looks as if {{PomModuleDescriptorBuilder}} was merging the two
> dependencies into one rather than creating two artifacts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1642) PomModuleDescriptorBuilder may lose depndencies in translation
[
https://issues.apache.org/jira/browse/IVY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1642:
Affects Version/s: 2.5.1
> PomModuleDescriptorBuilder may lose depndencies in translation
> --
>
> Key: IVY-1642
> URL: https://issues.apache.org/jira/browse/IVY-1642
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Stefan Bodewig
>Assignee: Stefan Bodewig
>Priority: Major
>
> https://github.com/Fernal73/CheckStyleSample/ shows an example where I fails
> to resolve one of the dependencies of Saxon-H2.
> Saxon-H2's POM says
> {code}
>
> org.xmlresolver
> xmlresolver
> 5.1.1
>
>
> org.xmlresolver
> xmlresolver
> 5.1.1
> data
>
> {code}
> but when translated to an ivy.xml file we only have
> {code}
> conf="compile->compile(*),\
> master(*);runtime->runtime(*)">
>
> m:classifier="data"/>
>
> {code}
> It looks as if {{PomModuleDescriptorBuilder}} was merging the two
> dependencies into one rather than creating two artifacts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IVY-1642) PomModuleDescriptorBuilder may lose depndencies in translation
Stefan Bodewig created IVY-1642:
---
Summary: PomModuleDescriptorBuilder may lose depndencies in
translation
Key: IVY-1642
URL: https://issues.apache.org/jira/browse/IVY-1642
Project: Ivy
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Stefan Bodewig
Assignee: Stefan Bodewig
https://github.com/Fernal73/CheckStyleSample/ shows an example where I fails to
resolve one of the dependencies of Saxon-H2.
Saxon-H2's POM says
{code}
org.xmlresolver
xmlresolver
5.1.1
org.xmlresolver
xmlresolver
5.1.1
data
{code}
but when translated to an ivy.xml file we only have
{code}
{code}
It looks as if {{PomModuleDescriptorBuilder}} was merging the two dependencies
into one rather than creating two artifacts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1641) NullPointerException when using Basic Auth for repository together with Apache HttpClient
[
https://issues.apache.org/jira/browse/IVY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1641:
Attachment: ivysettings.xml
ivy.xml
build.xml
> NullPointerException when using Basic Auth for repository together with
> Apache HttpClient
> -
>
> Key: IVY-1641
> URL: https://issues.apache.org/jira/browse/IVY-1641
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.5.1
>Reporter: Stefan Bodewig
>Assignee: Stefan Bodewig
>Priority: Major
> Fix For: 2.5.2
>
> Attachments: build.xml, ivy.xml, ivysettings.xml
>
>
> For context see
> https://lists.apache.org/thread/9qk9z7h1xn7xs4ngyfhgcd9d1wjwb36r
> Full Stack Trace:
> {code}
> java.lang.NullPointerException: Cannot invoke
> "java.nio.charset.Charset.name()" because "charSet" is null
> at
> org.apache.ivy.util.url.HttpClientHandler.getURLInfo(HttpClientHandler.java:243)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.getURLInfo(URLHandlerDispatcher.java:122)
> at
> org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:82)
> at
> org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:101)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:102)
> at
> org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:94)
> at
> org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findArtifactRef(AbstractPatternsBasedResolver.java:74)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1029)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:966)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:247)
> at
> org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:101)
> at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:191)
> at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
> at
> org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:722)
> at
> org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:801)
> at
> org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:729)
> at
> org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:607)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:250)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:206)
> at org.apache.ivy.Ivy.resolve(Ivy.java:507)
> at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:328)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
> at
> org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:229)
> at
> org.apache.ivy.ant.IvyPostResolveTask.prepareAndCheck(IvyPostResolveTask.java:183)
> at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:92)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
> at org.apache.tools.ant.Task.perform(Task.java:350)
> at org.apache.tools.ant.Target.execute(Target.java:449)
> at org.apache.tools.ant.Target.performTasks(Target.java:470)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
> at org.apache.tools.ant.Main.runBuild(Main.java:818)
> at org.apache.tools.ant.Main.startAnt(Main.jav
[jira] [Updated] (IVY-1641) NullPointerException when using Basic Auth for repository together with Apache HttpClient
[
https://issues.apache.org/jira/browse/IVY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1641:
Fix Version/s: 2.5.2
> NullPointerException when using Basic Auth for repository together with
> Apache HttpClient
> -
>
> Key: IVY-1641
> URL: https://issues.apache.org/jira/browse/IVY-1641
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.5.1
>Reporter: Stefan Bodewig
>Assignee: Stefan Bodewig
>Priority: Major
> Fix For: 2.5.2
>
>
> For context see
> https://lists.apache.org/thread/9qk9z7h1xn7xs4ngyfhgcd9d1wjwb36r
> Full Stack Trace:
> {code}
> java.lang.NullPointerException: Cannot invoke
> "java.nio.charset.Charset.name()" because "charSet" is null
> at
> org.apache.ivy.util.url.HttpClientHandler.getURLInfo(HttpClientHandler.java:243)
> at
> org.apache.ivy.util.url.URLHandlerDispatcher.getURLInfo(URLHandlerDispatcher.java:122)
> at
> org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:82)
> at
> org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:101)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:102)
> at
> org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:94)
> at
> org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findArtifactRef(AbstractPatternsBasedResolver.java:74)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1029)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:966)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:247)
> at
> org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:101)
> at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:191)
> at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
> at
> org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:722)
> at
> org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:801)
> at
> org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:729)
> at
> org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:607)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:250)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:206)
> at org.apache.ivy.Ivy.resolve(Ivy.java:507)
> at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:328)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
> at
> org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:229)
> at
> org.apache.ivy.ant.IvyPostResolveTask.prepareAndCheck(IvyPostResolveTask.java:183)
> at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:92)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
> at org.apache.tools.ant.Task.perform(Task.java:350)
> at org.apache.tools.ant.Target.execute(Target.java:449)
> at org.apache.tools.ant.Target.performTasks(Target.java:470)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
> at org.apache.tools.ant.Main.runBuild(Main.java:818)
> at org.apache.tools.ant.Main.startAnt(Main.java:223)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
> at org.apache.tools.ant.launch.Lau
[jira] [Created] (IVY-1641) NullPointerException when using Basic Auth for repository together with Apache HttpClient
Stefan Bodewig created IVY-1641:
---
Summary: NullPointerException when using Basic Auth for repository
together with Apache HttpClient
Key: IVY-1641
URL: https://issues.apache.org/jira/browse/IVY-1641
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.5.1
Reporter: Stefan Bodewig
Assignee: Stefan Bodewig
For context see https://lists.apache.org/thread/9qk9z7h1xn7xs4ngyfhgcd9d1wjwb36r
Full Stack Trace:
{code}
java.lang.NullPointerException: Cannot invoke
"java.nio.charset.Charset.name()" because "charSet" is null
at
org.apache.ivy.util.url.HttpClientHandler.getURLInfo(HttpClientHandler.java:243)
at
org.apache.ivy.util.url.URLHandlerDispatcher.getURLInfo(URLHandlerDispatcher.java:122)
at
org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:82)
at
org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:101)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:102)
at
org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:94)
at
org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findArtifactRef(AbstractPatternsBasedResolver.java:74)
at
org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1029)
at
org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:966)
at
org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:247)
at
org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:101)
at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:191)
at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:722)
at
org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:801)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:729)
at
org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:607)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:250)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:206)
at org.apache.ivy.Ivy.resolve(Ivy.java:507)
at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:328)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
at
org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:229)
at
org.apache.ivy.ant.IvyPostResolveTask.prepareAndCheck(IvyPostResolveTask.java:183)
at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:92)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:259)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.Main.runBuild(Main.java:818)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
Unexpected error: Cannot invoke "java.nio.charset.Charset.name()" because
"charSet" is null (java.lang.NullPointerException: Cannot invoke
"java.nio.charset.Charset.name()" because "charSet" is null)
java.lang.NullPointerException: Cannot invoke
"java.nio.charset.Charset.name()" because "charSet" is null
at
org.apache.ivy.util.url.HttpClientHandler.getURLInfo(HttpClientHandler.java:243)
at
org.apache.ivy.util.url.URLHandlerDispatcher.getURLInfo(URLHandlerDispatcher.java:122)
[jira] [Created] (IVY-1640) Ivy Authentication does not support HTTP Header tokens
Joern Guy Suess created IVY-1640: Summary: Ivy Authentication does not support HTTP Header tokens Key: IVY-1640 URL: https://issues.apache.org/jira/browse/IVY-1640 Project: Ivy Issue Type: Improvement Components: Core Affects Versions: 2.5.1, master Reporter: Joern Guy Suess [It is not possible to use Ivy in gitlab CI jobs, because auth does not support tokens.](https://docs.gitlab.com/ee/user/packages/maven_repository/#authenticate-to-the-package-registry). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IVYDE-396) Reuse available XML editors - Ant Editor / XML editor - for Ivy files
KDV created IVYDE-396: - Summary: Reuse available XML editors - Ant Editor / XML editor - for Ivy files Key: IVYDE-396 URL: https://issues.apache.org/jira/browse/IVYDE-396 Project: IvyDE Issue Type: Proposal Components: ivy editor, ivysettings editor Affects Versions: 2.2.0.final Reporter: KDV Attachments: ANT XML editor.png, IvyDE XML Editor.png, WTP-CPP XML editor.png IvyDE has XML editor meant specially for Ivy files. Ant editor - for build.xml - as part of Eclipse Platform is available in most Eclipse distribution packs(Java, JEE...) And XML Editor is available in CPP distribution(s). There is XML editor zoo in my Eclipse installations. E.g. in JEE: Ant editor, Ivy editor and XML editor. In Embedded CPP there is XML editor too(well, have no idea if IvyDE is useful in CPP-oriented enviroment). They all use their own syntax highlighting. So, by default Ant files, Ivy files and the rest xml files look different. And there is no single place to configure it. Why not to reuse available XML editor(s)? There will be less places to configure in Eclipse Preferences and less subsystems to support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVY-1632) Ivy can't access AWS CodeArtifact Repository
[
https://issues.apache.org/jira/browse/IVY-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1632:
Fix Version/s: 2.5.1
> Ivy can't access AWS CodeArtifact Repository
>
>
> Key: IVY-1632
> URL: https://issues.apache.org/jira/browse/IVY-1632
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.4.0, 2.5.0
>Reporter: Berno Langer
>Priority: Major
> Fix For: 2.5.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ivy can't access (Maven) CodeArtifact Repositories at AWS. The Server answers
> with HTTP 400 Bad Request.
> After debugging and looking into the sources, I found that Ivy sends an
> invalid "Accept" header. This seems to be related to
> [https://bugs.openjdk.java.net/browse/JDK-8163921]
> Changing the class org.apache.ivy.util.url.BasicUrlHandler, so that it sets
> an Accept header after opening a connection, like this ...
>
> {noformat}
> 95 con = normalizedURL.openConnection();
> 96 con.setRequestProperty("Accept", "*/*"); // <-- added
> {noformat}
> ... Ivy can access CodeArtifact Repositories perfectly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IVY-1632) Ivy can't access AWS CodeArtifact Repository
[
https://issues.apache.org/jira/browse/IVY-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved IVY-1632.
-
Resolution: Fixed
> Ivy can't access AWS CodeArtifact Repository
>
>
> Key: IVY-1632
> URL: https://issues.apache.org/jira/browse/IVY-1632
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.4.0, 2.5.0
>Reporter: Berno Langer
>Priority: Major
> Fix For: 2.5.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ivy can't access (Maven) CodeArtifact Repositories at AWS. The Server answers
> with HTTP 400 Bad Request.
> After debugging and looking into the sources, I found that Ivy sends an
> invalid "Accept" header. This seems to be related to
> [https://bugs.openjdk.java.net/browse/JDK-8163921]
> Changing the class org.apache.ivy.util.url.BasicUrlHandler, so that it sets
> an Accept header after opening a connection, like this ...
>
> {noformat}
> 95 con = normalizedURL.openConnection();
> 96 con.setRequestProperty("Accept", "*/*"); // <-- added
> {noformat}
> ... Ivy can access CodeArtifact Repositories perfectly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1626) Investigate impact of Bintray/JCenter shutdown
[ https://issues.apache.org/jira/browse/IVY-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated IVY-1626: Fix Version/s: 2.5.1 (was: master) > Investigate impact of Bintray/JCenter shutdown > -- > > Key: IVY-1626 > URL: https://issues.apache.org/jira/browse/IVY-1626 > Project: Ivy > Issue Type: Task >Reporter: Aurélien Pupier >Assignee: Jaikiran Pai >Priority: Major > Fix For: 2.5.1 > > > on 1st May 2021, the Bintray/Jcenter service will be shutdown. Ivy is > providing bintray resolver. I think it is set by default (o maybe it is Grape > that is setting by default?) > https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ > Which changes in codebase are required? > Which changes in user config can be done to avoid issues if cannot upgrade to > latest version easily? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVY-1618) ResolveEngine resets dictator resolver to null in the global configuration
[
https://issues.apache.org/jira/browse/IVY-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1618:
Fix Version/s: 2.5.1
(was: master)
> ResolveEngine resets dictator resolver to null in the global configuration
> --
>
> Key: IVY-1618
> URL: https://issues.apache.org/jira/browse/IVY-1618
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.5.0
> Environment: Windows 10, Java 8, Ivy 2.5.0.
>Reporter: Sergei Zhirikov
>Assignee: Jaikiran Pai
>Priority: Minor
> Fix For: 2.5.1
>
>
> ResolveEngine does not initialize its dictatorResover field in the
> constructor. As the result, when
> {code:java}
> public ResolveReport resolve(ModuleDescriptor md, ResolveOptions
> options){code}
> is called, the {{oldDictator}} local variable will be set to null in the
> beginning of the method. Then, in the end of the same method, inside the
> {{finally}} block, {{setDictatorResolver(null)}} will be called, which will
> not only set the private field in the ResolveEngine itself, but will also
> reset the dictator resolver in the global configuration. Why would it do
> that???
> The problem manifests itself when an {{Ivy}} instance is configured (using
> Java API) with only a dictator resolver, it will be able to handle a single
> call to {{resolve(...)}} successfully, and all subsequent calls will fail
> because of "no resolver available" (because the one that is supposed to be
> available, has been reset by the ResolveEngine, as described above).
> I have to admit that I am not very familiar with Ivy internals, but I find it
> extremely puzzling that an object that is a part of the internal
> implementation would change the global configuration at will.
> Looking at the implementation of {{Ivy}} and {{IvyContext}} classes, I get
> the impression that an {{Ivy}} instance is supposed to be thread-safe, in the
> sense that it should allow to call {{resolve(...)}} on the same instance from
> multiple threads safely. Am I mistaken? If there is supposed to be any thread
> safety, it is broken by the peculiar behavior of ResolveEngine with respect
> to setting the dictator resolver.
> In any case, I think it would be really helpful to explicitly mention thread
> safety (or lack thereof) in the Javadoc page of the main {{Ivy}} class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1612) Remove old fr\jayasoft\ivy\ant\antlib.xml from the jar
[ https://issues.apache.org/jira/browse/IVY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated IVY-1612: Fix Version/s: 2.5.1 (was: master) > Remove old fr\jayasoft\ivy\ant\antlib.xml from the jar > --- > > Key: IVY-1612 > URL: https://issues.apache.org/jira/browse/IVY-1612 > Project: Ivy > Issue Type: Task > Components: Ant, Core >Affects Versions: 2.5.0 >Reporter: Jan Materne >Priority: Minor > Fix For: 2.5.1 > > > The antlib definition file fr\jayasoft\ivy\ant\antlib.xml is there since 2007 > for BWC. > Now we should remove that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IVY-1612) Remove old fr\jayasoft\ivy\ant\antlib.xml from the jar
[ https://issues.apache.org/jira/browse/IVY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig reopened IVY-1612: - Assignee: (was: Jan Materne) > Remove old fr\jayasoft\ivy\ant\antlib.xml from the jar > --- > > Key: IVY-1612 > URL: https://issues.apache.org/jira/browse/IVY-1612 > Project: Ivy > Issue Type: Task > Components: Ant, Core >Affects Versions: 2.5.0 >Reporter: Jan Materne >Priority: Minor > Fix For: master > > > The antlib definition file fr\jayasoft\ivy\ant\antlib.xml is there since 2007 > for BWC. > Now we should remove that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IVY-1612) Remove old fr\jayasoft\ivy\ant\antlib.xml from the jar
[ https://issues.apache.org/jira/browse/IVY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved IVY-1612. - Resolution: Fixed > Remove old fr\jayasoft\ivy\ant\antlib.xml from the jar > --- > > Key: IVY-1612 > URL: https://issues.apache.org/jira/browse/IVY-1612 > Project: Ivy > Issue Type: Task > Components: Ant, Core >Affects Versions: 2.5.0 >Reporter: Jan Materne >Priority: Minor > Fix For: 2.5.1 > > > The antlib definition file fr\jayasoft\ivy\ant\antlib.xml is there since 2007 > for BWC. > Now we should remove that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVY-1631) ivy:retrieve task doesn't create empty set
[ https://issues.apache.org/jira/browse/IVY-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated IVY-1631: Fix Version/s: 2.5.1 (was: master) > ivy:retrieve task doesn't create empty set > -- > > Key: IVY-1631 > URL: https://issues.apache.org/jira/browse/IVY-1631 > Project: Ivy > Issue Type: Bug >Affects Versions: 2.4.0, 2.5.0 >Reporter: Maarten Coene >Assignee: Maarten Coene >Priority: Major > Fix For: 2.5.1 > > Time Spent: 50m > Remaining Estimate: 0h > > Scenario: > * specify a setId on ivy:retrieve > * the ivy:retrieve task retrieves no files > * the target directory already contained some other files > Instead of an empty FileSet, the FileSet created by ivy:retrieve task will > contain all existing files located in that target directory -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVY-1615) Ivy standalone : specify settings from URL
[
https://issues.apache.org/jira/browse/IVY-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1615:
Fix Version/s: 2.5.1
(was: master)
> Ivy standalone : specify settings from URL
> --
>
> Key: IVY-1615
> URL: https://issues.apache.org/jira/browse/IVY-1615
> Project: Ivy
> Issue Type: Improvement
> Components: Core
>Affects Versions: 2.5.0
>Reporter: Jason A. Guild
>Assignee: Jaikiran Pai
>Priority: Minor
> Labels: CLI, settings, standalone
> Fix For: 2.5.1
>
> Attachments: cli_ivysettings_from_url.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using ivy in standalone mode via CLI, allow the {{-settings}} option to
> read xml settings from a URL instead of a filesystem path. This allows
> convenient access to centralized settings.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1616) useOrigin="true" fails with file-based ibiblio
[
https://issues.apache.org/jira/browse/IVY-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1616:
Fix Version/s: 2.5.1
(was: master)
> useOrigin="true" fails with file-based ibiblio
> --
>
> Key: IVY-1616
> URL: https://issues.apache.org/jira/browse/IVY-1616
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Eric Milles
>Assignee: Jaikiran Pai
>Priority: Major
> Fix For: 2.5.1
>
>
> We are trying to use Maven's artifacts if they have already been downloaded.
> To that end, we have a file-based {{ibiblio}} resolver that points to the
> local .m2 repository directory. If maven is used to download an artifact so
> that it is in .m2 and not in Ivy's cache, we are getting errors from the
> origin check in {{DefaultRepositoryCacheManager}}.
> {code}
> java.lang.IllegalArgumentException:
> org.apache.maven.shared#maven-shared-utils;3.2.1!maven-shared-utils.jar
> origin location must be absolute:
> file:/C:/Users/Name/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.2.1/maven-shared-utils-3.2.1.jar
> at org.apache.ivy.util.Checks.checkAbsolute(Checks.java:57)
> at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getArchiveFileInCache(DefaultRepositoryCacheManager.java:410)
> at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.download(DefaultRepositoryCacheManager.java:996)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.download(BasicResolver.java:836)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.download(RepositoryResolver.java:305)
> at
> org.apache.ivy.plugins.resolver.IBiblioResolver.download(IBiblioResolver.java:563)
> at
> org.apache.ivy.core.resolve.ResolveEngine.downloadArtifacts(ResolveEngine.java:405)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:351)
> at org.apache.ivy.Ivy.resolve(Ivy.java:522)
> {code}
> {code:xml}
>
>
>
>
>checkmodified="true" changingPattern=".*" changingMatcher="regexp"
> m2compatible="true"/>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IVY-1628) ConcurrentModificationException in MessageLoggerHelper.sumupProblems
[
https://issues.apache.org/jira/browse/IVY-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated IVY-1628:
Fix Version/s: 2.5.1
(was: master)
> ConcurrentModificationException in MessageLoggerHelper.sumupProblems
>
>
> Key: IVY-1628
> URL: https://issues.apache.org/jira/browse/IVY-1628
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Environment: Groovy 2.4.12
>Reporter: Monroe Walker
>Assignee: Jaikiran Pai
>Priority: Major
> Fix For: 2.5.1
>
>
> Our Jenkins build job occasionally fails with
> {code:java}
> java.util.ConcurrentModificationExceptionjava.util.ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:911) at
> java.util.ArrayList$Itr.next(ArrayList.java:861) at
> org.apache.ivy.util.MessageLoggerHelper.sumupProblems(MessageLoggerHelper.java:45)
> at
> org.apache.ivy.util.MessageLoggerEngine.sumupProblems(MessageLoggerEngine.java:136)
> at org.apache.ivy.util.Message.sumupProblems(Message.java:143) at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:347) at
> org.apache.ivy.Ivy.resolve(Ivy.java:523)
> {code}
> It seems this must be due to a warning / error being logged while
> `sumupProblems` is printing the captured warning/errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (IVY-1197) OutOfMemoryError during ivy:publish
[ https://issues.apache.org/jira/browse/IVY-1197 ]
Maarten Coene deleted comment on IVY-1197:
was (Author: ekkara...@gmail.com):
http://ekkara...@gmail.com
> 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
>Priority: Major
> 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
(v8.20.10#820010)
[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=17620615#comment-17620615
]
Maarten Coene commented on IVY-1197:
[~andrew norman] : did you configure Ivy to use the Apache HTTP client
libraries?
> 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
>Priority: Major
> 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
(v8.20.10#820010)
[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=17620549#comment-17620549
]
Andrew Norman commented on IVY-1197:
the file size in my usecase just barely exceeds the 512m size and used to work
when it was less than that size so I think that the 512M is a hard limit of the
jenkins ivy plugin
> 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
>Priority: Major
> 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
(v8.20.10#820010)
[jira] [Comment Edited] (IVY-1197) OutOfMemoryError during ivy:publish
[
https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17620530#comment-17620530
]
Andrew Norman edited comment on IVY-1197 at 10/19/22 7:39 PM:
--
any chance this gets fixed soon? My use case is this out of memory failure when
running an "sbt publish" of a large zip file >512M on jenkins
was (Author: JIRAUSER297261):
any chance this gets fixed soon? My use case is this out of memory failing when
running an "sbt publish" of a large zip file >512M on jenkins
> 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
>Priority: Major
> 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
(v8.20.10#820010)
[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=17620530#comment-17620530
]
Andrew Norman commented on IVY-1197:
any chance this gets fixed soon? My use case is this out of memory failing when
running an "sbt publish" of a large zip file >512M on jenkins
> 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
>Priority: Major
> 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
(v8.20.10#820010)
[jira] [Created] (IVYDE-395) IvyDE loads multiple revisions of the same library
Sebastiano Vigna created IVYDE-395: -- Summary: IvyDE loads multiple revisions of the same library Key: IVYDE-395 URL: https://issues.apache.org/jira/browse/IVYDE-395 Project: IvyDE Issue Type: Bug Components: workspace resolver Affects Versions: 2.2.0.final Environment: Mac OS X 12.6, Eclipse 4.25.0. Reporter: Sebastiano Vigna Attachments: Screenshot 2022-10-09 at 08.10.16.png Resolving the Ivy configuration for WebGraph [https://github.com/vigna/webgraph/blob/master/ivy.xml] the "force" attributes for Logback are not respected. When I look into the artifacts that have been downloaded, I end up with two versions of Logback: !Screenshot 2022-10-09 at 08.10.16.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVY-1639) ivy 2.5.0 throws false positive CircularDependencyException
[
https://issues.apache.org/jira/browse/IVY-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Zhang updated IVY-1639:
--
Description:
When I try to use ivy 2.5.0 ivy:convertpom to convert hadoop-annotations pom
file to ivy, see
[https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-annotations/pom.xml]
I got CircularDependencyException, see stacktrace. There is no circular
dependencies and maven can successfully built the project. ivy should handle
these cases as well.
{code:java}
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:216)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:843)
at
org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:860)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1364)
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.parser.m2.PomModuleDescriptorParser.parseOtherPom(PomModuleDescriptorParser.java:492)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:221)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)
at org.apache.ivy.ant.IvyConvertPom.doExecute(IvyConvertPom.java:62)
... 18 more
{code}
was:
When I try to use ivy 2.5.0 ivy:convertpom to convert pom file to ivy, see
[https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-annotations/pom.xml]
I got CircularDependencyException, see stacktrace. There is no circular
dependencies and maven can successfully built the project. ivy should handle
these cases as well.
{code:java}
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:216)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:843)
at
org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:860)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1364)
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.parser.m2.PomModuleDescriptorParser.parseOtherPom(PomModuleDescriptorParser.java:492)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:221)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)
at org.apache.ivy.ant.IvyConvertPom.doExecute(IvyConvertPom.java:62)
... 18 more
{code}
> ivy 2.5.0 throws false positive CircularDependencyException
> ---
>
> Key: IVY-1639
> URL: https://issues.apache.org/jira/browse/IVY-1639
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
>Affects Versions: 2.5.0
>Reporter: Yu Zhang
>Priority: Major
>
> When I try to use ivy 2.5.0 ivy:convertpom to convert hadoop-annotations pom
> file to ivy, see
> [https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-annotations/pom.xml]
> I got CircularDependencyException, see stacktrace. There is no circular
> dependencies and maven can successfully built the project. ivy should handle
> these cases as well.
> {code:java}
> at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:216)
> at
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)
> at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyMo
[jira] [Created] (IVY-1639) ivy 2.5.0 throws false positive CircularDependencyException
Yu Zhang created IVY-1639:
-
Summary: ivy 2.5.0 throws false positive
CircularDependencyException
Key: IVY-1639
URL: https://issues.apache.org/jira/browse/IVY-1639
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.5.0
Reporter: Yu Zhang
When I try to use ivy 2.5.0 ivy:convertpom to convert pom file to ivy, see
[https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-annotations/pom.xml]
I got CircularDependencyException, see stacktrace. There is no circular
dependencies and maven can successfully built the project. ivy should handle
these cases as well.
{code:java}
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:216)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager$MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.java:843)
at
org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(ModuleDescriptorMemoryCache.java:68)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(DefaultRepositoryCacheManager.java:860)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1364)
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.parser.m2.PomModuleDescriptorParser.parseOtherPom(PomModuleDescriptorParser.java:492)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:221)
at
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.parseDescriptor(PomModuleDescriptorParser.java:123)
at org.apache.ivy.ant.IvyConvertPom.doExecute(IvyConvertPom.java:62)
... 18 more
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IVY-1638) Stop resolving dependencies when a wrong username/password is provided.
Maarten Coene created IVY-1638: -- Summary: Stop resolving dependencies when a wrong username/password is provided. Key: IVY-1638 URL: https://issues.apache.org/jira/browse/IVY-1638 Project: Ivy Issue Type: Improvement Components: Core Affects Versions: 2.5.0 Reporter: Maarten Coene When a wrong username/password is provided for some URL repository, Ivy will try this wrong combination for every module it wants to download from that repository. This can give issues on some servers (like for instance Artifactory) that lock user accounts after some failed login attempts. To prevent this from happening, it would be great if Ivy stops connecting to this server during the resolution process (for instance after a HTTP 401 response). Perhaps this should be made configurable somewhere to avoid backwards compatible issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IVYDE-394) IvyDE managed libraries not exported
[
https://issues.apache.org/jira/browse/IVYDE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harri T. updated IVYDE-394:
---
Description:
h2. Issue description
The classes of IvyDE managed libraries are not exported into a runnable JAR
file when a project JRE System Library is JavaSE-17.
h2. Steps for reproducing the issue
# Clone [the project|https://github.com/haba713/eclipse-ivyde-export-issue]:
{{git clone g...@github.com:haba713/eclipse-ivyde-export-issue.git}}
# Make sure that your Eclipse uses OpenJDK 17 and has IvyDE installed.
# Import the cloned project into Eclipse workspace.
# Right-click the class {{src/com.example/Main.java}} in the project tree and
choose Run as → Java Application. See the output: \{"key":"value"}
# Right-click the project and choose Export → Java → Runnable JAR file.
# Choose the launch configuration created on the step 4 above and choose also
Library handling: ◉ Extract required libraries into generated JAR. Click Finish.
# Try to run the generated JAR file:
{code:java}
$ java -jar eclipse-ivyde-export-issue.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/JSONObject
at com.example.Main.main(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.json.JSONObject
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 1 more{code}
The class {{org.json.JSONObject}} and other JSON classes are not included in
the JAR file even though the library is listed in the [Ivy
dependencies|https://github.com/haba713/eclipse-ivyde-export-issue/blob/master/ivy.xml].
h2. Workaround: Use JRE System Library 1.8 instead
Add OpenJDK 8 to Eclipse and change Java Build Path → Libraries → JRE System
Library to JavaSE-1.8. After that the IvyDE managed libraries are included in
the runnable JAR file when it's generated again.
See [this
commit|https://github.com/haba713/eclipse-ivyde-export-issue/commit/1789bb9e5a583bb1b0baa0481c8ea6e0481ef421].
h2. JDT or IvyDE issue?
The issue was also reported
[here|https://github.com/eclipse-jdt/eclipse.jdt.core/issues/130] because I'm
not sure if this is a JDT or IvyDE issue.
was:
h2. Issue description
The classes of IvyDE managed libraries are not exported into a runnable JAR
file when a project JRE System Library is JavaSE-17.
h2. Steps for reproducing the issue
# Clone [the project|https://github.com/haba713/eclipse-ivyde-export-issue]:
{{git clone g...@github.com:haba713/eclipse-ivyde-export-issue.git}}
# Make sure that your Eclipse uses OpenJDK 17 and has IvyDE installed.
# Import the cloned project into Eclipse workspace.
# Right-click the class {{src/com.example/Main.java}} in the project tree and
choose Run as → Java Application. See the output: \{"key":"value"}
# Right-click the project and choose Export → Java → Runnable JAR file.
# Choose the launch configuration created on the step 4 above and choose also
Library handling: ◉ Extract required libraries into generated JAR. Click Finish.
# Try to run the generated JAR file:
{code:java}
$ java -jar eclipse-ivyde-export-issue.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/JSONObject
at com.example.Main.main(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.json.JSONObject
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 1 more{code}
The class {{org.json.JSONObject}} and other JSON classes are not included in
the JAR file even though the library is listed in the [Ivy
dependencies|https://github.com/haba713/eclipse-ivyde-export-issue/blob/master/ivy.xml].
h2. Workaround: Use JRE System Library 1.8 instead
Add OpenJDK 8 to Eclipse and change Java Build Path → Libraries → JRE System
Library to JavaSE-1.8. After that the IvyDE managed libraries are included in
the runnable JAR file when it's generated again.
See [this
commit|https://github.com/haba713/eclipse-ivyde-export-issue/commit/1789bb9e5a583bb1b0baa0481c8ea6e0481ef421].
h2. JDT or IvyDE issue?
The issue was also reported
[here|https://github.com/eclipse-jdt/eclipse.jdt.core/issues/130] because I'm
not sure if this is JDT or IvyDE issue.
> IvyDE managed libraries not exported
>
>
> Key: IVYDE-394
> URL: https://issues.apache.org/jira/browse/IVYDE-394
> Project: IvyDE
> Issue Type: Bug
>Affects Versions: 2.2.0.final
> Environment: * Eclipse 2022-06 M2 (4.24.0 M2)
> * IvyDE 2.2.0
[jira] [Updated] (IVYDE-394) IvyDE managed libraries not exported
[
https://issues.apache.org/jira/browse/IVYDE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harri T. updated IVYDE-394:
---
Description:
h2. Issue description
The classes of IvyDE managed libraries are not exported into a runnable JAR
file when a project JRE System Library is JavaSE-17.
h2. Steps for reproducing the issue
# Clone [the project|https://github.com/haba713/eclipse-ivyde-export-issue]:
{{git clone g...@github.com:haba713/eclipse-ivyde-export-issue.git}}
# Make sure that your Eclipse uses OpenJDK 17 and has IvyDE installed.
# Import the cloned project into Eclipse workspace.
# Right-click the class {{src/com.example/Main.java}} in the project tree and
choose Run as → Java Application. See the output: \{"key":"value"}
# Right-click the project and choose Export → Java → Runnable JAR file.
# Choose the launch configuration created on the step 4 above and choose also
Library handling: ◉ Extract required libraries into generated JAR. Click Finish.
# Try to run the generated JAR file:
{code:java}
$ java -jar eclipse-ivyde-export-issue.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/JSONObject
at com.example.Main.main(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.json.JSONObject
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 1 more{code}
The class {{org.json.JSONObject}} and other JSON classes are not included in
the JAR file even though the library is listed in the [Ivy
dependencies|https://github.com/haba713/eclipse-ivyde-export-issue/blob/master/ivy.xml].
h2. Workaround: Use JRE System Library 1.8 instead
Add OpenJDK 8 to Eclipse and change Java Build Path → Libraries → JRE System
Library to JavaSE-1.8. After that the IvyDE managed libraries are included in
the runnable JAR file when it's generated again.
See [this
commit|https://github.com/haba713/eclipse-ivyde-export-issue/commit/1789bb9e5a583bb1b0baa0481c8ea6e0481ef421].
h2. JDT or IvyDE issue?
The issue was also reported
[here|https://github.com/eclipse-jdt/eclipse.jdt.core/issues/130] because I'm
not sure if this is JDT or IvyDE issue.
was:
h2. Issue description
The classes of IvyDE managed libraries are not exported into a runnable JAR
file when a project JRE System Library is JavaSE-17.
h2. Steps for reproducing the issue
# Clone [the project|https://github.com/haba713/eclipse-ivyde-export-issue]:
{{git clone g...@github.com:haba713/eclipse-ivyde-export-issue.git}}
# Make sure that your Eclipse uses OpenJDK 17 and has IvyDE installed.
# Import the cloned project into Eclipse workspace.
# Right-click the class {{src/com.example/Main.java}} in the project tree and
choose Run as → Java Application. See the output: \{"key":"value"}
# Right-click the project and choose Export → Java → Runnable JAR file.
# Choose the launch configuration created on the step 4 above and choose also
Library handling: ◉ Extract required libraries into generated JAR. Click Finish.
# Try to run the generated JAR file:
{code:java}
$ java -jar eclipse-ivyde-export-issue.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/JSONObject
at com.example.Main.main(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.json.JSONObject
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 1 more{code}
The class {{org.json.JSONObject}} and other JSON classes are not included in
the JAR file even though the library is listed in the [Ivy
dependencies|https://github.com/haba713/eclipse-ivyde-export-issue/blob/master/ivy.xml].
h2. Workaround: Use JRE System Library 1.8 instead
Add OpenJDK 8 to Eclipse and change Java Build Path → Libraries → JRE System
Library to JavaSE-1.8. After that the IvyDE managed libraries are included in
the runnable JAR file when it's generated again.
See [this
commit|https://github.com/haba713/eclipse-ivyde-export-issue/commit/1789bb9e5a583bb1b0baa0481c8ea6e0481ef421].
> IvyDE managed libraries not exported
>
>
> Key: IVYDE-394
> URL: https://issues.apache.org/jira/browse/IVYDE-394
> Project: IvyDE
> Issue Type: Bug
>Affects Versions: 2.2.0.final
> Environment: * Eclipse 2022-06 M2 (4.24.0 M2)
> * IvyDE 2.2.0.final-201311091524-RELEASE
> * OpenJDK 17.0.3+7-Debian-1deb11u1
> * Debian GNU/Linux 11 (Bullseye)
>Reporter: Harri T.
>Priority: Major
&
[jira] [Updated] (IVYDE-394) IvyDE managed libraries not exported
[
https://issues.apache.org/jira/browse/IVYDE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harri T. updated IVYDE-394:
---
Description:
h2. Issue description
The classes of IvyDE managed libraries are not exported into a runnable JAR
file when a project JRE System Library is JavaSE-17.
h2. Steps for reproducing the issue
# Clone [the project|https://github.com/haba713/eclipse-ivyde-export-issue]:
{{git clone g...@github.com:haba713/eclipse-ivyde-export-issue.git}}
# Make sure that your Eclipse uses OpenJDK 17 and has IvyDE installed.
# Import the cloned project into Eclipse workspace.
# Right-click the class {{src/com.example/Main.java}} in the project tree and
choose Run as → Java Application. See the output: \{"key":"value"}
# Right-click the project and choose Export → Java → Runnable JAR file.
# Choose the launch configuration created on the step 4 above and choose also
Library handling: ◉ Extract required libraries into generated JAR. Click Finish.
# Try to run the generated JAR file:
{code:java}
$ java -jar eclipse-ivyde-export-issue.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/JSONObject
at com.example.Main.main(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.json.JSONObject
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 1 more{code}
The class {{org.json.JSONObject}} and other JSON classes are not included in
the JAR file even though the library is listed in the [Ivy
dependencies|https://github.com/haba713/eclipse-ivyde-export-issue/blob/master/ivy.xml].
h2. Workaround: Use JRE System Library 1.8 instead
Add OpenJDK 8 to Eclipse and change Java Build Path → Libraries → JRE System
Library to JavaSE-1.8. After that the IvyDE managed libraries are included in
the runnable JAR file when it's generated again.
See [this
commit|https://github.com/haba713/eclipse-ivyde-export-issue/commit/1789bb9e5a583bb1b0baa0481c8ea6e0481ef421].
was:
h2. Issue description
The classes of IvyDE managed libraries are not exported into a runnable JAR
file when a project JRE System Library is JavaSE-17.
h2. Steps for reproducing the issue
# Clone [the project|https://github.com/haba713/eclipse-ivyde-export-issue]:
{{git clone g...@github.com:haba713/eclipse-ivyde-export-issue.git}}
# Make sure that your Eclipse uses OpenJDK 17 and has IvyDE installed.
# Import the cloned project into Eclipse workspace.
# Right-click the class {{src/com.example/Main.java}} in the project tree and
choose Run as → Java Application. See the output: {{{}{"key":"value"}{}}}.
# Right-click the project and choose Export → Java → Runnable JAR file.
# Choose the launch configuration created on the step 4 above and choose also
Library handling: ◉ Extract required libraries into generated JAR. Click Finish.
# Try to run the generated JAR file:
$ java -jar eclipse-ivyde-export-issue.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/JSONObject
at com.example.Main.main(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.json.JSONObject
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 1 more{{}}
The class {{org.json.JSONObject}} and other JSON classes are not included in
the JAR file even though the library is listed in the [Ivy
dependencies|https://github.com/haba713/eclipse-ivyde-export-issue/blob/master/ivy.xml].
h2. Workaround: Use JRE System Library 1.8 instead
Add OpenJDK 8 to Eclipse and change Java Build Path → Libraries → JRE System
Library to JavaSE-1.8. After that
the IvyDE managed libraries are included in the runnable JAR file when it's
generated again.
See [this
commit|https://github.com/haba713/eclipse-ivyde-export-issue/commit/1789bb9e5a583bb1b0baa0481c8ea6e0481ef421].
> IvyDE managed libraries not exported
>
>
> Key: IVYDE-394
> URL: https://issues.apache.org/jira/browse/IVYDE-394
> Project: IvyDE
> Issue Type: Bug
>Affects Versions: 2.2.0.final
> Environment: * Eclipse 2022-06 M2 (4.24.0 M2)
> * IvyDE 2.2.0.final-201311091524-RELEASE
> * OpenJDK 17.0.3+7-Debian-1deb11u1
> * Debian GNU/Linux 11 (Bullseye)
>Reporter: Harri T.
>Priority: Major
>
> h2. Issue description
> The classes of IvyDE managed libraries are not exported into a runnable JAR
> file when a project JRE System Library is JavaSE-17.
&
[jira] [Created] (IVYDE-394) IvyDE managed libraries not exported
Harri T. created IVYDE-394:
--
Summary: IvyDE managed libraries not exported
Key: IVYDE-394
URL: https://issues.apache.org/jira/browse/IVYDE-394
Project: IvyDE
Issue Type: Bug
Affects Versions: 2.2.0.final
Environment: * Eclipse 2022-06 M2 (4.24.0 M2)
* IvyDE 2.2.0.final-201311091524-RELEASE
* OpenJDK 17.0.3+7-Debian-1deb11u1
* Debian GNU/Linux 11 (Bullseye)
Reporter: Harri T.
h2. Issue description
The classes of IvyDE managed libraries are not exported into a runnable JAR
file when a project JRE System Library is JavaSE-17.
h2. Steps for reproducing the issue
# Clone [the project|https://github.com/haba713/eclipse-ivyde-export-issue]:
{{git clone g...@github.com:haba713/eclipse-ivyde-export-issue.git}}
# Make sure that your Eclipse uses OpenJDK 17 and has IvyDE installed.
# Import the cloned project into Eclipse workspace.
# Right-click the class {{src/com.example/Main.java}} in the project tree and
choose Run as → Java Application. See the output: {{{}{"key":"value"}{}}}.
# Right-click the project and choose Export → Java → Runnable JAR file.
# Choose the launch configuration created on the step 4 above and choose also
Library handling: ◉ Extract required libraries into generated JAR. Click Finish.
# Try to run the generated JAR file:
$ java -jar eclipse-ivyde-export-issue.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/JSONObject
at com.example.Main.main(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.json.JSONObject
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 1 more{{}}
The class {{org.json.JSONObject}} and other JSON classes are not included in
the JAR file even though the library is listed in the [Ivy
dependencies|https://github.com/haba713/eclipse-ivyde-export-issue/blob/master/ivy.xml].
h2. Workaround: Use JRE System Library 1.8 instead
Add OpenJDK 8 to Eclipse and change Java Build Path → Libraries → JRE System
Library to JavaSE-1.8. After that
the IvyDE managed libraries are included in the runnable JAR file when it's
generated again.
See [this
commit|https://github.com/haba713/eclipse-ivyde-export-issue/commit/1789bb9e5a583bb1b0baa0481c8ea6e0481ef421].
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IVY-1637) Default value of 'revConstraint' is not set, if 'branchConstraint' is present in
Sebastian Dingel created IVY-1637:
-
Summary: Default value of 'revConstraint' is not set, if
'branchConstraint' is present in
Key: IVY-1637
URL: https://issues.apache.org/jira/browse/IVY-1637
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.5.0
Reporter: Sebastian Dingel
The
[documentation|https://ant.apache.org/ivy/history/2.5.0/ivyfile/dependency.html]
of iyv states:
||Attribute||Description||Required||
|revConstraint|the dynamic revision constraint originally used for this
dependency. See
[above|https://ant.apache.org/ivy/history/2.5.0/ivyfile/dependency.html#revision-constraint]
for details.|No, defaults to the value of {{rev}}|
The behaviour of XmlModuleDescriptorParser is different. If attribute
'branchConstraint' is given the parser does not fall back to 'rev'. It only
falls back to rev, if 'branchConstraint' is not set.
Example:
{code:java}
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IVY-1636) Ivy.xml failed to resolve dependency
Vipin created IVY-1636: -- Summary: Ivy.xml failed to resolve dependency Key: IVY-1636 URL: https://issues.apache.org/jira/browse/IVY-1636 Project: Ivy Issue Type: Question Components: Core Environment: Linux, Editor: Eclipse STS Reporter: Vipin Attachments: ivy issue details.docx I have a project which is using ivy for dependency resolution. When I am adding ivy library in eclipse. Its giving me following error. 'IvyDE resolve' has encountered a problem. some projects fail to be resolved. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IVY-1635) [SOLVED] attributes of inline ivy:resolve not being re-used by post-resolve tasks
[
https://issues.apache.org/jira/browse/IVY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jswdevteam updated IVY-1635:
Description:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call and repeat all the attributes ({_}inline{_},
{_}organization{_}, {_}module{_}, {_}revision{_}, etc.) {*}to each retrieve
task{*}, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve info.
*EDIT:* Solved, see comment
was:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call and repeat all the attributes ({_}inline{_},
{_}organization{_}, {_}module{_}, {_}revision{_}, etc.) {*}to each retrieve
task{*}, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve info.
Issue Type: Question (was: Bug)
Summary: [SOLVED] attributes of inline ivy:resolve not being re-used by
post-resolve tasks (was: attributes of inline ivy:resolve not being re-used by
post-resolve tasks)
> [SOLVED] attributes of inline ivy:resolve not being re-used by post-resolve
> tasks
> -
>
> Key: IVY-1635
> URL: https://issues.apache.org/jira/browse/IVY-1635
> Project: Ivy
> Issue Type: Question
>Affects Versions: 2.5.0
>Reporter: jswdevteam
>Priority: Major
>
> I tried to have one inline *resolve* task followed by several *retrieve*
> tasks.
> Example:
> {{ module="mymod" revision="${mymod.revision}" settingsRef="settings1"/>}}
> {{ type="lib" />}}
> {{ type="header"/>}}
>
> I was expecting that the retrieve tasks would reuse the informations of the
> resolve previously done. But I get this error:
> ??no organisation provided for ivy cache task: It can either be set
> explicitly via the attribute 'organisation' or via 'ivy.organisation'
> property *or a prior call to *??
>
> If I don't call and repeat all the attributes ({_}inline{_},
> {_}organization{_}, {_}module{_}, {_}revision{_}, etc.) {*}to each retrieve
> task{*}, then it works.
> However I would think it more logical to resolve once and retrieve as many
> time as needed using the same resolve info.
> *EDIT:* Solved, see comment
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IVY-1635) attributes of inline ivy:resolve not being re-used by post-resolve tasks
[
https://issues.apache.org/jira/browse/IVY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17513770#comment-17513770
]
jswdevteam commented on IVY-1635:
-
My bad. This was solved by using keep="true" on the resolve task.
The documentation mentions that keep "defaults to *false* for an *inline*
resolve and to true in any other case".
I was not aware of that.
> attributes of inline ivy:resolve not being re-used by post-resolve tasks
>
>
> Key: IVY-1635
> URL: https://issues.apache.org/jira/browse/IVY-1635
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: jswdevteam
>Priority: Major
>
> I tried to have one inline *resolve* task followed by several *retrieve*
> tasks.
> Example:
> {{ module="mymod" revision="${mymod.revision}" settingsRef="settings1"/>}}
> {{ type="lib" />}}
> {{ type="header"/>}}
>
> I was expecting that the retrieve tasks would reuse the informations of the
> resolve previously done. But I get this error:
> ??no organisation provided for ivy cache task: It can either be set
> explicitly via the attribute 'organisation' or via 'ivy.organisation'
> property *or a prior call to *??
>
> If I don't call and repeat all the attributes ({_}inline{_},
> {_}organization{_}, {_}module{_}, {_}revision{_}, etc.) {*}to each retrieve
> task{*}, then it works.
> However I would think it more logical to resolve once and retrieve as many
> time as needed using the same resolve info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IVY-1635) attributes of inline ivy:resolve not being re-used by post-resolve tasks
[
https://issues.apache.org/jira/browse/IVY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jswdevteam updated IVY-1635:
Description:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call and repeat all the attributes ({_}inline{_},
{_}organization{_}, {_}module{_}, {_}revision{_}, etc.) {*}to each retrieve
task{*}, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve info.
was:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
> attributes of inline ivy:resolve not being re-used by post-resolve tasks
>
>
> Key: IVY-1635
> URL: https://issues.apache.org/jira/browse/IVY-1635
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: jswdevteam
>Priority: Major
>
> I tried to have one inline *resolve* task followed by several *retrieve*
> tasks.
> Example:
> {{ module="mymod" revision="${mymod.revision}" settingsRef="settings1"/>}}
> {{ type="lib" />}}
> {{ type="header"/>}}
>
> I was expecting that the retrieve tasks would reuse the informations of the
> resolve previously done. But I get this error:
> ??no organisation provided for ivy cache task: It can either be set
> explicitly via the attribute 'organisation' or via 'ivy.organisation'
> property *or a prior call to *??
>
> If I don't call and repeat all the attributes ({_}inline{_},
> {_}organization{_}, {_}module{_}, {_}revision{_}, etc.) {*}to each retrieve
> task{*}, then it works.
> However I would think it more logical to resolve once and retrieve as many
> time as needed using the same resolve info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IVY-1635) attributes of inline ivy:resolve not being re-used by post-resolve tasks
[
https://issues.apache.org/jira/browse/IVY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jswdevteam updated IVY-1635:
Description:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
was:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
> attributes of inline ivy:resolve not being re-used by post-resolve tasks
>
>
> Key: IVY-1635
> URL: https://issues.apache.org/jira/browse/IVY-1635
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: jswdevteam
>Priority: Major
>
> I tried to have one inline *resolve* task followed by several *retrieve*
> tasks.
> Example:
> {{ module="mymod" revision="${mymod.revision}" settingsRef="settings1"/>}}
> {{ type="lib" />}}
> {{ type="header"/>}}
> I was expecting that the retrieve tasks would reuse the informations of the
> resolve previously done. But I get this error:
> ??no organisation provided for ivy cache task: It can either be set
> explicitly via the attribute 'organisation' or via 'ivy.organisation'
> property *or a prior call to *??
> If I don't call \{{ }}and repeat all the attributes (inline,
> organization, , module, revision, etc.) to each retrieve task, then it works.
> However I would think it more logical to resolve once and retrieve as many
> time as needed using the same resolve.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IVY-1635) attributes of inline ivy:resolve not being re-used by post-resolve tasks
[
https://issues.apache.org/jira/browse/IVY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jswdevteam updated IVY-1635:
Description:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
was:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
> attributes of inline ivy:resolve not being re-used by post-resolve tasks
>
>
> Key: IVY-1635
> URL: https://issues.apache.org/jira/browse/IVY-1635
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: jswdevteam
>Priority: Major
>
> I tried to have one inline *resolve* task followed by several *retrieve*
> tasks.
> Example:
> {{ module="mymod" revision="${mymod.revision}" settingsRef="settings1"/>}}
> {{ type="lib" />}}
> {{ type="header"/>}}
>
> I was expecting that the retrieve tasks would reuse the informations of the
> resolve previously done. But I get this error:
> ??no organisation provided for ivy cache task: It can either be set
> explicitly via the attribute 'organisation' or via 'ivy.organisation'
> property *or a prior call to *??
> If I don't call \{{ }}and repeat all the attributes (inline,
> organization, , module, revision, etc.) to each retrieve task, then it works.
> However I would think it more logical to resolve once and retrieve as many
> time as needed using the same resolve.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IVY-1635) attributes of inline ivy:resolve not being re-used by post-resolve tasks
[
https://issues.apache.org/jira/browse/IVY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jswdevteam updated IVY-1635:
Description:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
was:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
> attributes of inline ivy:resolve not being re-used by post-resolve tasks
>
>
> Key: IVY-1635
> URL: https://issues.apache.org/jira/browse/IVY-1635
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: jswdevteam
>Priority: Major
>
> I tried to have one inline *resolve* task followed by several *retrieve*
> tasks.
> Example:
> {{ module="mymod" revision="${mymod.revision}" settingsRef="settings1"/>}}
> {{ type="lib" />}}
> {{ type="header"/>}}
>
> I was expecting that the retrieve tasks would reuse the informations of the
> resolve previously done. But I get this error:
> ??no organisation provided for ivy cache task: It can either be set
> explicitly via the attribute 'organisation' or via 'ivy.organisation'
> property *or a prior call to *??
>
> If I don't call \{{ }}and repeat all the attributes (inline,
> organization, , module, revision, etc.) to each retrieve task, then it works.
> However I would think it more logical to resolve once and retrieve as many
> time as needed using the same resolve.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IVY-1635) attributes of inline ivy:resolve not being re-used by post-resolve tasks
jswdevteam created IVY-1635:
---
Summary: attributes of inline ivy:resolve not being re-used by
post-resolve tasks
Key: IVY-1635
URL: https://issues.apache.org/jira/browse/IVY-1635
Project: Ivy
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: jswdevteam
I tried to have one inline resolve task followed by several retrieve tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call {{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IVY-1635) attributes of inline ivy:resolve not being re-used by post-resolve tasks
[
https://issues.apache.org/jira/browse/IVY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jswdevteam updated IVY-1635:
Description:
I tried to have one inline *resolve* task followed by several *retrieve* tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call \{{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
was:
I tried to have one inline resolve task followed by several retrieve tasks.
Example:
{{}}
{{}}
{{}}
I was expecting that the retrieve tasks would reuse the informations of the
resolve previously done. But I get this error:
??no organisation provided for ivy cache task: It can either be set explicitly
via the attribute 'organisation' or via 'ivy.organisation' property *or a prior
call to *??
If I don't call {{ }}and repeat all the attributes (inline,
organization, , module, revision, etc.) to each retrieve task, then it works.
However I would think it more logical to resolve once and retrieve as many time
as needed using the same resolve.
> attributes of inline ivy:resolve not being re-used by post-resolve tasks
>
>
> Key: IVY-1635
> URL: https://issues.apache.org/jira/browse/IVY-1635
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: jswdevteam
>Priority: Major
>
> I tried to have one inline *resolve* task followed by several *retrieve*
> tasks. Example:
> {{ module="mymod" revision="${mymod.revision}" settingsRef="settings1"/>}}
> {{ type="lib" />}}
> {{ type="header"/>}}
> I was expecting that the retrieve tasks would reuse the informations of the
> resolve previously done. But I get this error:
> ??no organisation provided for ivy cache task: It can either be set
> explicitly via the attribute 'organisation' or via 'ivy.organisation'
> property *or a prior call to *??
> If I don't call \{{ }}and repeat all the attributes (inline,
> organization, , module, revision, etc.) to each retrieve task, then it works.
> However I would think it more logical to resolve once and retrieve as many
> time as needed using the same resolve.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IVY-1634) Clean the Jira issue tracker. It's a mess.
Sérgio Siegrist created IVY-1634: Summary: Clean the Jira issue tracker. It's a mess. Key: IVY-1634 URL: https://issues.apache.org/jira/browse/IVY-1634 Project: Ivy Issue Type: Bug Reporter: Sérgio Siegrist -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481464#comment-17481464
]
John Robert Fallows commented on IVY-1633:
--
[~jaikiran] Kindly let me know your feedback please.
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Major
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 0 | 0 | 0 || 0 | 0 |
> | master | 0 | 0 | 0 | 0 || 0 | 0 |
> | compile | 1 | 0 | 0 | 0 || 0 | 0 |
> | provided | 0 | 0 | 0 | 0 || 0 | 0 |
> | runtime | 1 | 0 | 0 | 0 || 0 | 0 |
> | test | 1 | 0 | 0 | 0 || 0 | 0 |
> | system | 0 | 0 | 0 | 0 || 0 | 0 |
> | sources | 0 | 0 | 0 | 0 || 0 | 0 |
> | javadoc | 0 | 0 | 0 | 0 || 0 | 0 |
> | optional | 0 | 0 | 0 | 0 || 0 | 0 |
> -
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] WARNINGS
> [ivy:retrieve] module not found: io.aklivity.sandbox#toys;0.3
> [ivy:retrieve] ibiblio: tried
> [
[jira] [Commented] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469563#comment-17469563
]
John Robert Fallows commented on IVY-1633:
--
[~jaikiran] When experimenting with using Apache HttpComponents HttpClient
{{4.5.9}} optional Ivy {{2.5.0}} dependency, I found the following changes are
also necessary to support this usecase.
*http client*
https://github.com/jfallows/httpcomponents-client/commit/0295b6e38449957c783a991f9a2f11379104e994
*ivy*
https://github.com/jfallows/ant-ivy/commit/3a99deddf23bff630c54ead35d4081b101a8d429
Please take a look and let me know your feedback.
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Major
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 0 | 0 | 0 || 0 | 0 |
> | master | 0 | 0 | 0 | 0 || 0 | 0 |
> | compile | 1 | 0 | 0 | 0 || 0 | 0 |
> | provided | 0 | 0 | 0 | 0 || 0 | 0 |
> | runtime | 1 | 0 | 0 | 0 || 0 | 0 |
> | test | 1 | 0 | 0 | 0 || 0 | 0 |
> | system | 0 | 0 | 0 | 0 || 0 | 0 |
> | sources | 0 | 0 | 0 | 0 || 0 | 0 |
> | javadoc | 0 | 0 | 0
[jira] [Commented] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464290#comment-17464290
]
Jaikiran Pai commented on IVY-1633:
---
> The use case here allows the redirecting server to provide default "readonly"
>credentials, then the client can choose to elevate their privileges with their
>own credentials as required and if none are provided then the server
>credentials are used.
> If we invert the order, then a client could never override the credentials
> provided by the redirecting server.
I think the client (Ivy) having a final control over which credential gets used
makes sense. That way, users can at least configure a different credential for
that redirected URL if they want to. So what you have now I think is fine then.
Would you be able to include a test case in the patch, in the Ivy test suite to
make sure this works (and continues to work) as expected? If not, I'll add one
myself before merging this.
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Major
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 0 | 0 | 0 || 0 | 0 |
> | master | 0 | 0 | 0 | 0 || 0 | 0 |
> | compile | 1 | 0 | 0 | 0 || 0 | 0 |
> | provided | 0 | 0 | 0 | 0
[jira] [Commented] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462736#comment-17462736
]
John Robert Fallows commented on IVY-1633:
--
[~jaikiran] thanks, yes I did consider the ordering when providing the proposed
patch, but totally open to discussion about it.
The use case here allows the redirecting server to provide default "readonly"
credentials, then the client can choose to elevate their privileges with their
own credentials as required and if none are provided then the server
credentials are used.
If we invert the order, then a client could never override the credentials
provided by the redirecting server.
Let me the order of precedence you think is best for the Ivy project, and I can
update the patch if needed.
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Major
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 0 | 0 | 0 || 0 | 0 |
> | master | 0 | 0 | 0 | 0 || 0 | 0 |
> | compile | 1 | 0 | 0 | 0 || 0 | 0 |
> | provided | 0 | 0 | 0 | 0 || 0 | 0 |
> | runtime | 1 | 0 | 0 | 0 || 0 | 0 |
> | test | 1 | 0 | 0 | 0 || 0 | 0 |
> |
[jira] [Commented] (IVY-1632) Ivy can't access AWS CodeArtifact Repository
[
https://issues.apache.org/jira/browse/IVY-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462469#comment-17462469
]
Berno Langer commented on IVY-1632:
---
https://github.com/apache/ant-ivy/pull/96
> Ivy can't access AWS CodeArtifact Repository
>
>
> Key: IVY-1632
> URL: https://issues.apache.org/jira/browse/IVY-1632
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.4.0, 2.5.0
>Reporter: Berno Langer
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ivy can't access (Maven) CodeArtifact Repositories at AWS. The Server answers
> with HTTP 400 Bad Request.
> After debugging and looking into the sources, I found that Ivy sends an
> invalid "Accept" header. This seems to be related to
> [https://bugs.openjdk.java.net/browse/JDK-8163921]
> Changing the class org.apache.ivy.util.url.BasicUrlHandler, so that it sets
> an Accept header after opening a connection, like this ...
>
> {noformat}
> 95 con = normalizedURL.openConnection();
> 96 con.setRequestProperty("Accept", "*/*"); // <-- added
> {noformat}
> ... Ivy can access CodeArtifact Repositories perfectly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461774#comment-17461774
]
Jaikiran Pai commented on IVY-1633:
---
Hello John, I took a quick look at this. It appears that even Java's
implementation of HTTPURLConnection doesn't handle redirects of this form where
ther userinfo is part of the redirected "Location".
Looking at your patch, I think one thing we might have to consider in that
change is the "priority" of which credential gets used for that particular URL.
What I mean is, the IvyAuthenticator uses a CredentialsStore which is queried
for credentials, for a particular realm and host. In your patch, that
credential store will be queried first and only if it returns null then the
user/pass from the URL (if any) is used. I think it should be the other way
around. The userinfo (if any) in the requesting URL should be first checked and
only if it is missing, then the credential store should be queried. We will
have to see if there are any other implications of this.
FWIW, there seems to be a JDK issue requesting a similar enhancement (not
specifically to redirected requests, but URLs in general)
[https://bugs.openjdk.java.net/browse/JDK-5043482] and the recommendation seems
to be use an Authenticator (like the IvyAuthenticator) to handle this use case.
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Major
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnl
[jira] [Updated] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaikiran Pai updated IVY-1633:
--
Priority: Major (was: Blocker)
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Major
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 0 | 0 | 0 || 0 | 0 |
> | master | 0 | 0 | 0 | 0 || 0 | 0 |
> | compile | 1 | 0 | 0 | 0 || 0 | 0 |
> | provided | 0 | 0 | 0 | 0 || 0 | 0 |
> | runtime | 1 | 0 | 0 | 0 || 0 | 0 |
> | test | 1 | 0 | 0 | 0 || 0 | 0 |
> | system | 0 | 0 | 0 | 0 || 0 | 0 |
> | sources | 0 | 0 | 0 | 0 || 0 | 0 |
> | javadoc | 0 | 0 | 0 | 0 || 0 | 0 |
> | optional | 0 | 0 | 0 | 0 || 0 | 0 |
> -
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] WARNINGS
> [ivy:retrieve] module not found: io.aklivity.sandbox#toys;0.3
> [ivy:retrieve] ibiblio: tried
> [ivy:retrieve]
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/
[jira] [Commented] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461659#comment-17461659
]
John Robert Fallows commented on IVY-1633:
--
When I apply the attached patch to Ivy, and replace the ivy.jar in ant libexec
directory, then Ivy resolves the dependencies successfully, same as Maven.
{quote}% ant
Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
resolve:
[ivy:convertpom] :: Apache Ivy 2.6.0-local-20211217115540 - 20211217115540 ::
https://ant.apache.org/ivy/ ::
[ivy:convertpom] :: loading settings :: file =
/Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
[ivy:retrieve] :: resolving dependencies ::
io.aklivity.sandbox#toystore;develop-SNAPSHOT
[ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
system, sources, javadoc, optional]
[ivy:retrieve] found io.aklivity.sandbox#toys;0.3 in ibiblio
[ivy:retrieve] downloading
https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar ...
[ivy:retrieve] [SUCCESSFUL ] io.aklivity.sandbox#toys;0.3!toys.jar (2894ms)
[ivy:retrieve] :: resolution report :: resolve 11421ms :: artifacts dl 2896ms
-
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
-
| default | 1 | 1 | 1 | 0 || 1 | 1 |
| master | 0 | 0 | 0 | 0 || 0 | 0 |
| compile | 1 | 1 | 1 | 0 || 1 | 1 |
| provided | 0 | 0 | 0 | 0 || 0 | 0 |
| runtime | 1 | 1 | 1 | 0 || 1 | 1 |
| test | 1 | 1 | 1 | 0 || 1 | 1 |
| system | 0 | 0 | 0 | 0 || 0 | 0 |
| sources | 0 | 0 | 0 | 0 || 0 | 0 |
| javadoc | 0 | 0 | 0 | 0 || 0 | 0 |
| optional | 0 | 0 | 0 | 0 || 0 | 0 |
-
[ivy:retrieve] :: retrieving :: io.aklivity.sandbox#toystore
[ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
system, sources, javadoc, optional]
[ivy:retrieve] 1 artifacts copied, 0 already retrieved (1kB/11ms)
BUILD SUCCESSFUL
{quote}
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Blocker
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been
[jira] [Updated] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Robert Fallows updated IVY-1633:
-
Environment:
% java -version
java version "1.8.0_271"
Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
% ant -version
Apache Ant(TM) version 1.10.12 compiled on October 13 2021
% ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
/usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
was:
{{{}% java -version
{}}}{{{}java version "1.8.0_271"
{}}}{{{}Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
{}}}{{{}Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode){}}}
{{{}% ant -version
{}}}{{{}Apache Ant(TM) version 1.10.12 compiled on October 13 2021{}}}
{{{}% ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
{}}}{{{}/usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar{}}}
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: % java -version
> java version "1.8.0_271"
> Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
> % ant -version
> Apache Ant(TM) version 1.10.12 compiled on October 13 2021
> % ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar
>Reporter: John Robert Fallows
>Priority: Blocker
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 0 | 0 | 0 || 0 | 0 |
> | master | 0 | 0 | 0 | 0 || 0 | 0 |
> | compile | 1 | 0 | 0 | 0 || 0 | 0 |
> | provided | 0 | 0 | 0 | 0 || 0 | 0 |
> | runtime | 1 | 0 |
[jira] [Updated] (IVY-1633) Unable to follow redirects with user info in URL
[
https://issues.apache.org/jira/browse/IVY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Robert Fallows updated IVY-1633:
-
Attachment: ivy-userinfo.patch
> Unable to follow redirects with user info in URL
>
>
> Key: IVY-1633
> URL: https://issues.apache.org/jira/browse/IVY-1633
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
>Affects Versions: 2.5.0
> Environment: {{{}% java -version
> {}}}{{{}java version "1.8.0_271"
> {}}}{{{}Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
> {}}}{{{}Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode){}}}
> {{{}% ant -version
> {}}}{{{}Apache Ant(TM) version 1.10.12 compiled on October 13 2021{}}}
> {{{}% ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
> {}}}{{{}/usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar{}}}
>Reporter: John Robert Fallows
>Priority: Blocker
> Attachments: ivy-userinfo.patch
>
>
> Maven2 compatible repositories sending 302 redirect with user info embedded
> in the location response header are followed properly by Maven but not by Ivy.
> See example at [https://github.com/aklivity/toystore].
> {quote}% ./mvnw dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < io.aklivity.sandbox:toystore
> >
> [INFO] Building toystore develop-SNAPSHOT
> [INFO] [ jar
> ]-
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
> (550 B at 348 B/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
> (1.8 kB at 1.9 kB/s)
> Downloading from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> Downloaded from anonymous:
> https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
> (1.5 kB at 1.4 kB/s)
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] io.aklivity.sandbox:toys:jar:0.3:compile
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {quote}
> whereas for Ivy
> {quote}% ant
> Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
>
> resolve:
> [ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
> https://ant.apache.org/ivy/ ::
> [ivy:convertpom] :: loading settings :: file =
> /Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies ::
> io.aklivity.sandbox#toystore;develop-SNAPSHOT
> [ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
> system, sources, javadoc, optional]
> [ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
> -
> | | modules || artifacts |
> | conf | number| search|dwnlded|evicted|| number|dwnlded|
> -
> | default | 1 | 0 | 0 | 0 || 0 | 0 |
> | master | 0 | 0 | 0 | 0 || 0 | 0 |
> | compile | 1 | 0 | 0 | 0 || 0 | 0 |
> | provided | 0 | 0 | 0 | 0 || 0 | 0 |
> | runtime | 1 | 0 | 0 | 0 || 0 | 0 |
> | test | 1 | 0 | 0 | 0 || 0 | 0 |
> | system | 0 | 0 | 0 | 0 || 0 | 0 |
> | sources | 0 | 0 | 0 | 0 || 0 | 0 |
> | javadoc | 0 | 0 | 0 | 0 || 0 | 0 |
> | optional | 0 | 0 | 0 | 0 || 0 | 0 |
> -
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] WARNINGS
> [ivy:retrieve] module not found: io.aklivity.sandbox#toys;0.3
> [ivy:retrieve] ibiblio: tried
> [
[jira] [Created] (IVY-1633) Unable to follow redirects with user info in URL
John Robert Fallows created IVY-1633:
Summary: Unable to follow redirects with user info in URL
Key: IVY-1633
URL: https://issues.apache.org/jira/browse/IVY-1633
Project: Ivy
Issue Type: Improvement
Components: Maven Compatibility
Affects Versions: 2.5.0
Environment: {{{}% java -version
{}}}{{{}java version "1.8.0_271"
{}}}{{{}Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
{}}}{{{}Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode){}}}
{{{}% ant -version
{}}}{{{}Apache Ant(TM) version 1.10.12 compiled on October 13 2021{}}}
{{{}% ls /usr/local/Cellar/ant/1.10.12/libexec/lib/ivy*
{}}}{{{}/usr/local/Cellar/ant/1.10.12/libexec/lib/ivy-2.5.0.jar{}}}
Reporter: John Robert Fallows
Maven2 compatible repositories sending 302 redirect with user info embedded in
the location response header are followed properly by Maven but not by Ivy.
See example at [https://github.com/aklivity/toystore].
{quote}% ./mvnw dependency:resolve
[INFO] Scanning for projects...
[INFO]
[INFO] < io.aklivity.sandbox:toystore >
[INFO] Building toystore develop-SNAPSHOT
[INFO] [ jar ]-
Downloading from anonymous:
https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
Downloaded from anonymous:
https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
(550 B at 348 B/s)
Downloading from anonymous:
https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
Downloaded from anonymous:
https://maven.packages.aklivity.io/io/aklivity/sandbox/parent/0.3/parent-0.3.pom
(1.8 kB at 1.9 kB/s)
Downloading from anonymous:
https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
Downloaded from anonymous:
https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
(1.5 kB at 1.4 kB/s)
[INFO]
[INFO] --- maven-dependency-plugin:2.8:resolve (default-cli) @ toystore ---
[INFO]
[INFO] The following files have been resolved:
[INFO] io.aklivity.sandbox:toys:jar:0.3:compile
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{quote}
whereas for Ivy
{quote}% ant
Buildfile: /Users/jfallows/GitHub/aklivity/toystore/build.xml
resolve:
[ivy:convertpom] :: Apache Ivy 2.5.0 - 20191020104435 ::
https://ant.apache.org/ivy/ ::
[ivy:convertpom] :: loading settings :: file =
/Users/jfallows/GitHub/aklivity/toystore/ivysettings.xml
[ivy:retrieve] :: resolving dependencies ::
io.aklivity.sandbox#toystore;develop-SNAPSHOT
[ivy:retrieve] confs: [default, master, compile, provided, runtime, test,
system, sources, javadoc, optional]
[ivy:retrieve] :: resolution report :: resolve 1148ms :: artifacts dl 0ms
-
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
-
| default | 1 | 0 | 0 | 0 || 0 | 0 |
| master | 0 | 0 | 0 | 0 || 0 | 0 |
| compile | 1 | 0 | 0 | 0 || 0 | 0 |
| provided | 0 | 0 | 0 | 0 || 0 | 0 |
| runtime | 1 | 0 | 0 | 0 || 0 | 0 |
| test | 1 | 0 | 0 | 0 || 0 | 0 |
| system | 0 | 0 | 0 | 0 || 0 | 0 |
| sources | 0 | 0 | 0 | 0 || 0 | 0 |
| javadoc | 0 | 0 | 0 | 0 || 0 | 0 |
| optional | 0 | 0 | 0 | 0 || 0 | 0 |
-
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve] WARNINGS
[ivy:retrieve] module not found: io.aklivity.sandbox#toys;0.3
[ivy:retrieve] ibiblio: tried
[ivy:retrieve]
https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
[ivy:retrieve] -- artifact io.aklivity.sandbox#toys;0.3!toys.jar:
[ivy:retrieve]
https://maven.packages.aklivity.io/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
[ivy:retrieve] ibiblio: tried
[ivy:retrieve]
https://repo1.maven.org/maven2/io/aklivity/sandbox/toys/0.3/toys-0.3.pom
[ivy:retrieve] -- artifact io.aklivity.sandbox#toys;0.3!toys.jar:
[ivy:retrieve]
https://repo1.maven.org/maven2/io/aklivity/sandbox/toys/0.3/toys-0.3.jar
[ivy:retrieve] ::
[ivy:retrieve] :: UNRESOLVED DEPENDENCIES :
[jira] [Created] (IVY-1632) Ivy can't access AWS CodeArtifact Repository
Berno Langer created IVY-1632:
-
Summary: Ivy can't access AWS CodeArtifact Repository
Key: IVY-1632
URL: https://issues.apache.org/jira/browse/IVY-1632
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.5.0, 2.4.0
Reporter: Berno Langer
Ivy can't access (Maven) CodeArtifact Repositories at AWS. The Server answers
with HTTP 400 Bad Request.
After debugging and looking into the sources, I found that Ivy sends an invalid
"Accept" header. This seems to be related to
[https://bugs.openjdk.java.net/browse/JDK-8163921]
Changing the class org.apache.ivy.util.url.BasicUrlHandler, so that it sets an
Accept header after opening a connection, like this ...
{noformat}
95 con = normalizedURL.openConnection();
96 con.setRequestProperty("Accept", "*/*"); // <-- added
{noformat}
... Ivy can access CodeArtifact Repositories perfectly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (IVY-1631) ivy:retrieve task doesn't create empty set
[ https://issues.apache.org/jira/browse/IVY-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Coene resolved IVY-1631. Fix Version/s: master Resolution: Fixed > ivy:retrieve task doesn't create empty set > -- > > Key: IVY-1631 > URL: https://issues.apache.org/jira/browse/IVY-1631 > Project: Ivy > Issue Type: Bug >Affects Versions: 2.4.0, 2.5.0 >Reporter: Maarten Coene >Assignee: Maarten Coene >Priority: Major > Fix For: master > > Time Spent: 50m > Remaining Estimate: 0h > > Scenario: > * specify a setId on ivy:retrieve > * the ivy:retrieve task retrieves no files > * the target directory already contained some other files > Instead of an empty FileSet, the FileSet created by ivy:retrieve task will > contain all existing files located in that target directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IVY-1631) ivy:retrieve task doesn't create empty set
Maarten Coene created IVY-1631: -- Summary: ivy:retrieve task doesn't create empty set Key: IVY-1631 URL: https://issues.apache.org/jira/browse/IVY-1631 Project: Ivy Issue Type: Bug Affects Versions: 2.5.0, 2.4.0 Reporter: Maarten Coene Assignee: Maarten Coene Scenario: * specify a setId on ivy:retrieve * the ivy:retrieve task retrieves no files * the target directory already contained some other files Instead of an empty FileSet, the FileSet created by ivy:retrieve task will contain all existing files located in that target directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IVY-1630) get started link take me to adds websites
[ https://issues.apache.org/jira/browse/IVY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaikiran Pai resolved IVY-1630. --- Assignee: Jaikiran Pai Resolution: Fixed > get started link take me to adds websites > - > > Key: IVY-1630 > URL: https://issues.apache.org/jira/browse/IVY-1630 > Project: Ivy > Issue Type: Bug >Reporter: dyea >Assignee: Jaikiran Pai >Priority: Minor > > search in this link for > Getting Started with Apache Ivy > https://ant.apache.org/ivy/links.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IVY-1630) get started link take me to adds websites
[ https://issues.apache.org/jira/browse/IVY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426752#comment-17426752 ] Jaikiran Pai commented on IVY-1630: --- Thank you for bringing this to attention. I've updated the site to remove references to that link. > get started link take me to adds websites > - > > Key: IVY-1630 > URL: https://issues.apache.org/jira/browse/IVY-1630 > Project: Ivy > Issue Type: Bug >Reporter: dyea >Priority: Minor > > search in this link for > Getting Started with Apache Ivy > https://ant.apache.org/ivy/links.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IVY-1630) get started link take me to adds websites
dyea created IVY-1630: - Summary: get started link take me to adds websites Key: IVY-1630 URL: https://issues.apache.org/jira/browse/IVY-1630 Project: Ivy Issue Type: Bug Reporter: dyea search in this link for Getting Started with Apache Ivy https://ant.apache.org/ivy/links.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IVY-1629) Add attribute to force ivy:info not using the cache
[ https://issues.apache.org/jira/browse/IVY-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17326263#comment-17326263 ] Maxime Andrighetto commented on IVY-1629: - In my case, a better workaround than cleaning all the cache is to use ivy.resolver.default.check.modified before the configuration of Ivy. However one might want to call ivy:info after the configuration of ivy...? > Add attribute to force ivy:info not using the cache > --- > > Key: IVY-1629 > URL: https://issues.apache.org/jira/browse/IVY-1629 > Project: Ivy > Issue Type: Improvement >Reporter: Maxime Andrighetto >Priority: Major > > Info retrieved from the cache is sometimes different than from the real Ivy > repository. Currently the solution is to clean cache prior to executing > ivy:info, but this defeats the purpose of the cache for other tasks... > Please add an attribute to force not use the cache when calling ivy:info (the > same attribute may be used by 'resolve' or other post resolve tasks btw). > This would be really helpful! > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IVY-1629) Add attribute to force ivy:info not using the cache
Maxime Andrighetto created IVY-1629: --- Summary: Add attribute to force ivy:info not using the cache Key: IVY-1629 URL: https://issues.apache.org/jira/browse/IVY-1629 Project: Ivy Issue Type: Improvement Reporter: Maxime Andrighetto Info retrieved from the cache is sometimes different than from the real Ivy repository. Currently the solution is to clean cache prior to executing ivy:info, but this defeats the purpose of the cache for other tasks... Please add an attribute to force not use the cache when calling ivy:info (the same attribute may be used by 'resolve' or other post resolve tasks btw). This would be really helpful! Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IVY-1616) useOrigin="true" fails with file-based ibiblio
[
https://issues.apache.org/jira/browse/IVY-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaikiran Pai resolved IVY-1616.
---
Fix Version/s: master
Resolution: Fixed
This is now fixed and should be available in next release.
> useOrigin="true" fails with file-based ibiblio
> --
>
> Key: IVY-1616
> URL: https://issues.apache.org/jira/browse/IVY-1616
> Project: Ivy
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Eric Milles
>Assignee: Jaikiran Pai
>Priority: Major
> Fix For: master
>
>
> We are trying to use Maven's artifacts if they have already been downloaded.
> To that end, we have a file-based {{ibiblio}} resolver that points to the
> local .m2 repository directory. If maven is used to download an artifact so
> that it is in .m2 and not in Ivy's cache, we are getting errors from the
> origin check in {{DefaultRepositoryCacheManager}}.
> {code}
> java.lang.IllegalArgumentException:
> org.apache.maven.shared#maven-shared-utils;3.2.1!maven-shared-utils.jar
> origin location must be absolute:
> file:/C:/Users/Name/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.2.1/maven-shared-utils-3.2.1.jar
> at org.apache.ivy.util.Checks.checkAbsolute(Checks.java:57)
> at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getArchiveFileInCache(DefaultRepositoryCacheManager.java:410)
> at
> org.apache.ivy.core.cache.DefaultRepositoryCacheManager.download(DefaultRepositoryCacheManager.java:996)
> at
> org.apache.ivy.plugins.resolver.BasicResolver.download(BasicResolver.java:836)
> at
> org.apache.ivy.plugins.resolver.RepositoryResolver.download(RepositoryResolver.java:305)
> at
> org.apache.ivy.plugins.resolver.IBiblioResolver.download(IBiblioResolver.java:563)
> at
> org.apache.ivy.core.resolve.ResolveEngine.downloadArtifacts(ResolveEngine.java:405)
> at
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:351)
> at org.apache.ivy.Ivy.resolve(Ivy.java:522)
> {code}
> {code:xml}
>
>
>
>
>checkmodified="true" changingPattern=".*" changingMatcher="regexp"
> m2compatible="true"/>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IVY-1615) Ivy standalone : specify settings from URL
[
https://issues.apache.org/jira/browse/IVY-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaikiran Pai resolved IVY-1615.
---
Fix Version/s: master
Resolution: Fixed
Thank you for that patch. I've merged it along with a test case and credited
you for that contribution.
> Ivy standalone : specify settings from URL
> --
>
> Key: IVY-1615
> URL: https://issues.apache.org/jira/browse/IVY-1615
> Project: Ivy
> Issue Type: Improvement
> Components: Core
>Affects Versions: 2.5.0
>Reporter: Jason A. Guild
>Assignee: Jaikiran Pai
>Priority: Minor
> Labels: CLI, settings, standalone
> Fix For: master
>
> Attachments: cli_ivysettings_from_url.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using ivy in standalone mode via CLI, allow the {{-settings}} option to
> read xml settings from a URL instead of a filesystem path. This allows
> convenient access to centralized settings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IVY-1615) Ivy standalone : specify settings from URL
[
https://issues.apache.org/jira/browse/IVY-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaikiran Pai reassigned IVY-1615:
-
Assignee: Jaikiran Pai
> Ivy standalone : specify settings from URL
> --
>
> Key: IVY-1615
> URL: https://issues.apache.org/jira/browse/IVY-1615
> Project: Ivy
> Issue Type: Improvement
> Components: Core
>Affects Versions: 2.5.0
>Reporter: Jason A. Guild
>Assignee: Jaikiran Pai
>Priority: Minor
> Labels: CLI, settings, standalone
> Attachments: cli_ivysettings_from_url.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using ivy in standalone mode via CLI, allow the {{-settings}} option to
> read xml settings from a URL instead of a filesystem path. This allows
> convenient access to centralized settings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IVY-1618) ResolveEngine resets dictator resolver to null in the global configuration
[
https://issues.apache.org/jira/browse/IVY-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaikiran Pai resolved IVY-1618.
---
Fix Version/s: master
Resolution: Fixed
> ResolveEngine resets dictator resolver to null in the global configuration
> --
>
> Key: IVY-1618
> URL: https://issues.apache.org/jira/browse/IVY-1618
> Project: Ivy
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.5.0
> Environment: Windows 10, Java 8, Ivy 2.5.0.
>Reporter: Sergei Zhirikov
>Assignee: Jaikiran Pai
>Priority: Minor
> Fix For: master
>
>
> ResolveEngine does not initialize its dictatorResover field in the
> constructor. As the result, when
> {code:java}
> public ResolveReport resolve(ModuleDescriptor md, ResolveOptions
> options){code}
> is called, the {{oldDictator}} local variable will be set to null in the
> beginning of the method. Then, in the end of the same method, inside the
> {{finally}} block, {{setDictatorResolver(null)}} will be called, which will
> not only set the private field in the ResolveEngine itself, but will also
> reset the dictator resolver in the global configuration. Why would it do
> that???
> The problem manifests itself when an {{Ivy}} instance is configured (using
> Java API) with only a dictator resolver, it will be able to handle a single
> call to {{resolve(...)}} successfully, and all subsequent calls will fail
> because of "no resolver available" (because the one that is supposed to be
> available, has been reset by the ResolveEngine, as described above).
> I have to admit that I am not very familiar with Ivy internals, but I find it
> extremely puzzling that an object that is a part of the internal
> implementation would change the global configuration at will.
> Looking at the implementation of {{Ivy}} and {{IvyContext}} classes, I get
> the impression that an {{Ivy}} instance is supposed to be thread-safe, in the
> sense that it should allow to call {{resolve(...)}} on the same instance from
> multiple threads safely. Am I mistaken? If there is supposed to be any thread
> safety, it is broken by the peculiar behavior of ResolveEngine with respect
> to setting the dictator resolver.
> In any case, I think it would be really helpful to explicitly mention thread
> safety (or lack thereof) in the Javadoc page of the main {{Ivy}} class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
