[
https://issues.apache.org/jira/browse/MNG-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565840#comment-16565840
]
Karl Heinz Marbaise commented on MNG-6378:
------------------------------------------
* The question is why do you need properties for your plugin versions if you
already using {{pluginManagement}} that exactly the use case to define the
plugin versions in {{pluginManagement}}.
* Dependencies can be controlled with {{dependencyManagement}} which also is
valid for dependencies which you might use in profiles (which is a little bit
strange ?) Can you give an concrete example?
* Additional artifacts shouldn't be defined in profile better use separate
module for it...
* If I correctly understand that point with the links could already being
defined in the above given pluginManagement ?
* What do you mean by interpolated resources referencing version properties?
Can you give a concrete example for that ?
Apart from that I think I can say here already that this will not be changed in
Maven 3.X cause that would break compatibility.
> 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)
