[ https://issues.apache.org/jira/browse/IVY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575076#action_12575076
]
Ross Camara commented on IVY-716:
---------------------------------
It would be very useful to be able to specify the order the tokens.
In a standard repository it makes sense to generally have [org]/[mod]/[rev]. However in an
enterprise situation you some times would want to group the modules based on a release revision.
This functionality is especially useful when using a file system for the repository where
it might be accessed outside of the ivy framework.
> repreport task not working against a repository structured by branches
> ----------------------------------------------------------------------
>
> Key: IVY-716
> URL: https://issues.apache.org/jira/browse/IVY-716
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0-alpha-2
> Environment: Windows XP, IBM JDK 1.5
> Reporter: Antoine Levy-Lambert
> Assignee: Maarten Coene
> Fix For: 2.0
>
>
> I am trying to use the repreport task like this
> <ivy:repreport organisation="saic" branch="5.1" module="foo" revision="FOO_5.1.0.413"
matcher="glob" />
> here are my settings :
> <ivysettings>
> <settings defaultResolver="http-resolver"
> defaultBranch="${ivy.branch}"/>
> <resolvers>
> <url name="http-resolver">
> <ivy pattern="${repository.http.url}/[organisation]/[module]/[revision]/ivy.xml"/>
> <artifact pattern="${repository.http.url}/[organisation]/[module]/[revision]/[artifact].[ext]"/>
> </url>
> <url name="http-branch-resolver">
> <ivy pattern="${repository.http.url}/[organisation]/[branch]/[module]/[revision]/ivy.xml"/>
> <artifact pattern="${repository.http.url}/[organisation]/[branch]/[module]/[revision]/[artifact].[ext]"/>
> </url>
> </resolvers>
> <modules>
> <module organisation="saic" name="*" resolver="http-branch-resolver"/>
> </modules>
> </ivysettings>
> I see the following standard out :
> [ivy:repreport] :: problems summary ::
> [ivy:repreport] :::: WARNINGS
> [ivy:repreport] problem while listing resources in http://ivyrepo:8060/ivyrepo/saic/[branch]/
with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri 'http://ivyrepo:8060/ivyrepo/saic/[branch]/':
escaped absolute path not valid
> [ivy:repreport] problem while listing resources in http://ivyrepo:8060/ivyrepo/saic/[branch]/
with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri 'http://ivyrepo:8060/ivyrepo/saic/[branch]/':
escaped absolute path not valid
> [ivy:repreport] problem while listing resources in http://ivyrepo:8060/ivyrepo/saic/[branch]/
with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri 'http://ivyrepo:8060/ivyrepo/saic/[branch]/':
escaped absolute path not valid
> [ivy:repreport] problem while listing resources in http://ivyrepo:8060/ivyrepo/saic/[branch]/
with http-branch-resolver:
> [ivy:repreport] java.lang.IllegalArgumentException Invalid uri 'http://ivyrepo:8060/ivyrepo/saic/[branch]/':
escaped absolute path not valid
> [ivy:repreport]
> Replacing [branch] by its value in my settings file is a workaround.
> Looking at the source code from SVN, it looks like public ModuleId[] listModules(ModuleId
criteria, PatternMatcher matcher) {
> in org.apache.ivy.core.search.SearchEngine is involved in the work.
> Should a new version of listModules be created, having also a branch as parameter ?
> A more powerful solution might be to create a new class extending ModuleId, adding a
branch field to the instance variables, and to code using this class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|