Return-Path: 
 <notifications-return-821-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@locus.apache.org
Received: (qmail 57621 invoked from network); 4 Feb 2008 22:29:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Feb 2008 22:29:29 -0000
Received: (qmail 4321 invoked by uid 500); 4 Feb 2008 22:29:20 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 4280 invoked by uid 500); 4 Feb 2008 22:29:20 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 4262 invoked by uid 99); 4 Feb 2008 22:29:20 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 14:29:20 -0800
X-ASF-Spam-Status: No, hits=-98.5 required=10.0
	tests=ALL_TRUSTED,WEIRD_PORT
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 22:29:00 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id B95B371403C
	for <notifications@ant.apache.org>; Mon,  4 Feb 2008 14:29:07 -0800 (PST)
Message-ID: <24450646.1202164147749.JavaMail.jira@brutus>
Date: Mon, 4 Feb 2008 14:29:07 -0800 (PST)
From: "Maarten Coene (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Reopened: (IVY-716) repreport task not working against a
 repository structured by branches
In-Reply-To: <12863939.1202157667873.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/IVY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene reopened IVY-716:
-------------------------------


ok, I see it now...
You won't get this error message any longer when using beta1, but the report won't be correct (you'll probably get an empty report without any warning).

Isn't the real problem that in SearchEngine we assume that the [organisation] token must come before the [module] token, which must come before the [branch] token? Maybe we could refactor this en let the resolver decide for the correct order of tokens (the resolver knows the pattern if it uses one) and add a ModuleRevisionId[] listModules(ModuleRevisionId criteria, PatternMatcher matcher) method to the Resolver interface?

> 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
>
> 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.