Ok, I seem to have found the issue.
It appears to test errors, it has Ivy requesting an invalid URL for a given
artifact. However, the HTML returned by my internet provider is returning
a legitmate document that throws a SAX exception which is uncaught and
bleeds all the way to the test.
Are
So, for the sbt project we noticed significant resolution time improvements
with the following patch:
https://github.com/sbt/ivy/pull/1
The reasoning:
- A lot of artifacts being resolved use Maven's dependencyManagement
conventions
- Ivy appears to turn these into exact matcher rules
I had started this a few months back (
https://github.com/mc1arke/ant/tree/JUnit4Conversion) but got side-tracked
due to a job change. I'd be happy to go back and continue/finish the work
if there's a general demand for it.
On 31 March 2014 01:14, Matt Sicker boa...@gmail.com wrote:
I'd be a
Hello Michael,
yes please go back and continue this, this is interesting.
@Matt we are always happy to have new volunteers to help us maintain Ant :-)
Ant’s minimum Java version is 1.5 so we are good on that side.
Regards,
Antoine
On Mar 31, 2014, at 5:28 PM, Michael Clarke
Hello Josh,
thanks for contacting the Ant/Ivy community.
I think we can work with pull requests on github, as long as we see clearly the
diffs with the code in the svn repository we should be fine.
@Maarten, Nicolas, and others in the Ivy community, do you think we can merge
this before
