it seems there is a misunderstanding: it's not 4 parent POMs it's resource bundles, that are used with maven-assembly-plugin or maven- remote-resources-plugin in Apache parent POM [1]
see https://maven.apache.org/apache-resource-bundles/index.html for some description Regards, Hervé [1] https://github.com/apache/maven-apache-parent/blob/master/pom.xml Le lundi 22 juin 2020, 20:31:16 CEST Robert Scholte a écrit : > On 22-6-2020 00:25:39, Hervé BOUTEMY <[email protected]> wrote: > > I agree: independent release cycles means independent repositories. > > in the past, we had 4 independent Maven parent POMs [1] under one unique svn > trunk, with 4 separate release cycles, many votes/hard maintenance (having > a new parent POM release for plugins, for example) and hard to use (version > of parent for plugins was not the same as shared parent, or pure maven > parent). When switching to Git, we switched to one Git repository and one > unique release cycle: a vote for a release remains not so easy (because > getting votes is not easy), but at least there is only one for every parent > POM. Robert Scholte: I think there's a small difference, these poms all > inherit from the apache-parent. If there's a new parent, it makes sense to > release them all at once. > > > > We have the same initial situation with resource bundles: the independence > of the release cycles inside the unique trunk are not written in stone, we > can simplify and hope that it will ease maintenance in addition to ease > migration. Or we can make efforts to split: for plugins or shared > components, splitting was the only reasonable option. > > > I wonder if they should be part of the Maven group, looks more like a they > > are maintained by us by coincidence. Is there some ASF resources group to > > maintain this (or worth introducing)? > > exactly like the ASF parent POM > If you find someone who want to maintain, don't hesitate > Robert Scholte: > Let me see if I can get them out of the Maven project. > I don't mind maintaining these parents, but I'd prefer have a clear > separation on which parts are clearly Maven and which actually ASF > > thanks, > Robert > > > > Regards, > > Hervé > > [1] https://maven.apache.org/pom/index.html > > Le dimanche 21 juin 2020, 21:36:37 CEST Robert Scholte a écrit : > > I agree: independent release cycles means independent repositories. > > I wonder if they should be part of the Maven group, looks more like a they > > are maintained by us by coincidence. Is there some ASF resources group to > > maintain this (or worth introducing)? > > > > thanks, > > Robert > > > > On 21-6-2020 19:14:47, Michael Osipov wrote: > > > > Am 2020-06-20 um 00:31 schrieb Hervé BOUTEMY: > > > one of the last part not yet done, because there is a choice to do: > > > - migrate to one multi-module Git repository? > > > - or split each bundle into a separate Git repo? > > > > These two question can be answered when we know whether these modules > > are loosely coupled of strongly interrelated like our POM parents. > > If the former, separate repos, if the latter one repo. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
