You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/02/20 19:32:00 UTC
[jira] [Commented] (MNG-6596) maven should not make assumptions on
the location of the parent pom
[ https://issues.apache.org/jira/browse/MNG-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773311#comment-16773311 ]
Michael Osipov commented on MNG-6596:
-------------------------------------
I don't understand this request. If the parent POM is not available locally it will be downloaded. Where is the issue here?
> maven should not make assumptions on the location of the parent pom
> -------------------------------------------------------------------
>
> Key: MNG-6596
> URL: https://issues.apache.org/jira/browse/MNG-6596
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.5.4, 3.6.0
> Environment: linux maven 3.5.4 and 3.6.0
> Reporter: Pieter van den Hombergh
> Priority: Major
>
> the parent pom is currently the way to go to set configurations for multiple projects, even if these projects are not siblings.
> Creating and deploying a parent pom to be shared in many projects should not force you to copy the parent pom around. Configurations should be dealt with in the same way: Don not repeat (as in copy and waste) yourselves.
> Making NO assumption OR ignoring the (default)) parentPath when the assumption does not match would solve this issue.
> The problem is even more annoying when maven reacts differently to using the same parent pom.
> The parent pom in question can be found on github under [statewalker sebipom|https://github.com/sebivenlo/statewalker]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)