[
https://issues.apache.org/jira/browse/IVY-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636595#action_12636595
]
Xavier Hanin commented on IVY-931:
----------------------------------
Indeed, maybe it's the best option, but if we want to go this way we have to
release it before 2.0 because it will break backward compatibility. The other
option is to break only if a dependency has no revision, and only warn when we
can't locate the parent. I don't have a strong opinion on this, what do others
think?
> Ivy badly attempt to locate a 'working@<host>' dependency revision when the
> dependency revision is not set in a pom
> -------------------------------------------------------------------------------------------------------------------
>
> Key: IVY-931
> URL: https://issues.apache.org/jira/browse/IVY-931
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0-RC1
> Reporter: Xavier Hanin
>
> If in a pom a dependency is declared without revision, Ivy interprets it as a
> 'working@<host>' revision, which is very confusing. This may happen for
> instance when Ivy cannot locate a parent pom which contains a
> dependencyManagement section.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
