[jira] [Updated] (MRESOLVER-10) New class 'TransitiveDependencyManager' supporting transitive dependency management.
[
https://issues.apache.org/jira/browse/MRESOLVER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MRESOLVER-10:
Fix Version/s: (was: Maven Artifact Resolver 1.2.0 pre-reset)
1.4.0
> New class 'TransitiveDependencyManager' supporting transitive dependency
> management.
>
>
> Key: MRESOLVER-10
> URL: https://issues.apache.org/jira/browse/MRESOLVER-10
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 1.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{ClassicDependencyManager}} ignores the dependency management from
> transitive dependencies to maintain backwards compatibility with Maven 2,
> then Maven 3 (objective when extracting Aether was to keep compatibility).
> The new {{TransitiveDependencyManager}} will use that dependency management:
> this new behaviour is expected to be a better choice. Once it is integrated
> into Maven core (version to be defined) as default new behaviour = a
> behaviour that is more predictible/logical, but that will break some
> previously working builds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MRESOLVER-10) New class 'TransitiveDependencyManager' supporting transitive dependency management.
[
https://issues.apache.org/jira/browse/MRESOLVER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MRESOLVER-10:
---
Description:
The {{ClassicDependencyManager}} ignores the dependency management from
transitive dependencies to maintain backwards compatibility with Maven 2, then
Maven 3 (objective when extracting Aether was to keep compatibility).
The new {{TransitiveDependencyManager}} will use that dependency management:
this new behaviour is expected to be a better choice. Once it is integrated
into Maven core (version to be defined) as default new behaviour = a behaviour
that is more predictible/logical, but that will break some previously working
builds.
was:
The {{ClassicDependencyManager}} ignores the dependency management from
transitive dependencies to maintain backwards compatibility with Maven 2, then
Maven 3 (objective when extracting Aether was to keep compatibility).
The new {{TransitiveDependencyManager}} will use that dependency management:
this new behaviour is expected to be a better choice.
It could also be named {{DefaultDependencyManager}}, once it is integrated into
Maven core (version to be defined) as default new behaviour = a behaviour that
is more predictible/logical, but that will break some previously working builds.
> New class 'TransitiveDependencyManager' supporting transitive dependency
> management.
>
>
> Key: MRESOLVER-10
> URL: https://issues.apache.org/jira/browse/MRESOLVER-10
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Maven Artifact Resolver 1.2.0 pre-reset
>
>
> The {{ClassicDependencyManager}} ignores the dependency management from
> transitive dependencies to maintain backwards compatibility with Maven 2,
> then Maven 3 (objective when extracting Aether was to keep compatibility).
> The new {{TransitiveDependencyManager}} will use that dependency management:
> this new behaviour is expected to be a better choice. Once it is integrated
> into Maven core (version to be defined) as default new behaviour = a
> behaviour that is more predictible/logical, but that will break some
> previously working builds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MRESOLVER-10) New class 'TransitiveDependencyManager' supporting transitive dependency management.
[
https://issues.apache.org/jira/browse/MRESOLVER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MRESOLVER-10:
---
Description:
The {{ClassicDependencyManager}} ignores the dependency management from
transitive dependencies to maintain backwards compatibility with Maven 2, then
Maven 3 (objective when extracting Aether was to keep compatibility).
The new {{TransitiveDependencyManager}} will use that dependency management:
this new behaviour is expected to be a better choice.
It could also be named {{DefaultDependencyManager}}, once it is integrated into
Maven core (version to be defined) as default new behaviour = a behaviour that
is more predictible/logical, but that will break some previously working builds.
was:
The {{ClassicDependencyManager}} ignores the dependency management from
transitive dependencies to maintain backwards compatibility with Maven 2. The
{{TransitiveDependencyManager}} will correctly use that dependency management
(it could also be named {{DefaultDependencyManager}}).
> New class 'TransitiveDependencyManager' supporting transitive dependency
> management.
>
>
> Key: MRESOLVER-10
> URL: https://issues.apache.org/jira/browse/MRESOLVER-10
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> The {{ClassicDependencyManager}} ignores the dependency management from
> transitive dependencies to maintain backwards compatibility with Maven 2,
> then Maven 3 (objective when extracting Aether was to keep compatibility).
> The new {{TransitiveDependencyManager}} will use that dependency management:
> this new behaviour is expected to be a better choice.
> It could also be named {{DefaultDependencyManager}}, once it is integrated
> into Maven core (version to be defined) as default new behaviour = a
> behaviour that is more predictible/logical, but that will break some
> previously working builds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
