[
https://issues.apache.org/jira/browse/IVY-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613500#action_12613500
]
Archie Cobbs commented on IVY-829:
----------------------------------
My guess would be some Windows-specific problem with the {{<pathconvert>}} tag
in the generated ant build file (see
{{C:\projects\ivy\trunk\build\test\PackagerResolverTest\build\org\mod\1.0\packager-output.xml}}).
I thought this should be O/S independent because it specifies {{pathsep="/"}}
and the result is used for an URL (not a file pathname)... ?
The goal here is simply to convert a maven2 groupId like {{org.apache.foo}}
into an URL subdirectory fragment like {{org/apache/foo}}.
The result in the test is that it should be looking for
{{../m2repo/org/apache/ivy/foobar/1.0/...}} instead of
{{../m2repo//foobar/1.0/...}}. Looks like somehow the {{<pathconvert>}} is
returning the empty string.
> 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, test-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.