[
https://issues.apache.org/jira/browse/IVY-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612651#action_12612651
]
Xavier Hanin commented on IVY-829:
----------------------------------
It's weird. My working copy is clean, so I have no pending changes. Unit tests
pass on by box with no problem (a linux box). And if I check the changes done
on July 2nd, I don't see how it can make the test fail at line 138. What's also
weird is that almost no console output is captured in the junit report, so it
makes it difficult to understand what's happening... I've even run the test
target on my box from a different directory than ivy root, and it still works.
So I really don't see what can be causing the problem.
> Add new "packager" resolver to Ivy
> ----------------------------------
>
> Key: IVY-829
> URL: https://issues.apache.org/jira/browse/IVY-829
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.0-beta-2
> Reporter: Archie Cobbs
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
> Attachments: m2repo.tgz, packager-resolver-patch.txt
>
>
> Feature request to add a new resolver, called the "Packager Resolver",
> [described
> here|http://ivyroundup.googlecode.com/svn/wiki/files/packager.html].
> Patch is attached and also available
> [here|http://ivyroundup.googlecode.com/svn/wiki/files/packager-resolver.patch].
> Patch contains binary test files, so to apply it you have to follow the
> [simple steps described here|http://code.google.com/p/ivyroundup/].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
