migration done:
source: https://github.com/apache/maven-apache-resources
SNAPSHOT site
https://maven.apache.org/apache-resource-bundles-archives/apache-resource-bundles-LATEST/
once the 1.5 release will be done, we can replace the old page
https://maven.apache.org/apache-resource-bundles/
Le
Hi,
quick topic refresh - looks like the rat project was finally migrated to git
and there is some activity there
https://github.com/apache/creadur-rat/commits/master
Maybe it's a good time to move forward with the remaining svn repos and
parent-poms?
Sylwester
On 2020/06/25 06:57:18 "Robert
Karl helps everyone who has questions He will always answer any questions I ask
no matter how trivial Viel Gluck!
--
Sent from my Alcatel GO FLIP V
On Jun 25, 2020 2:57 AM, Robert Scholte wrote:
I don't mind joining as committer. I actually was surprised Karl Heinz is
already PMC.
I don't mind joining as committer. I actually was surprised Karl Heinz is
already PMC.
Robert
On 25-6-2020 08:37:55, Hervé BOUTEMY wrote:
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
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
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 wrote:
the little discussion now gave me an opinion:
if nobody objects, I'll migrate the bundles to one
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)-resource-bundle
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]
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
> 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
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,
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
12 matches
Mail list logo
