The Apache Maven team is pleased to announce the release of the Apache Maven
SCM, version 2.2.1.
https://maven.apache.org/scm/
Release Notes - Maven SCM - Version 2.2.1:
https://github.com/apache/maven-scm/releases/tag/v2.2.1
Enjoy,
-The Apache Maven team
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.14.1
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins-archives/maven-compiler-plugin-3.14.1/
You should specify the version in your
HI,
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin 3.12.0
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
Howdy,
The Apache Maven team is pleased to announce the release of the
Apache Maven Daemon version 1.0.3
This release provides binaries based on Maven 3.9.11
(From now on, Maven Daemon 1.x line will wrap Maven 3.x binaries,
while Maven Daemon 2.x will wrap Maven 4.x binaries. Previous releases
Since when did the tag format template change in Maven Release?
On 2025/09/14 11:25:25 Olivier Lamy wrote:
> The Apache Maven team is pleased to announce the release of the Apache
> Maven Shade Plugin, version 3.6.1
>
> This plugin provides the capability to package the artifact in a
On 2025/09/17 09:12:45 Claude Warren wrote:
> Greetings,
>
> The maven site plugin indicates that properties defined in the pom.xml
> should be available within the velocity engine as "${propertyName}". This
> works for most cases. However, I have found that pom proper
ne 14. 9. 2025 v 13:25 odesílatel Olivier Lamy napsal:
> The Apache Maven team is pleased to announce the release of the Apache
> Maven Shade Plugin, version 3.6.1
>
The plugin web site rendering is kinda broken. Notice the placeholders:
[image: image.png]
>
> This plug
Le mercredi 17 septembre 2025, 11:12:45 CEST Claude Warren a écrit :
> Greetings,
>
> The maven site plugin indicates that properties defined in the pom.xml
> should be available within the velocity engine as "${propertyName}". This
> works for most cases. Howev
Greetings,
The maven site plugin indicates that properties defined in the pom.xml
should be available within the velocity engine as "${propertyName}". This
works for most cases. However, I have found that pom properties with dots
(".") in the name do not work. Thus "$
+1
Requires some changes to https://maven.apache.org/doxia/doxia-tools/index.html
though.
Konrad
> On 10. Sep 2025, at 22:21, Slawomir Jaranowski wrote:
>
> Hi,
>
> Last release of Maven Doxia LinkCheck
>
> https://github.com/apache/maven-doxia-linkcheck
> https:
+1
On 2025/09/13 07:05:09 Slawomir Jaranowski wrote:
> +1
>
> On Wed, 10 Sept 2025 at 22:21, Slawomir Jaranowski
> wrote:
> >
> > Hi,
> >
> > Last release of Maven Doxia LinkCheck
> >
> > https://github.com/apache/maven-doxia-linkcheck
>
Hi,
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire, version 3.5.4
The Surefire Plugin is used during the test phase of the build
lifecycle to execute the unit tests of an application.
https://maven.apache.org/surefire/maven-surefire-plugin/index.html
You
The Apache Maven team is pleased to announce the release of the Apache
Maven Shade Plugin, version 3.6.1
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies.
https
gt; Hi,
>
> Last release of Maven Linkcheck Plugin
>
> https://github.com/apache/maven-linkcheck-plugin
> https://maven.apache.org/plugins/maven-linkcheck-plugin/
>
> was about 11 years ago ... Since the last release we only did maintenance task
> https://github.com/apache/maven-
+1
On Wed, 10 Sept 2025 at 22:21, Slawomir Jaranowski
wrote:
>
> Hi,
>
> Last release of Maven Doxia LinkCheck
>
> https://github.com/apache/maven-doxia-linkcheck
> https://maven.apache.org/doxia/doxia-tools/doxia-linkcheck/
>
> was about 15 years ago ... Since t
+1
On Thu, 11 Sept 2025 at 19:13, Slawomir Jaranowski
wrote:
>
> Hi,
>
> I don't see a release for this project
> https://github.com/apache/maven-doxia-book-renderer
>
>
> This project use modules from doxia, like doxia-module-itext,
> doxia-module-latex whic
+1
On 2025/09/10 20:02:09 Slawomir Jaranowski wrote:
> Hi,
>
> Last release of Maven Linkcheck Plugin
>
> https://github.com/apache/maven-linkcheck-plugin
> https://maven.apache.org/plugins/maven-linkcheck-plugin/
>
> was about 11 years ago ... Since the last release
On Fri, Sep 12, 2025 at 4:25 PM Michael Osipov wrote:
>
> Are you able to lift that plugin to Doxia 2.x
I've actually been hanging out on m-site-p 3.8.2 for a long time, because I
started seeing visual issues with Doxia above 1.9, so I'm probably not the
best one to ask.
to update it (but it
> took him 4 years!), but many plugins are still on the 1.x stack.
>
> Personally I find site feature overblown, overcomplicated and just too
> fragile. And ultimately, way too hard to keep it up to date.
> However, I do agree that Maven is a great source of
On 2025/09/11 00:19:39 Greg Chabala wrote:
> Non-binding -1
>
> I don't know what the threshold for 'widely used' should be for an optional
> reporting plugin. I see 200+ results in the search provided.
>
> I'm a user of it. In general, I think Maven
+1
On 2025/09/10 20:21:40 Slawomir Jaranowski wrote:
> Hi,
>
> Last release of Maven Doxia LinkCheck
>
> https://github.com/apache/maven-doxia-linkcheck
> https://maven.apache.org/doxia/doxia-tools/doxia-linkcheck/
>
> was about 15 years ago ... Since the last release
+1
Konrad
> On 11. Sep 2025, at 19:13, Slawomir Jaranowski wrote:
>
> Hi,
>
> I don't see a release for this project
> https://github.com/apache/maven-doxia-book-renderer
>
>
> This project use modules from doxia, like doxia-module-itext,
> doxia-
+1 (nb)
Am 11.09.2025 um 19:13 schrieb Slawomir Jaranowski:
Hi,
I don't see a release for this project
https://github.com/apache/maven-doxia-book-renderer
This project use modules from doxia, like doxia-module-itext,
doxia-module-latex which was removed from doxia
https://githu
+1
On Thu, Sep 11, 2025 at 7:14 PM Slawomir Jaranowski
wrote:
>
> Hi,
>
> I don't see a release for this project
> https://github.com/apache/maven-doxia-book-renderer
>
>
> This project use modules from doxia, like doxia-module-itext,
> doxia-module-la
+1
czw., 11 wrz 2025, 19:38 użytkownik Tamás Cservenák
napisał:
> +1
>
> On Thu, Sep 11, 2025 at 7:14 PM Slawomir Jaranowski
> wrote:
> >
> > Hi,
> >
> > I don't see a release for this project
> > https://github.com/apache/maven-doxia-boo
Hi,
I don't see a release for this project
https://github.com/apache/maven-doxia-book-renderer
This project use modules from doxia, like doxia-module-itext,
doxia-module-latex which was removed from doxia
https://github.com/apache/maven-doxia/pull/79
So we don't have a poss
site feature overblown, overcomplicated and just too
fragile. And ultimately, way too hard to keep it up to date.
However, I do agree that Maven is a great source of metadata (usable
on websites), and reports, but my personal pet peeve is that Maven
*should not render*. IMHO, it should produce
Howdy,
The Apache Maven team is pleased to announce the release of the Maven
Resolver 2.0.11:
The 1.x resolver lineage is in "bugfix only" maintenance mode.
Maven Resolver 1.x is used in Maven 3.x, while Resolver 2.x is used in
Maven 4.x.
Site:
https://maven.apache.org/resolver
Rel
Howdy,
The Apache Maven team is pleased to announce the release of the Apache
Maven Wrapper, version 3.3.4
The Apache Maven Wrapper is an easy way to ensure a user of your Maven
build has everything necessary to run your Maven build.
See https://maven.apache.org/tools/wrapper/ for instructions
+1
On Thu, 11 Sept 2025 at 06:22, Slawomir Jaranowski
wrote:
>
> Hi,
>
> Last release of Maven Doxia LinkCheck
>
> https://github.com/apache/maven-doxia-linkcheck
> https://maven.apache.org/doxia/doxia-tools/doxia-linkcheck/
>
> was about 15 years ago ... Since t
Non-binding -1
I don't know what the threshold for 'widely used' should be for an optional
reporting plugin. I see 200+ results in the search provided.
I'm a user of it. In general, I think Maven site generation is
underappreciated, underutilized, and not well advertised
Hi,
Last release of Maven Doxia LinkCheck
https://github.com/apache/maven-doxia-linkcheck
https://maven.apache.org/doxia/doxia-tools/doxia-linkcheck/
was about 15 years ago ... Since the last release we only did maintenance task
https://github.com/apache/maven-doxia-linkcheck/compare/doxia
Hi,
Last release of Maven Linkcheck Plugin
https://github.com/apache/maven-linkcheck-plugin
https://maven.apache.org/plugins/maven-linkcheck-plugin/
was about 11 years ago ... Since the last release we only did maintenance task
https://github.com/apache/maven-linkcheck-plugin/compare/maven
ot my builds running on several multi-module maven builds and all but
one end up with only a single target/*.buildinfo. My build process actually
looks in all the folders for the buildinfo files and logs wherever
it finds one. That buildinfo contains references to all the
submodule artifacts publi
output as it is
temporary data in target dir
Regards,
Hervé
On 2025/08/26 16:53:19 Lee Meador wrote:
> What I read about using maven-artifact-plugin (reproducible builds) says it
> will generate a single buildinfo file but I have one of my maven
> multimodule builds that generates 2.
>
&
Ping, Herve?
Thanks
T
On Tue, Aug 26, 2025 at 6:53 PM Lee Meador wrote:
>
> What I read about using maven-artifact-plugin (reproducible builds) says it
> will generate a single buildinfo file but I have one of my maven
> multimodule builds that generates 2.
>
> Does anyone
As a gap filler, here are 3 BOMs for Maven 3.9.11:
https://github.com/maveniverse/maven-boms/releases/tag/maven-3.9.11-01
Thanks
T
On Mon, Aug 25, 2025 at 10:46 PM Slawomir Jaranowski
wrote:
>
> Should we add a scope provided for artifacts exported by Maven?
>
> On Sat, 23 Aug 2
The Apache Maven team is pleased to announce the release of the Apache
Maven Wrapper, version 3.3.3
The Apache Maven Wrapper is an easy way to ensure a user of your Maven
build has everything necessary to run your Maven build.
See https://maven.apache.org/tools/wrapper/ for instructions on how
What I read about using maven-artifact-plugin (reproducible builds) says it
will generate a single buildinfo file but I have one of my maven
multimodule builds that generates 2.
Does anyone know why there is more than one buildinfo file.
The logs look like this showing "Saved aggregate in
Should we add a scope provided for artifacts exported by Maven?
On Sat, 23 Aug 2025 at 18:54, Tamás Cservenák wrote:
>
> Howdy,
>
> so for quick turnaround, I did this:
> https://github.com/maveniverse/maven-boms
>
> This project uses Nisse + BOM builder and publishes 3 B
Howdy,
so for quick turnaround, I did this:
https://github.com/maveniverse/maven-boms
This project uses Nisse + BOM builder and publishes 3 BOMs for given
Maven version:
* "fat" that is "full stack"
* "skinny" that is "reactor only"
* "plugin" t
Looks like something that we should apply also to our 3.x branches for
Maven projects
Sylwester
sob., 23 sie 2025, 14:49 użytkownik Tamás Cservenák
napisał:
> Just for reference, here is a PR fixing the issue by setting up proper
> dependabot rules as well:
> https://github.co
Just for reference, here is a PR fixing the issue by setting up proper
dependabot rules as well:
https://github.com/ascopes/protobuf-maven-plugin/pull/773
T
On Sat, Aug 23, 2025 at 11:56 AM Tamás Cservenák wrote:
>
> Howdy,
>
> We have a thread about this on Slack, but let me ju
Howdy,
We have a thread about this on Slack, but let me just reiterate some
things brought up there...
Here is what we could do, from "least helpful" to "most helpful" (for user PoV):
1. clearly document these, like "Maven 3 uses Resolver 1, and Maven 4
uses Resol
We can add check for it in Maven validation -
https://maven.apache.org/guides/plugins/validation/
and also in plugin-tools ...
On Fri, 22 Aug 2025 at 20:03, Tamás Cservenák wrote:
>
> Howdy,
>
> I was just checking downstream dependencies of Resolver 2.x and was
> first surpri
checking downstream dependencies of Resolver 2.x and was
> > first surprised how many of them are:
> >
> >
> https://deps.dev/maven/org.apache.maven.resolver%3Amaven-resolver-api/2.0.10/dependents
> >
> > By inspecting, I discovered that MANY are in fact Maven 3
ervenák a écrit :
> Howdy,
>
> I was just checking downstream dependencies of Resolver 2.x and was
> first surprised how many of them are:
>
> https://deps.dev/maven/org.apache.maven.resolver%3Amaven-resolver-api/2.0.10/dependents
>
> By inspecting, I discovered tha
Howdy,
I was just checking downstream dependencies of Resolver 2.x and was
first surprised how many of them are:
https://deps.dev/maven/org.apache.maven.resolver%3Amaven-resolver-api/2.0.10/dependents
By inspecting, I discovered that MANY are in fact Maven 3 plugins (!),
building against some
The Apache Maven team is pleased to announce the release of the Apache
Maven Artifact Resolver Ant Tasks, version 1.6.0
The Maven Artifact Resolver Ant Tasks enable build scripts for Apache
Ant 1.7+ to use Maven Artifact Resolver combined with Apache Maven
Artifact Resolver Provider to resolve
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.11.3
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project..
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
t more once I am back home.
>
> Thanks
> T
>
> On Thu, Aug 14, 2025 at 1:16 PM Nils Breunese wrote:
> >
> > Tamás, do you know who could perform this Maven Wrapper release?
> >
> > Nils.
> >
> > On 2025/07/25 18:18:37 Tamás Cservenák wrote:
> >
n is created by GenericVersionScheme exclusively.
- is not, in fact, it is reusable, see for example here
https://github.com/maveniverse/toolbox/blob/6442611992f83a85de5235616c38c05cb180ec8e/shared/src/main/java/eu/maveniverse/maven/toolbox/shared/ToolboxCommando.java#L411
And a general note: ev
We have some code that uses the ArtifactVersion interface and
DefaultArtifactVersion implementation from maven-artifact 3.9.11. Reading this
thread makes me think I should be looking into migrating away from this
dependency.
I just took a look at maven-resolver-util to see if I could migrate
could perform this Maven Wrapper release?
>
> Nils.
>
> On 2025/07/25 18:18:37 Tamás Cservenák wrote:
> > +1 for doing it
> >
> > On Fri, Jul 25, 2025, 15:54 Nils Breunese wrote:
> >
> > > Hello,
> > >
> > > Today I ran into an issue w
Tamás, do you know who could perform this Maven Wrapper release?
Nils.
On 2025/07/25 18:18:37 Tamás Cservenák wrote:
> +1 for doing it
>
> On Fri, Jul 25, 2025, 15:54 Nils Breunese wrote:
>
> > Hello,
> >
> > Today I ran into an issue with Maven wrapper’s dis
Just a heads up: maven-artifact is dead (legacy); the exact reason why
it is stopped being supported is that since 2010 there is duplicate
(and superior) implementation for versions in Resolver. Also note that
maven-artifact is deprecated in Maven 4.
That said, the "effort worth" impl
s like "-1" (hyphen as initial token); if these are
clarified I can take a stab at some PRs for both the spec and
maven-artifact code to close this out.
Trimming "---1"
Trimming and tokenization are substantial sections of the version spec and
factor into the version compa
I created an bug issue in the repository, thanks for helping :)
https://github.com/apache/maven-build-cache-extension/issues/369
On 2025/08/08 14:24:38 "Steffens, Tammo - ENCOWAY" wrote:
> Hi, I am currently trying to use the maven build cache extension. I wanted to
> ask if the
ound a workaround. You could create an issue
> (https://github.com/apache/maven-build-cache-extension/issues) for either
> supporting including files in hidden directories or documenting this
> limitation.
>
> Nils.
>
> > Op 11 aug 2025 om 12:05 heeft Steffens, Tammo - ENCOWAY
Nice to hear that you found a workaround. You could create an issue
(https://github.com/apache/maven-build-cache-extension/issues) for either
supporting including files in hidden directories or documenting this limitation.
Nils.
> Op 11 aug 2025 om 12:05 heeft Steffens, Tammo - ENCOWAY
>
after I looked at the source code, it appears because the
> default location of the configuration is placed inside an hidden directory, I
> can't add it as an input.
>
> For reference (Tag 1.2.0)
> org/apache/maven/buildcache/checksum/MavenProjectInput.java:480
>
Hi Nils,
I did try, but after I looked at the source code, it appears because the
default location of the configuration is placed inside an hidden directory, I
can't add it as an input.
For reference (Tag 1.2.0)
org/apache/maven/buildcache/checksum/MavenProjectInput.java:480
So this see
Hi
The Apache Maven team is pleased to announce the release of the Apache
Maven Archiver 3.6.4 and 4.0.0-beta-4.
The Maven Archiver is mainly used by plugins to handle packaging:
https://maven.apache.org/shared/maven-archiver/
Release notes available:
3.6.4:
https://github.com/apache/maven
> So to recap, had three questions:
>
> 1) should versions be treated as if there's an implicit separator?
> 2) how should trimming/tokenization work for "--1--" and "--1-"?
> 3) how should trimming/tokenization work for "abc" and "-abc"?
Trimming and tokenization are implementation details and a
Roughly, https://maven.apache.org/pom.html#Version_Order_Specification
is normative.
If Maven itself is doing something contrary to that spec, we need to
take a look. It's possible that the spec is wrong in some edge cases,
but more likely the code is wrong.
If there are edge cases the
My only thought after reading this, is that these would make good unit
tests inside the project, so that the answers would become explicitly
defined.
On Tue, Aug 5, 2025 at 12:21 PM Ron Desmond
wrote:
> Hi,
>
> I'm ironing out my understanding of the Maven Version Order
Steffens, Tammo - ENCOWAY wrote:
> Hi, I am currently trying to use the maven build cache extension. I wanted
> to ask if there is any way to include the extension config itself as part of
> the hash for every module. Because when I change the configuration, I want to
> in
Hi, I am currently trying to use the maven build cache extension. I wanted to
ask if there is any way to include the extension config itself as part of the
hash for every module. Because when I change the configuration, I want to
invalidate old artifacts from the cache. Is there any known way
Hi,
I'm ironing out my understanding of the Maven Version Order Spec
<https://maven.apache.org/pom.html#Version_Order_Specification> and had
three questions: one was related to an implicit separator before the
beginning of versions, and the next two were related
+1 for doing it
On Fri, Jul 25, 2025, 15:54 Nils Breunese wrote:
> Hello,
>
> Today I ran into an issue with Maven wrapper’s distributionSha256Sum
> feature, which turned out to be
> https://github.com/apache/maven-wrapper/issues/297 and a fix was already
> merged for it in
Hello,
Today I ran into an issue with Maven wrapper’s distributionSha256Sum feature,
which turned out to be https://github.com/apache/maven-wrapper/issues/297 and a
fix was already merged for it in December last year, but there hasn't been a
Maven Wrapper release since 2024-05-21.
Looki
rry over local repo"
> > 2nd and other jobs: work a top of prepopulated and installed from 1st
> > job artifacts, running IT-like tests against them.
>
> Timothy Stone wrote:
> > Take a look at the To Be Continuous Maven Pipeline templates.
> > https://gitlab.co
Hi,
Last time we released a 3.8.9 Maven version,
as we announced in releases [1] it will be the latest version for the
3.8.x line.
I have prepared a documentation update [2] which removes 3.8.x from
the download page [3]
Additionally version 3.8.9 will be also removed from distribution space [4
The Apache Maven team is pleased to announce the release of the Apache
Maven 3.9.11
Apache Maven is a software project management and comprehension tool. Based
on the concept of a project object model (POM), Maven can manage a
project's build, reporting and documentation from a central pie
The Apache Maven team is pleased to announce the release of the Apache
Maven Enforcer Plugin, version 3.6.1
The Enforcer plugin provides goals to control certain environmental constraints
such as Maven version, JDK version, and OS family
along with many more built-in rules and user created rules
On 7/2/25 09:39, Slawomir Jaranowski wrote:
The Apache Maven team is pleased to announce the release of the Apache
Maven Enforcer Plugin, version 3.6.0
The Enforcer plugin provides goals to control certain environmental constraints
such as Maven version, JDK version, and OS family
along with
The Apache Maven team is pleased to announce the release of the Apache
Maven Enforcer Plugin, version 3.6.0
The Enforcer plugin provides goals to control certain environmental constraints
such as Maven version, JDK version, and OS family
along with many more built-in rules and user created rules
The Apache Maven team is pleased to announce the release of the Apache
Maven GPG Plugin, version 3.2.8
This plugin signs all of the project's attached artifacts with GnuPG.
https://maven.apache.org/plugins/maven-gpg-plugin/
You should specify the version in your project's plugin con
tone wrote:
> Take a look at the To Be Continuous Maven Pipeline templates.
> https://gitlab.com/to-be-continuous/maven
Many thanks for your kind replies and ideas/feedback which have indeed been
very helpful for my understanding of the inner workings of the GitLab Runner
stages and
is here:
> https://github.com/maveniverse/mima/tree/main/demo/library-maven-plugin
>
> And library is NOT part of the "main build" (the demo directory at top
> level is not part of build).
>
> Basically what happens:
> 1st job, top leve: mvn install (again demo is not part of u
Library is here:
https://github.com/maveniverse/mima/tree/main/demo/library-maven-plugin
And library is NOT part of the "main build" (the demo directory at top
level is not part of build).
Basically what happens:
1st job, top leve: mvn install (again demo is not part of upper leve
Tamás Cservenák wrote:
> Does not have to, for example I usually do something like this:
> https://maveniverse.eu/blog/2024/09/07/very-simple-ci-setup/
>
> True, this "carry over" idea works IF you are good with
> (built/installed) artifacts, as basically all I do is carry local repo
> from one
Hi Hantsy,
The mavenup is an Upgrade-Tool to upgrade projects from Maven 3 to Maven 4
(with either Maven 3 compatibility mode or including Maven 4 only features).
So it‘s no plugin to use in a regular build, but a tool helping people to
migrate.
Sadly I did not find time to write a guide for
I have just tried Maven 4.0, and found that there are several commands
provided in the mvn dist, but I am sure the purpose of Maven.
When I used Arquillian and Maven 4 in projects, I encountered some warnings
in the Arquillian archives for Maven POMs when running Arquillian tests.
However, when I
The Apache Maven team is pleased to announce the release of the Maven
Resolver 2.0.10:
The 1.x resolver lineage is in "bugfix only" maintenance mode.
Maven Resolver 1.x is used in Maven 3.x, while Resolver 2.x is used in
Maven 4.x.
Site:
https://maven.apache.org/resolver
Release Not
The Apache Maven team is pleased to announce the release of the Maven
Resolver 1.9.24
The 1.x resolver lineage is in "bugfix only" maintenance mode.
Maven Resolver 1.x is used in Maven 3.x, while Resolver 2.x is used in
Maven 4.x.
Site:
https://maven.apache.org/resolver-archives/resol
Hi,
* This is reproducible with Maven 4 RC 4 as well.
* I created https://github.com/mojohaus/extra-enforcer-rules/issues/327 and
bisected the maven-core.
* extra-enforcer-rules ITs started to „break“ as of
https://github.com/apache/maven/commit/3ba8f2d which introduced a lot of
changes how
The Apache Maven team is pleased to announce the release of the Apache
Maven Invoker Plugin, version 3.9.1
This plugin is particularly handy to perform integration tests for
other Maven plugins.
The Invoker Plugin can be employed to run a set of test projects that
have been designed to assert
On 6/26/25 09:01, Andreas A Loew -Extern wrote:
Hello Maven experts,
having started to make a big legacy enterprise Java project (which
previously used Jenkins) ready to build through GitLab CI/CD, I ran into
the exact same problems as described here with regards to an obvious
misfit between
s marked
> with an attribute
>
> T
>
> On Thu, Jun 26, 2025 at 8:12 PM Arnaud Héritier
> wrote:
> >
> > It's strange I have the same issue if I download the tar.gz, even if I
> > extract it outside of Downloads folder
> > But the version I get fr
But the version I get from maven-wrapper is ok
>
>
> Arnaud Héritier
> GitHub/ASF/... : aheritier
>
>
> On Thu, Jun 26, 2025 at 12:37 PM Mark Derricutt wrote:
>
> > On 26 Jun 2025 at 9:05:12 PM, Guillaume Nodet wrote:
> >
> > > The Apache Maven team is
It's strange I have the same issue if I download the tar.gz, even if I
extract it outside of Downloads folder
But the version I get from maven-wrapper is ok
Arnaud Héritier
GitHub/ASF/... : aheritier
On Thu, Jun 26, 2025 at 12:37 PM Mark Derricutt wrote:
> On 26 Jun 2025 at 9:
xample, IT matrix runs like this, as explained.
Thanks
T
On Thu, Jun 26, 2025 at 5:02 PM Andreas A Loew -Extern
wrote:
>
> Nils Breunese wrote:
>
> > Would it be an option to just do everything (build, test, code quality,
> > etc.) in a single Maven execution in a single GitLab
Nils Breunese wrote:
> Would it be an option to just do everything (build, test, code quality, etc.)
> in a single Maven execution in a single GitLab job? That way you wouldn’t
> need to pass any artifacts between multiple jobs.
That's also the most simple I was thinking about
Sorry for the confusion, but I was referring to ‘job artifacts’ in the context
of GitLab (https://docs.gitlab.com/ci/jobs/job_artifacts/), not Maven artifacts.
Nils.
> Op 26 jun 2025, om 16:09 heeft Tamás Cservenák het
> volgende geschreven:
>
> The problem is that "That
I was thinking if maven-buildcache-extension could help you, but as the
goal is taken into account in the cache, I'm not sure.
Am 26.06.2025 um 15:06 schrieb Andreas A Loew -Extern:
Hello Maven experts,
having started to make a big legacy enterprise Java project (which previously
do everything (build, test, code quality, etc.)
> in a single Maven execution in a single GitLab job? That way you wouldn’t
> need to pass any artifacts between multiple jobs.
>
> Nils.
>
> > Op 26 jun 2025, om 15:06 heeft Andreas A Loew -Extern
> > het volgende ge
Would it be an option to just do everything (build, test, code quality, etc.)
in a single Maven execution in a single GitLab job? That way you wouldn’t need
to pass any artifacts between multiple jobs.
Nils.
> Op 26 jun 2025, om 15:06 heeft Andreas A Loew -Extern
> het volgende gesc
Hello Maven experts,
having started to make a big legacy enterprise Java project (which previously
used Jenkins) ready to build through GitLab CI/CD, I ran into the exact same
problems as described here with regards to an obvious misfit between the
concepts of GitLab Runner CI/CD and Maven
Hello Maven experts,
having started to make a big legacy enterprise Java project (which previously
used Jenkins) ready to build through GitLab CI/CD, I ran into the exact same
problems as described here with regards to an obvious misfit between the
concepts of GitLab Runner CI/CD and Maven
1 - 100 of 38261 matches
Mail list logo
