You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "James Poli (JIRA)" <ji...@apache.org> on 2007/06/15 13:12:25 UTC

[jira] Created: (IVY-528) repreport task does not support repositories with no organisation token.

repreport task does not support repositories with no organisation token.
------------------------------------------------------------------------

                 Key: IVY-528
                 URL: https://issues.apache.org/jira/browse/IVY-528
             Project: Ivy
          Issue Type: Bug
    Affects Versions: 1.4.1
         Environment: Linux
            Reporter: James Poli


On 6/14/07, James Poli <Ja...@sas.com> wrote:
>
> Hello,
>
> We've created an ivy repository only containing ivy.xml files that 
> point to our already built jar repository.  Our resolver works fine 
> with our pattern's (note no organisation) of:
>
> <ivy pattern="<ivy repo 
> location>/[module]_[revision]/META-INF/ivy.xml" /> <artifact 
> pattern="<jar repo
> location>/[module]_[revision]/[artifact].[ext]" />
>
> But when I run repreport I get:
> ...
> [ivy:repreport] unable to list organisation in
> /sasusr/playpens/japoli/repo_JUN06_1250_gvjr/[module]_[revision]/META-INF/ivy.xml:
> token not found in pattern
> ...
>
> Question: Is there a way I generate a report if our repository(s)  
> don't contain an organisation in the directory structure?  We've
>                stored the organisation in our ivy.xml files.


The repreport task is still too limited ATM, and does not support repositories with no organisation token. We also have a bug with m2compatible repos. Please open a JIRA issue requesting this enhancement.

Xavier

Thanks in advance,
> Jim
>
>
>


--
Xavier Hanin - Independent Java Consultant Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-528) repreport task does not support repositories with no organisation token.

Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilles Scokart updated IVY-528:
-------------------------------

    Fix Version/s: 2.0

> repreport task does not support repositories with no organisation token.
> ------------------------------------------------------------------------
>
>                 Key: IVY-528
>                 URL: https://issues.apache.org/jira/browse/IVY-528
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: Linux
>            Reporter: James Poli
>             Fix For: 2.0
>
>
> On 6/14/07, James Poli <Ja...@sas.com> wrote:
> >
> > Hello,
> >
> > We've created an ivy repository only containing ivy.xml files that 
> > point to our already built jar repository.  Our resolver works fine 
> > with our pattern's (note no organisation) of:
> >
> > <ivy pattern="<ivy repo 
> > location>/[module]_[revision]/META-INF/ivy.xml" /> <artifact 
> > pattern="<jar repo
> > location>/[module]_[revision]/[artifact].[ext]" />
> >
> > But when I run repreport I get:
> > ...
> > [ivy:repreport] unable to list organisation in
> > /sasusr/playpens/japoli/repo_JUN06_1250_gvjr/[module]_[revision]/META-INF/ivy.xml:
> > token not found in pattern
> > ...
> >
> > Question: Is there a way I generate a report if our repository(s)  
> > don't contain an organisation in the directory structure?  We've
> >                stored the organisation in our ivy.xml files.
> The repreport task is still too limited ATM, and does not support repositories with no organisation token. We also have a bug with m2compatible repos. Please open a JIRA issue requesting this enhancement.
> Xavier
> Thanks in advance,
> > Jim
> >
> >
> >
> --
> Xavier Hanin - Independent Java Consultant Manage your dependencies with Ivy!
> http://incubator.apache.org/ivy/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.