Interesting. Given that Maven 4 will include the wrapper; wrapper files are
kept at $ROOT/.mvn; running a wrapper from a child project requires that
$ROOt/.mvn be known (from the outside even). Thus the value of the top most
basedir can be guaranteed.
Of course this works only if there is a
Following on a bit, I logged this ticket
https://github.com/pascalgn/properties-maven-extension/issues/58
so the property *git.dir.worktree* is available before the reactor starts.
But now I've found a situation that even an extension can't help with:
Suppose I want to utilise an alternative
Hi,
Can someone explain the tag found in plugins?
https://maven.apache.org/guides/mini/guide-using-extensions.html
It seems like instead of being a plugin that provides lifecycle
enhancements using this tag, a lot of plugins should rather be extensions,
that can optionally accept configuration
Thanks, exactly what I was looking for.
-Original Message-
From: Thomas Broyer
Sent: donderdag 18 februari 2021 11:44
To: jean-pierre.urk...@devoteam.com.invalid
Cc: Maven Users List
Subject: Re: maven-assembly-plugin v3.3.0 - how to modify generated
MANIFEST.MF
Use the 'archive'
Hi all,
I am trying to generate a ‘jar’ assembly that contains a ‘Main-Class’ in
the META-INF/MANIFEST.MF. Now it looks like the assembly plugin is
generating its own (plexus archiver) MANIFEST file with contents:
Manifest-Version: 1.0
Created-By: Plexus Archiver 4.2.1
My
Use the 'archive' property of the assembly plugin itself (not in the
assembly descriptor):
http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#archive
Le jeu. 18 févr. 2021 à 11:23, Jean-Pierre Urkens
a écrit :
> Hi all,
>
>
>
> I am trying to generate a ‘jar’ assembly that
I wrote a doc for deploying to local staging directory [1] in Maven Deploy
Plugin documentation (not yet released)
perhaps this can be of use
Regards,
Hervé
[1]
https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/examples/deploy-network-issues.html
Le vendredi 5 février
