maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fred Cooke <>
Subject Re: Convert everything to Git
Date Thu, 20 Feb 2014 22:13:26 GMT
+            <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

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.


On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt <> 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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message