)
[ivy:retrieve] at org.apache.ivy.Ivy.resolve(Ivy.java:507)
The exception looks like issue, IVY-1566, which is resolved in 2.5.0-rc1.
However, the exception still exists in this example which is using the
2.5.0-rc1 version.
On Mon, Aug 13, 2018 at 8:51 AM, t4rockets wrote:
> Using the dependence example, it h
The issue with downloading a replaced artifact in a filesystem repository
was solved using the "changing=true" attribute in the Ivy file for dependee
dependency. However, the MalformedURLException is still happening.
On Mon, Aug 13, 2018 at 10:54 AM, t4rockets wrote:
>
n.startAnt(Main.java:223)
[ivy:retrieve] at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
[ivy:retrieve] at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
On Tue, Aug 14, 2018 at 10:30 PM, Jaikiran Pai wrote:
> Hi t4rockets,
>
>
> On 14/08/18 8:46 PM
way, if curl itself can't get to the maven-metadata.xml file (noted
> in the logs above), then that's an issue that needs to be sorted at Nexus
> configuration, IMO.
>
> -Jaikiran
>
>
>
> On 13/07/18 7:02 PM, t4rockets wrote:
>
>> The resolver for NXRM is a standa
When Ivy 2.4.0 is requesting header information during an ivy:buildnumber
task, NXRM 3.x is returning for 404 error code indicating the page was not
found. Because of the 404 error, the buildnumber task can not determine
the current build number so that it can be incremented.
The Ivy
;
> On 12/07/18 11:33 PM, t4rockets wrote:
>
>> When Ivy 2.4.0 is requesting header information during an ivy:buildnumber
>> task, NXRM 3.x is returning for 404 error code indicating the page was not
>> found. Because of the 404 error, the buildnumber task can not determi
The key software components of this question are Ant with Ivy 2.4.0,
Jenkins, and Sonatype Nexus 3.14. The classifier attribute is being used
to build different OS artifacts (name = baz, e:classifier="el5.x86_66" )
via different Jenkins jobs (i.e. different Jenkins build IDs). The Jenkins
jobs
