Hi all,
Wondering, wouldn't maven-release be a good next candidate for a Git
migration?
I'm currently working locally with the maven-release github mirror, but
just had to checkout svn trunk to have a look at MRELEASE-431's robert's
current proposal (yes, I could've also git svn'ed it).
Cheers
2014-02-20 23:13 GMT+01:00 Fred Cooke <[email protected]>:
> + <extension>
> + <groupId>org.apache.maven.wagon</groupId>
> + <artifactId>wagon-ssh-external</artifactId>
> + <version>${extension.version.wagon}</version>
> + </extension>
>
> It was SSH settings that were not being respected. Things like ports
and
> ssh hosts vs DNS lookups, etc.
>
> There were other issues with multi-module-parents vs ONLY-parents vs
> aggregator poms. MRELEASE-814
>
> https://jira.codehaus.org/browse/MRELEASE-812
> https://jira.codehaus.org/browse/MRELEASE-815
>
> Other issues were m-site-p in terms of variables and inheritance and
> uploads, which work OK for general generation.
>
> IIRC the results of these bugs was that I had a lot of unwanted
> duplication
> of config that I couldn't inherit because it got mal-processed.
Nothing
> worse, but duplication is evil and makes baby Jesus and other equally
> ordinary small children cry.
>
> Then there are things that are just generally broken and don't affect
git
> worse than other SCMs
>
> <!-- <scmCommentPrefix>Releasing
${project.artifactId}
> version ${project.version} </scmCommentPrefix> --> <!-- Space trimmed
and
> version snapshot, yuck. -->
>
> But I'm OT now.
>
> Fred.
>
> On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt <[email protected]>
wrote:
> > On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
> > I only release core and that works fine which begs the question:
do we
> >
> >> want to normalize our repository structure to simplify the tooling
> >> requirements. What exactly doesn't work? Trying to release a single
>
> thing
>
> >> out of a repository containing many things?
> >
> > A stock m-r-p config will break using the latest releases of git (
due
> > to
> > depending on an old version of the -scm- artefacts ) which I've
> > mentioned
> > before, and I believe there are commits awaiting release to resolve
> > this.
> >
> > m-r-p also _really_ likes to release from the root directory of a
> > repository, so doing independent releases from sub
directories/modules
> > is
> > difficult ( there is a setting which lets this work, but that's just
> > unpleasant ) - but due to git's tagging/branching being repository
wide
> > just releasing an individual module really is unpleasant.
> >
> > Basically, if modules have a constant release cadence/version
numbering
> > scheme, they can release together in a single repo, otherwise they
> > should
> > be separate. This however I don't see as a "problem with git
tooling in
> > maven" - just good practise.
> >
> > Mark
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor ! nbsp;!
