[
https://issues.apache.org/jira/browse/IVY-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479304
]
Xavier Hanin commented on IVY-419:
----------------------------------
I agree with your point of view, but IMO Ivy is not an opinionated tool but a
flexible tool. As such it supports things that I don't like. Take for instance
the url attribute on artifact. This is something I really dislike, but it was
requested by so many users that I thought it was worth implementing. Simply
because it lowers the barrier of entry.
The point is that many users start using Ivy with no experience of dependency
management, and want it to be as simple to use as possible, with no
configuration at all. I agree that adding options and features is not the best
way to make things simple, but this kind of feature is something that can help
people to start using Ivy without having to setup their own repository.
And when you say that your repository is versioned, this is a good practice,
but it's not the case for everybody. And when speaking about maven repository
where jars change, it's really dangerous, but should we remove the support for
this huge public repo? I don't think so. I even think that this is something
that makes maven2 compelling, the out of the box experience is very good at
first sight.
But if others think this feature is a bad thing for Ivy, I'll remove it, or at
least undocument it, because I still need a way to deal with maven2
classifiers, and for the moment I see no other one.
> 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.
