[
https://issues.apache.org/jira/browse/MNG-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565744#comment-16565744
]
Gordon Pettey edited comment on MNG-6378 at 8/1/18 6:20 PM:
------------------------------------------------------------
Since there's no {{<scope>import</scope>}} for {{<pluginManagement>}}, there's
no support for {{<pluginManagement>}} in profiles, and there's no Xinclude,
this would at least allow my top-level {{<dependencyManagement>}} pom to
specify properties for plugin versions. Also:
* dependencies whose versions are additionally used in a {{<profile>}} for
additional artifacts, e.g. Checker Framework.
* {{<links>}} to javadoc which are not at the default URL m-javadoc-p expects,
but can be located using the same version property (e.g. every apache commons
dependency)
* interpolated resources referencing version properties
This usage should be considered for PDT so it doesn't become yet another thing
that can't be fixed ever because the model is set in stone.
{{<dependencyManagement>}} does not exist completely isolated from the rest of
the project. I like Maven for preventing the spaghetti builds that I see in ant
and gradle, but the duplication and kitchen-sink-pom I end up with from the
lack of any kind of multiple-inheritance or composition method for anything but
{{<dependencies>}} is a problem.
was (Author: gpettey):
Since there's no {{<scope>import</scope>}} for {{<pluginManagement>}}, there's
no support for {{<pluginManagement>}} in profiles, and there's no Xinclude,
this would at least allow my top-level {{<dependencyManagement>}} pom to
specify properties for plugin versions. Also:
* dependencies whose versions are additionally used in a {{<profile>}} for
additional artifacts, e.g. Checker Framework.
* {{<links>}} to javadoc which are not at the default URL m-javadoc-p expects,
but can be located using the same version property (e.g. every apache commons
dependency)
* interpolated resources referencing version properties
This usage should be considered for PDT so it doesn't become yet another thing
that can't be fixed ever because the model is set in stone.
{{<dependencyManagement>}} does not exist completely isolated from the rest of
the project.
> Properties from POM in import scope should be resolvable in the project
> -----------------------------------------------------------------------
>
> Key: MNG-6378
> URL: https://issues.apache.org/jira/browse/MNG-6378
> Project: Maven
> Issue Type: Improvement
> Reporter: Jakub Kubrynski
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> Properties defined in the POM that is in the import scope in the
> dependencyManagement section should be able to resolve in the project. It's
> especially important in the framework (like Spring) using BOM patterns
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
