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
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
> I think the reason someone might want their projects all in the same
> directory is because Eclipse has issues with nested project
> structures.
I see how that can be a pain in the ***. I was unaware of this problem,
being an IntelliJ IDEA user.
--
Alexander Kriegisch
https://scrum-master.de
Hopefully our conversation will benefit others who've experienced the same
issue, so thank you for showing that it works in some cases. I think the
reason someone might want their projects all in the same directory is
because Eclipse has issues with nested project structures.
@Lasse, the
> It seems the goal assumes that child modules sit in nested
> directories.
Well, that might be the case. I have never tested any other scenario
because this is how I organise my Maven projects. Neither am I a Maven
expert nor did I claim that my solution works for everybody in every
case. I just
Am 2021-02-05 um 18:52 schrieb Andres Almiray:
@Tamás: Right, should had explained the use case. I want to deploy all
artifacts to a local directory so that I can inspect everything which will
be deployed given certain conditions.
I managed to do that by forcing a stable, absolute directory as
It seems the goal assumes that child modules sit in nested directories.
Unzip and run mvn validate in the root directory, and you'll see the root
location for project sarek is incorrect.
Delany
On Sat, 6 Feb 2021 at 14:28, Alexander Kriegisch
wrote:
> Maybe I misunderstand you, but for me this
Maybe I misunderstand you, but for me this works nicely in a module which has a
parent of type POM which has the root (also of type POM) as parent. I.e. the
root POM is the grandparent. I have no issues, as long as the property is
declared in the root as shown in the project I linked to.
--
This only works if the parent is the root. If you extend to a third level
of pom, it will report the rootlocation as the project directory.
Delany
On Sat, 6 Feb 2021 at 04:22, Alexander Kriegisch
wrote:
> I had some discussion with Karl Heinz Marbaise about
> maven.multiModuleProjectDirectory a
I had some discussion with Karl Heinz Marbaise about
maven.multiModuleProjectDirectory a while ago (cannot remember where
exactly) and he strongly advised me not to use it as it is for internal
use only. Even so, other tools such as IntelliJ IDEA use it internally,
but not consequently, the
For me, no problem on Jenkins either (using "withMaven" pipeline step).
There used to be this issue: https://issues.jenkins.io/browse/JENKINS-35335
Which turned out to be a Maven bug which was fixed in 3.5.0:
https://issues.apache.org/jira/browse/MNG-5889
As far as MNG-5830 is concerned, I don't
Maybe for you Falko, but not my Jenkins server with Maven 3.6.3, or these
other users
https://issues.apache.org/jira/plugins/servlet/mobile#issue/MNG-5830
Delany
On Fri, 5 Feb 2021, 22:25 Falko Modler, wrote:
> I've been using maven.multiModuleProjectDirectory in various projects
> (and have
I've been using maven.multiModuleProjectDirectory in various projects
(and have also seen it in others).
You'll need a .mvn directory in your root directory to make it work.
PS: I know that there has been some controvery about this property but
well, it works! ;-)
Cheers,
Falko
Am 05.02.2021
Unsure will it help, but your description reminded me of nexus-staging
plugin, there we similarly "deploy locally" (defer actual deploy) to fire
the deployables at the project end:
@Tamás: Right, should had explained the use case. I want to deploy all
artifacts to a local directory so that I can inspect everything which will
be deployed given certain conditions.
I managed to do that by forcing a stable, absolute directory as shown at
Using directory-maven-plugin and highest-basedir goal from it has worked
just fine for me.
https://github.com/jdcasey/directory-maven-plugin#highest-basedir-goal
pe 5. helmik. 2021 klo 18.53 Tamás Cservenák (ta...@cservenak.net)
kirjoitti:
> Howdy,
> Grab somehow (you did not state from where if
Howdy,
Grab somehow (you did not state from where if "outside of plugins")
MavenSession, it has getExecutionRootDirectory method, BUT it may not be
what you want, as one may use -f param for example...
So, I'd shoot back: WHY do you need the root of a multi module build and
FROM WHAT you need it?
18 matches
Mail list logo
