Apache used to operate Gump for this purpose, back on the days of Ant and
Maven 1.x.
Hi all,
A while ago I encountered a bug [1] in Maven 4 which I'm testing at work. I
took quite some time into debugging the issue, but I am at a dead end
currently.
The issue should describe the problem enough, but in short I understand it
as the following:
1. Multi module project with two
This should be done as part of Mavens own build.
Don't rely on uploaded versions, there's always a gap where another job
could have uploaded a different version.
If things start to fail, it could be hard to reproduce it.
It should be the one that has been built and stashed, so you can unstash
hboutemy merged pull request #272:
URL: https://github.com/apache/maven-site/pull/272
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
hboutemy commented on pull request #272:
URL: https://github.com/apache/maven-site/pull/272#issuecomment-964163051
you're right
https://maven.apache.org/ref/3.8.3/maven-model/maven.html#class_scm
thank you
--
This is an automated message from the Apache Git Service.
To respond to
Hi,
Good idea.
One of the resolutions can be to use maven wrapper to configure the Maven
version to use, and use wrapper to build a project.
Such a solution can be easily used in any CI system.
Using a wrapper we simply download the latest build and deployed Maven
version from the repository,
Hi all,
In the last year, we've seen multiple situations where a change in
Maven core prevented Maven from building itself [1][2].
On the path to stabilising Maven towards Maven 4, I think this isn't
helping us. That's why I propose we introduce an additional GitHub
action. Let's call it
