You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2015/11/29 16:29:10 UTC
[jira] [Resolved] (MPOM-95) release all Maven parent POMs in one
step and with same consistent version
[ https://issues.apache.org/jira/browse/MPOM-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy resolved MPOM-95.
-------------------------------
Resolution: Fixed
Assignee: Hervé Boutemy
seems ready: now we need to do a release and see if something unexpected happens
> release all Maven parent POMs in one step and with same consistent version
> --------------------------------------------------------------------------
>
> Key: MPOM-95
> URL: https://issues.apache.org/jira/browse/MPOM-95
> Project: Maven POMs
> Issue Type: Task
> Components: maven, maven-archeypes, maven-plugins, maven-shared-components, maven-skins
> Affects Versions: MAVEN-SKINS-10, MAVEN-SHARED-22, MAVEN-PLUGINS-28, MAVEN-27
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Fix For: MAVEN-30
>
>
> as discussed on maven-dev mailing list, releasing each pom separately, with its dedicated vote, is just a waste of time: doing only one release with everything inside it will be a lot more efficient
> And with every parent pom having its own version different from others, even using them is hard: having every parent pom at the same version, starting with version 30, will make their use a lot easier
> see http://mail-archives.apache.org/mod_mbox/maven-dev/201511.mbox/%3C2524303.3Sa8sxfxFZ%40herve-desktop%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)