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 "Xavier Hanin (JIRA)" <ji...@apache.org> on 2006/12/07 12:59:32 UTC

[jira] Commented: (IVY-351) Most ivyconfs in the build-a-ivy-repository example directory uses a wrong artifact pattern

    [ http://issues.apache.org/jira/browse/IVY-351?page=comments#action_12456394 ] 
            
Xavier Hanin commented on IVY-351:
----------------------------------

Yes, and there are other places with the same problem... The distinction between type and ext was not part of the very first ivy versions, thus there is still some bad habits remaining. This is not good, especially for tutorials :-)

> Most ivyconfs in the build-a-ivy-repository example directory uses a wrong artifact pattern
> -------------------------------------------------------------------------------------------
>
>                 Key: IVY-351
>                 URL: http://issues.apache.org/jira/browse/IVY-351
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Jacob Grydholt Jensen
>            Priority: Trivial
>
> In the build-a-ivy-repository example, the configurations:
> ivy-conf-advanced.xml
> ivy-conf-basic.xml
> ivy-conf-maven1.xml
> ivy-conf-maven2.xml
> uses the following artifact pattern:
> <artifact pattern="${dest.repo.dir}/[organisation]/[module]/[type]s/[artifact]-[revision].[type]" /> 
> The last [type] variable should be [ext].

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira