Re: migrating Apache Resource Bundles from svn to Git

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: migrating Apache Resource Bundles from svn to Git

Robert Scholte-8
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 <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: migrating Apache Resource Bundles from svn to Git

Hervé BOUTEMY
> 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.

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

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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: migrating Apache Resource Bundles from svn to Git

Hervé BOUTEMY
In reply to this post by Robert Scholte-8
yes, Creadur could be a good home both for these bundles and the Apache parent
POM, to manage Apache project conventions for Maven separately from Maven code
itself
And if some of us want to continue work on it (given we produce plugins that
are to be updated in Apache parent POM), they could join Creadur
https://creadur.apache.org/

Regards,

Hervé

Le mercredi 24 juin 2020, 21:40:41 CEST Robert Scholte a écrit :

> I've been thinking about asking if project Creadur wants this code, since
> they also maintain the rat maven plugin. Looks quite related to me.
>
> Robert
>
> On 24-6-2020 00:00:09, Hervé BOUTEMY <[hidden email]> wrote:
> the little discussion now gave me an opinion:
> if nobody objects, I'll migrate the bundles to one unique Git repository:
> - name: maven-apache-resource-bundles.git
> - version will be 1.5-SNAPSHOT
> - containing 3
> org.apache.apache.resources:apache-(jar|jar-txt|incubator-disclaimer)-resou
> rce-bundle for maven-remote-resources-plugin and
> apache-source-release-assembly-descriptor for maven-assembly-plugin
>
> Regards,
>
> Hervé
>
> Le mardi 23 juin 2020, 00:11:41 CEST Hervé BOUTEMY a écrit :
> > 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 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: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]