[
https://issues.apache.org/jira/browse/IVY-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478964
]
Stephane Bailliez commented on IVY-419:
---------------------------------------
Frankly I'm not exactly convinced here.... Especially when the rationale is to
support the classifier in maven and it leaks that way.
- You're providing a shortcut to have this defined...within the descriptor
that's not exactly great. To me it's worth spending 2 minutes to have a mapping
defined that your resolvers will use, because while it could be justifiable to
not do that for a single project (bur frankly you start to spread the
logic)...surely this cut it over 2 projects that reference the same dependency
this way and it starts to become a mess.
- You're basically providing a way to define a module descriptor of a
dependency within a module descriptor. That seems pretty weird, are you also
defining dependencies of the same artifact you define that way ? coz we should
not be far from being able to provide nested module descriptor right ?
- Assuming this is needed which I'm far from being convinced yet and would need
sleep and some time to understand that, looking at the attribute
what sense would it make to define an artifact with assumePublished=false ?
> 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.
