[
https://issues.apache.org/jira/browse/MNG-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MNG-7436:
--------------------------------
Description:
We currently have a [bug-report at
tycho|https://github.com/eclipse/tycho/issues/781] that complains about missing
dependency resolution.
It seems that a dependency with system scope but missing path triggers this
(something that should be fixed of course), but I think maven should be a bit
more forgiven here:
Instead of failing completely, it should simply skip the "bad" dependency. If
that's not feasible , in any case it should clearly indicate the causing item
in the pom.
was:
We currently have a[ bug-report at
tycho|https://github.com/eclipse/tycho/issues/781] that complains about missing
dependency resolution.
It seems that a dependency with system scope but missing path triggers this
(something that should be fixed of course), but I think maven should be a bit
more forgiven here:
Instead of failing completely, it should simply skip the "bad" dependency. If
that's not feasible , in any case it should clearly indicate the causing item
in the pom.
> Do not fail if there is one bad dependency
> ------------------------------------------
>
> Key: MNG-7436
> URL: https://issues.apache.org/jira/browse/MNG-7436
> Project: Maven
> Issue Type: Improvement
> Reporter: Christoph Läubrich
> Priority: Major
>
> We currently have a [bug-report at
> tycho|https://github.com/eclipse/tycho/issues/781] that complains about
> missing dependency resolution.
> It seems that a dependency with system scope but missing path triggers this
> (something that should be fixed of course), but I think maven should be a bit
> more forgiven here:
> Instead of failing completely, it should simply skip the "bad" dependency. If
> that's not feasible , in any case it should clearly indicate the causing item
> in the pom.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
