[
https://issues.apache.org/jira/browse/IVY-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478965
]
Stephane Bailliez commented on IVY-419:
---------------------------------------
I agree with maarteen, I think it should be really about specifying 'any' kind
of parameter (classifier or not it's not the issue, since it could perfectly be
things like 'platform' and 'architecture', etc..) and having a proper resolver
that grabs the artifacts.
> define artifacts not declared by the dependency module descriptor
> -----------------------------------------------------------------
>
> Key: IVY-419
> URL: https://issues.apache.org/jira/browse/IVY-419
> Project: Ivy
> Issue Type: New Feature
> Affects Versions: 1.4.1
> Reporter: Xavier Hanin
> Fix For: 1.5
>
>
> When you don't control your dependency module descriptor (using a public repo
> for example) it happens that you want more control over the dependency.
> For the moment, it's possible to define artifacts for the dependency only if
> the dependency has no module descriptor. What would be interesting would be
> to be able to declare such artifacts even when the dependency has a module
> descriptor. To be sure this is what is requested by the user, a boolean
> attribute would be use on the dependency artifact declaration:
> {code:xml}
> <dependency org="foo" name="bar" rev="1.0">
> <artifact name="baz" type="source" ext="jar" assumePublished="true"/>
> </dependency>
> {code}
> This feature would also help implement maven2 classifiers (see IVY-418)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
