ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-803) Cache can't distinguish artifacts with classifiers
Date Thu, 24 Apr 2008 06:49:22 GMT

    [ https://issues.apache.org/jira/browse/IVY-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591935#action_12591935
] 

Xavier Hanin commented on IVY-803:
----------------------------------

Using original name could be interesting, but the problem is that we don't know what is actually
used in the original name. For instance, the pattern "[organisation]/[module]/[type]s/[originalname]"
would lead to issues if the original name doesn't contain the revision. This could be solved
by putting all known tokens in the directory name. But I see another drawback: with this pattern
the cache wouldn't be unified anymore. Currently it's pretty easy to create tools analyzing
the cache. With originalname token as artifact name, we don't control the file name, and depending
on module origin we may have a very inconsistent cache. It can be bad also if you use the
same cache with different settings, picking modules from different resolvers, with some modules
shared available in different repositories, with different names.

For these reasons I'd prefer to use the solution to introduce the classifier token in pattern,
as James did in the patch.

> Cache can't distinguish artifacts with classifiers
> --------------------------------------------------
>
>                 Key: IVY-803
>                 URL: https://issues.apache.org/jira/browse/IVY-803
>             Project: Ivy
>          Issue Type: Bug
>          Components: Maven Compatibility
>    Affects Versions: 2.0.0-beta-2
>            Reporter: James P. White
>         Attachments: ivy803patch.txt
>
>
> Once an artifact with a Maven classifier is in the cache, then that will match any classifier
value.
> Presumably the fix is to include the classifier in the artifact pattern for the cache.
> But this seems a little obnoxious since AFAICT this problem may exist with all artifact
patterns.

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


Mime
View raw message