I love the idea of bringing some great tools to ASF: happy of this discussion
each one will require a separate in-depth evaluation of what it would mean to
have some part available as default in Maven CLI distribution vs what would
remain as a plugin or stil remain an extension
I personally stu
wow, it feels strange to have that discussion in 2025 after 20 years of
practice :)
it's what we promote through Modello for years
https://codehaus-plexus.github.io/modello/modello.html
and what we do for each and every descriptor we write
changing the practice for POM = the most sensitive pla
t; > > "natively"?
> > > > > I would be willing to implement it if you think it's a good idea.
> > > > >
> > > > > Regards
> > > > > Per
> > > > >
> > > > > On Tue, 22 Jul 2025 at 10:39, Jon Harper
&
deep dive done, with personal evaluation
https://github.com/apache/maven-studies/tree/deploy
happy to discuss and complete the review
Le jeudi 17 juillet 2025, 03:53:40 CEST Hervé Boutemy a écrit :
> I finally stopped procrastinating and took time to test
>
> https://github.com/apa
Hervé Boutemy a écrit :
> it seems we're back to Maven history of:
> 1. publication to simple file systems (eventually shared)
> 2. multi-module (aka. multi-subproject) publication
> 3. multi-file publication in a single gav
>
> On the positive side, this has been very f
+1
Reproducible Build ok: reference build done with JDK 21 on *nix
Regards,
Hervé
Le samedi 12 juillet 2025, 20:58:23 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 14 issues:
> https://github.com/apache/maven/issues?q=milestone%3A3.9.11
>
> Changes since the last release:
> https://g
+1
Reproducible Build ok: reference build done with JDK 21 on *nix
Regards,
Hervé
Le samedi 12 juillet 2025, 19:29:40 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 11 issues:
> https://github.com/apache/maven-enforcer/issues?q=milestone%3A3.6.1
>
> Changes since the last release:
> h
it seems we're back to Maven history of:
1. publication to simple file systems (eventually shared)
2. multi-module (aka. multi-subproject) publication
3. multi-file publication in a single gav
On the positive side, this has been very flexible and perfect for downloads.
But on the negative side, th
+1
Reproducible Build ok: reference build done with JDK 21 on *nix
Regards,
Hervé
Le samedi 21 juin 2025, 20:59:54 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 41 issues:
> https://github.com/apache/maven-pmd-plugin/issues?q=is%3Aclosed%20milestone%
> 3A%223.27.0%22
>
> Changes sinc
+1
Reproducible Build checked ok: reference build done with JDK 24 on *nix and
Maven 4.0.0-rc-3
for future release, using a LTS JDK may be a better idea than JDK 24
And decide if we use a rc Maven for building or latest 3.9.x
created a documentation issue https://github.com/apache/maven/issues/
+1
Reproducible Build checked ok: reference build done with JDK 21 on *nix
Regards,
Hervé
Le lundi 16 juin 2025, 23:04:00 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 47 issues:
> https://github.com/apache/maven-ear-plugin/issues?q=is%3Aclosed%20milestone%
> 3A%223.4.0%22
>
> Change
+1
Reproducible Build checked ok: reference build done on *nix (tested with JDK 17
and 21: no impact, as expected... :) )
Regards,
Hervé
On 2025/06/14 08:32:27 Slawomir Jaranowski wrote:
> Hi,
>
> We solved 14 issues:
> https://github.com/apache/maven-parent/milestone/25?closed=1
>
> There a
+1
Reproducible Build checked ok: reference build done with JDK 8 on Windows
Regards,
Hervé
On 2025/06/14 22:10:24 Michael Osipov wrote:
> Hi,
>
> NOTE: Expect this to be the *last* release on the 3.8.x line to close
> off the branch.
>
> We solved 6 issues:
> https://issues.apache.org/jira/
wow, great achievement!
this will ease interactions with our community
This is great to be able to continue to modernize infrastructure of a
venerable and vast project like Maven and keep it up to date with evolution of
practice (who remembers that Maven started with CVS? we did not even keep
Hi,
The Project Management Committee (PMC) for Apache Maven
has invited Sandra Parsick to become a committer
and we are pleased to announce that they have accepted.
Please join us in welcoming Sandra to their new role
and responsibility in our project community.
--
Hervé
On behalf of the Maven
+1
Reproducible Build ok: reference build done with JDK 21 on *nix
Regards,
Hervé
Le vendredi 30 mai 2025, 22:11:53 CEST Tamás Cservenák a écrit :
> Howdy,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&ve
> rsion=12355102
>
> There are st
+1
Reproducible Build checked ok: reference build done with JDK 21 on *nix
Regards,
Hervé
Le mercredi 28 mai 2025, 00:20:52 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 6 issues:
> https://github.com/apache/maven-clean-plugin/milestone/5?closed=1
>
> There are still a couple of issu
I think we need to clarify that
1. Maven 3 plugins should work with Maven 4 (eventually require a recent
update that fixes small compatibility issues),
2. and this is still the main expected way to use plugins with Maven 4
Maven 4 - specific plugins, using the still experimental Maven 4 API, is s
Le jeudi 22 mai 2025, 17:30:20 CEST Matthias Bünger a écrit :
> Am 22.05.2025 um 09:23 schrieb Hervé Boutemy:
> > yes to try to make sure Maven 4.0.0 will run smoothly on Java 24
> >
> > on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a
> > strong
yes to try to make sure Maven 4.0.0 will run smoothly on Java 24
on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a strong
reason for coupling these 2 huge beasts?
longer analysis:
Jira to GH Issues migration has started everywhere (66 as of now, if tracking
is accurate [
Le jeudi 22 mai 2025, 08:49:20 CEST Mark Derricutt a écrit :
> On 22 May 2025 at 6:19:26 PM, Hervé Boutemy wrote:
> > I don't get what plugin updates are expected: are there Maven 3 plugins
> > known
> > to fail on Maven 4? If yes, are they so many?
>
> That I
+1 we need a release before adding new changes
> world as well - or more than likely, a raft of third-party plugin updates.
I don't get what plugin updates are expected: are there Maven 3 plugins known
to fail on Maven 4? If yes, are they so many?
I hope releasing Maven 4 will help clarify
which
FTR Jira issues
https://issues.apache.org/jira/browse/MNG-7906
https://issues.apache.org/jira/browse/MNG-7854
https://issues.apache.org/jira/browse/MPH-183
and all linked issues
I don't know how this is relates with bom packaging in Maven 4
https://maven.apache.org/guides/introduction/introductio
07:55:41 CET Hervé Boutemy a écrit :
> I tried to clarify the 4.0 Milestones series in the version history, that
> were upgraded to 3.20.0 (yes, wrong from a mathematical perspective, but
> right from the intent) as they were targetting Doxia 2 (before we have the
> "plugin 4
I tried to clarify the 4.0 Milestones series in the version history, that were
upgraded to
3.20.0 (yes, wrong from a mathematical perspective, but right from the intent)
as they
were targetting Doxia 2 (before we have the "plugin 4.x = Maven 4 prerequisite"
convention)
https://maven.apache.o
if we go from svn-oriented old conventions to benefit from more modern Git
ones, I'd like that we investigate Git tag best practices like RC tag during
votes and protected tag on final release
Regards,
Hervé
Le samedi 8 mars 2025, 08:01:34 CET Slawomir Jaranowski a écrit :
> Hi,
>
> We use in
I see the interest of improving maintainability of build POM beyond what has
already been
achieved with inference (did I say I loved your presentation [4] and this term?)
But as already expressed, I fear the risk of confusion and time taken...
Your approach of not just discussing but providing
+1
Reproducible Builds ok: reference build done with JDK 21 on Windows
Regards,
Hervé
Le mardi 4 mars 2025, 19:23:46 CET Matthias Bünger a écrit :
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317620&ve
> rsion=12355704&styleName=Text
>
+1
Regards,
Hervé
Le samedi 22 février 2025, 09:43:42 CET Matthias Bünger a écrit :
> Good morning everybody,
> ten days ago I started a discussion about the Maven PDF plugin, asking
> who is using it, if people have switched over to other tools and what
> everybody is thinking about archiving t
or just keep the policy as we have, as it has been wisely worded: once 4 will
be GA, 3.8 will de-facto be EOL'ed as per policy intent
no need to change policy, the currently one perfectly does the job:
https://maven.apache.org/docs/history.html
Reagrds,
Hervé
Le dimanche 23 février 2025, 09:12
BTW I hope we won't end up with 3 vs 4 components, isn't it?
all plugins is already a huge added maintenance
Le vendredi 7 février 2025, 07:44:12 CET Hervé Boutemy a écrit :
> site plugin has a big history of parallel 3 vs 4: it's probably a good
> location to look at for
site plugin has a big history of parallel 3 vs 4: it's probably a good
location to look at for learning
need to add new columns to https://maven.apache.org/plugins/ ?
see also impact on README linking to 2 last releases in Maven Central
Regards,
Hervé
Le jeudi 6 février 2025, 20:09:31 CET Mat
let's step back one minute:
1. what problem are you trying to solve?
2. please take time to understand the larger bad implications I'm trying to
avoid
We're already struggling at maintaining full Maven scope, for the few of us
who try. I seriously fear adding more constraints will make our lif
Le jeudi 6 février 2025, 20:51:09 CET Matthias Bünger a écrit :
> Hi all,
> I would like to bring the (as of my understanding) not yet finished
> discussion about the commit/review policy with Github from a _merged_ GH
> PR [1] to the mailing list, as suggest by Hervé:
>
> As a short summuary:
> *
can we work on scaling the Jira to GH Issues first before diving into all the
implications of Maven 3 vs Maven 4 compatibility topic?
I feel we launch too much large scale and critical topics in parallel
Regards,
Hervé
Le mardi 4 février 2025, 18:53:30 CET Slawomir Jaranowski a écrit :
> Hi,
>
Le mercredi 5 février 2025, 07:48:53 CET Guillaume Nodet a écrit :
> Le mer. 5 févr. 2025 à 07:36, Slawomir Jaranowski
>
> a écrit :
> > I'm still not convitient if we really need copy all issues from jira
> > to github - as I wrote many times
> >
> > - jira will be exist with us
> > - I don't b
gt; >> what about using existing empty Jira project that you discovered?
> >> https://issues.apache.org/jira/projects/MMETRIC
> >
> >
> > That should work, I will test it.
> >
> > Thank you
> >
> > -
> > Sandra
> >
> > Am
>>>>>>> Then I think we should use a PR reference instead of a simple link.
> >>>>>>> Do you see a problem I did not expect?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> I'm fin
Le mardi 14 janvier 2025, 09:25:55 CET Julien Plissonneau Duquène a écrit :
> Le 2025-01-13 22:23, Gerd Aschemann a écrit :
> > Additionally, I wonder about the technical implementation. Keeping them
> > in one repo on separate branches makes using `repo` real hard.
> > Could we at least combine th
at 08:01, Hervé Boutemy wrote:
> >
> > oh, someone who seriously tries to maintain Maven Source Aggregator: nice!
> > https://github.com/apache/maven-sources/tree/master/aggregator
>
> Let’s see if I can manage this endeavour in the long run ;-).
>
> > I'
oh, someone who seriously tries to maintain Maven Source Aggregator: nice!
https://github.com/apache/maven-sources/tree/master/aggregator
I'm not really surprised that Maven Studies in that reactor may cause issues
https://github.com/apache/maven-studies
https://maven.apache.org/studies/
As said i
gt; >
> > Am 11.01.2025 um 12:50 schrieb Slawomir Jaranowski:
> >
> >> Should we need to map a priority from JIRA to GitHub issues - it can
> >> be useful information.
> >>
> >>
> >>
> >> If so, we can add labels like -
> >> http
Hi,
The vote has passed with the following result:
+1: Slawomir Jaranowski , Sylwester Lachiewicz, Hervé Boutemy
PMC quorum: reached
I will promote the source release zip file to the Apache distribution area and
the artifacts to the central repo
ot PRs for updates, including to Doxia
> 2. Ideally these would be included in this release.
>
> On Wed, Jan 8, 2025 at 4:56 PM Hervé Boutemy wrote:
> > Hi,
> >
> > We solved 5 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&
here is my +1
Reproducible Builds checked successfully: reference build done with JDK 11 on
*nix
Regards,
Hervé
Le mercredi 8 janvier 2025, 17:55:58 CET Hervé Boutemy a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId
Le mercredi 8 janvier 2025, 18:50:59 CET Sandra Parsick a écrit :
> - ARCHETYPE
>
> Migration result:
> https://github.com/support-and-care/mvn-issues-migration-test-archetype
> Used migration config:
> https://github.com/support-and-care/jira-to-gh-issues/blob/master/src/main/j
> ava/io/pivotal
).
>
> As I mentioned some mails before, I can give committers (and other
> interestedd person) write permission on the migration tool repository
>
>
> Am 10.01.25 um 14:52 schrieb Slawomir Jaranowski:
>
> > On Fri, 10 Jan 2025 at 12:50, Hervé Boutemy
> > w
Le vendredi 10 janvier 2025, 07:44:34 CET Slawomir Jaranowski a écrit :
> On Fri, 10 Jan 2025 at 01:59, Hervé Boutemy wrote:
> > can we have an up to date list of initial test migrations before talking
> > about large scale?
> > I see 2 tracking lists:
> We should have one
can we have an up to date list of initial test migrations before talking about
large scale?
I see 2 tracking lists:
1.
https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching
with 8 GH Issues enabled for 4 Jira projects: MPOM, MASFRES, ARCHETYPE,
MNGSITE
2 "copi
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12355247&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2261/
https://repository.apache.org/content/repositories/maven-2261/org/apache/maven/plugins/mav
we'll need to clarify what projects are guinea pigs, to stress test the issues
history copy
and releases/milestones
I see 3 cited:
- ARCHETYPE
- MCLEAN
- MJLINK
MNGSITE does not have any release, then not really something key IMHO for
testing
migration
I see also MPOM, but it seems it has be
+1
Reprodudible Builds ok: reference build done with JDK 21 on *nix
Regards,
Hervé
Le vendredi 15 novembre 2024, 16:34:46 CET Tamás Cservenák a écrit :
> Howdy,
>
> This Resolver 2.0.4 release is a bugfix release with some
> improvements as well.
>
> Maven 4.x is picking up Resolver 2.x, whil
if you rebuilt with artifact:compare, you have the diffoscope command printed,
that you can use with basic diff given it's a simple text file in the current
case:
❯ diffoscope
target/reference/org.apache.maven.surefire/surefire-3.5.2-cyclonedx.xml
target/bom.xml
--- target/reference/org.apach
The Apache Maven team is pleased to announce the release of the Apache Maven
Artifact Plugin, version 3.5.3
This plugin is used for Reproducible Builds tasks about artifacts.
https://maven.apache.org/plugins/maven-artifact-plugin/
You should specify the version in your project's plugin configur
Hi,
The vote has passed with the following result:
+1 : Slawomir Jaranowski, Michael Osipov, Jermaine Hua, Sylwester Lachiewicz,
Karl Heinz Marbaise, Tamás Cservenák, Hervé Boutemy
PMC quorum reached
I will promote the source release zip file to Apache distribution area and the
artifacts to
here is my +1
Reproducible Builds ok: reference build done with JDK 11 on *nix
Regards,
Hervé
Le dimanche 27 octobre 2024, 17:29:24 CET Hervé Boutemy a écrit :
> Hi,
>
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&ve
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12355188&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2238/
https://repository.apache.org/content/repositories/maven-2238/org/apache/maven/plugins/mav
The Apache Maven team is pleased to announce the release of the Apache Maven
Artifact Plugin, version 3.5.2
This plugin is used for Reproducible Builds tasks about artifacts.
https://maven.apache.org/plugins/maven-artifact-plugin/
You should specify the version in your project's plugin configur
Hi,
The vote has passed with the following result:
+1 : Olivier Lamy, Sylwester Lachiewicz, Tamás Cservenák, Hervé Boutemy
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and the
artifacts to the central repo
Hi,
We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12354471&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2218
https://repository.apache.org/content/repositories/maven-2218/org/apache/maven/plugins/mav
in fact, putting everything in 1 Git repo does not force to run 1 single
build: we can continue running in separate executions
and with this, nothing prevents from running the its HEAD against another
commit for Maven core build
Le jeudi 10 octobre 2024, 13:47:31 CEST Michael Osipov a écrit :
>
the resulting history looks reasonable
and we can later split with filter if necessary
I don't know if making one single build is useful, or keeping 2 separate, or
even promoting 3 (Maven core itself, ITs build, ITs run)
But definitively, doing one single Git commit when doing a feature is a cle
good idea, why not
this will be our first project doing full automated release staging from CI
https://github.com/apache/maven-mvnd/blob/master/.github/workflows/release.yaml
(= the technical reason why pushing to classical Apache staging repository has
not been done "as usual")
Regards,
Hervé
wow, I did not know that: I really love it
IIUC, these checksum files (per remote repository!) not only cover dependencies
(jars), but also:
- their poms, with parents
- plugins used during build (with their poms and parent...)
I suppose it also cover extensions?
This honestly makes me think at
everything is in the title
Jira issue is https://issues.apache.org/jira/browse/MNG-8258
PR is https://github.com/apache/maven/pull/1726
WDYT about merging this PR as part of the Maven 4 global update?
Regards,
Hervé
-
To uns
wow, going back to Maven 1, old people need to refresh their memory :)
summary looks ok to me, there is only one even more important change from
Maven 1 to Maven 2: starting with Maven 2, plugins are not bundled any more in
Maven core
(Arnaud Héritier, who did the Maven 1.1 release, remembers ho
-1, sorry
rebuilding the release, I found differences in the CycloneDX SBOM files: it
seems you have personal binaries in your local repository for Maven core 3.9.9
instead of the reference binaries from Maven Central
notice that it does not impact the .jar output, but I'd really prefer to avoi
merged to see if
it is worth the change
to me, merging install+deploy+clean+resource can be an idea
I don't see what other merges are in initial vision, in the same target plugin
that install/deploy/clean/resource or in another
Regards,
Hervé
>
> Am 19.08.24 um 09:04 schrieb
2:34 PM Gary Gregory
> >
> > wrote:
> > > > Another way to look at a "core":
> > > >
> > > > In my Maven 3.9.8 install folder I have 23 "maven-" jars including 10
> > > > "maven-resolver-". Why don
Le dimanche 18 août 2024, 13:04:39 CEST Konrad Windszus a écrit :
> > On 18. Aug 2024, at 12:59, Hervé Boutemy wrote:
> >
> > with Maven 4, we'll have to maintain a 4.x branch of each plugin in
> > parallel to the current Maven 3 compatible one: Maven 4 is t
with Maven 4, we'll have to maintain a 4.x branch of each plugin in parallel
to the current Maven 3 compatible one: Maven 4 is the right time to have the
discussion and eventually change the structure
we need to clarify what "core" means:
from https://maven.apache.org/plugins/ , I suppose we wo
I'm having a look at Jira and I could not find components releases in MSHARED
https://issues.apache.org/jira/projects/MSHARED/summary
did I miss something?
Still need to check for every plugin
Don't forget to create 3.x maintenance branch in Git too
releasing 11 components/plugins at once requi
hi Tamasz,
I think you're right on maven-dependency-tree, as it was with maven-artifact-
transfer
I'm not really convinced *many* shared stuff should be dropped: IMHO, over-
generalization
And I think that when replacing a shared stuff with direct use of an existing
API, in fact what normal peo
+1
Reproducible Build ok: reference build done with JDK 8 on Windows and umask =
022 (parent POM not upgraded, which should remove the umask requirement)
Regards,
Hervé
Le dimanche 5 mai 2024, 21:29:12 CEST Michael Osipov a écrit :
> Hi,
>
> we solved 4 issues:
> https://issues.apache.org/jir
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.5.3
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://maven.a
Hi,
The vote has passed with the following result:
+1 : zhongming hua, Olivier Lamy, Romain Manni-Bucau, Hervé Boutemy
PMC quorum reached
I will promote the source release zip file to Apache distribution area and the
artifacts to the central repo
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12354342&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2096/
https://repository.apache.org/content/repositories/maven-2096/org/apache/maven/plugins/mav
The Apache Maven team is pleased to announce the release of the Apache Maven
Plugin Tools, version 3.12.0
The Maven Plugin Tools contains the necessary tools to generate rebarbative
content like descriptor, help and documentation.
https://maven.apache.org/plugins-tools/index.html
You should sp
The Apache Maven team is pleased to announce the release of the Apache
Maven Source Plugin, version 3.3.1
The Source Plugin creates a jar archive of the source files of the current
project.
https://maven.apache.org/plugins/maven-source-plugin/
You should specify the version in your project's plu
The Apache Maven team is pleased to announce the release of the Apache Maven
Artifact Plugin, version 3.5.1
This plugin is used for Reproducible Builds tasks about artifacts.
https://maven.apache.org/plugins/maven-artifact-plugin/
You should specify the version in your project's plugin configur
Hi,
The vote has passed with the following result:
+1 : Sylwester Lachiewicz, Tamás Cservenák, Hervé Boutemy
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and the
artifacts to the central repo
Hi,
The vote has passed with the following result:
+1 : Olivier Lamy, Tamás Cservenák, Sylwester Lachiewicz, Slawomir Jaranowski,
Hervé Boutemy
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and the
artifacts to the central repo
Hi,
The vote has passed with the following result:
+1 : Sylwester Lachiewicz, Slawomir Jaranowski, Tamás Cservenák, Hervé Boutemy
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and the
artifacts to the central repo
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12354176&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2082/
https://repository.apache.org/content/repositories/maven-2082/org/apache/maven/plugin-tool
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12353471&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2081/
https://repository.apache.org/content/repositories/maven-2081/org/apache/maven/plugins/mav
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12353681&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2078/
https://repository.apache.org/content/repositories/maven-2078/org/apache/maven/plugins/mav
Hi Konrad,
I saw the fork between Maven 3.9.x where I started the documentation job and
Maven 4:
- Maven 3.9.x: https://github.com/apache/maven/pull/1444
as you can see, requiredMavenVersion exists since 3.0.2
https://issues.apache.org/jira/browse/MNG-4840
- Maven 4: https://github.com/apache/m
output file = another classifier
has to be configured
Regards,
Hervé
Le lundi 25 mars 2024, 07:31:53 CET Hervé Boutemy a écrit :
> IIUC, this is an explanation of the mystery failure that started the
> MSOURCE-121 update
>
> but after MSOURCE-121, the plugin itself stops with a
8:44, Gary Gregory a
>
> écrit :
> > Hi All,
> >
> > As long as https://issues.apache.org/jira/browse/MSOURCES-143 is in
> > play, Commons will stay on a pre-3.3.0 version.
> >
> > I re-read the comments, I still don't know what we can do in Commo
I'd like to release maven-source-plugin 3.3.1 to drop the umask sensitivity
during Reproducible Builds :)1
but there are a few issues open
https://issues.apache.org/jira/projects/MSOURCES/versions/12353471
they are related to https://issues.apache.org/jira/browse/MSOURCES-121: I
don't get what
Le lundi 26 février 2024, 13:42:19 CET Ceki Gulcu a écrit :
> Hello Bernd,
>
> I was unaware of the capabilities of the release flag. Thank you for
> explaining.
a proof that even capabilities like --release flag from JDK 9 (JEP 247 https://
openjdk.org/jeps/247) need to be promoted because it's
Le mardi 27 février 2024, 13:32:36 CET Elliotte Rusty Harold a écrit :
> Toolchains support using JDK 8 to compile even though JDK 17 is
> executing Maven, which does handle this. Unfortunately toolchains are
> poorly designed, badly documented, and not widely understood within
> the community. I'm
Le mardi 27 février 2024, 18:33:43 CET sebb a écrit :
> On Tue, 27 Feb 2024 at 17:01, Benjamin Marwell wrote:
> > > Compiling for Java 8 with
> > > Java 17 -release 8 is not the same as compiling with javac from JDK 8.
> > > They do not produce the same byte code.
+1 that's a fact
> > > There is
as discussed on the "Java version for Maven" thread(s), enablers are key IMHO
on plugins system requirements history, we started with
https://issues.apache.org/jira/browse/MPLUGIN-400
we need to fill data on every Maven -project plugin:
https://ci-maven.apache.org/job/Maven/job/maven-box/job/mave
mannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau>
> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <ht
for sure, given the JDK almanach https://javaalmanac.io/jdk/ , we'll have to
update our plans https://maven.apache.org/developers/compatibility-plan.html
the approach I'd love to promote is "what do we require to not hurt our
diversity of users when upgrading minimum prerequisites" (and I'm doin
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.5.2
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://maven.a
Hi,
The vote has passed with the following result:
+1 : Romain Manni-Bucau, zhongming hua, Guillaume Nodet, Tamás Cservenák,
Benjamin Marwell, Sylwester Lachiewicz, Slawomir Jaranowski, Karl Heinz
Marbaise, Olivier Lamy
-1: Elliotte Rusty Harold
PMC quorum reached
I will promote the source re
FYI I reviewed PRs and merged what I was confident with
I can't say if this one can be merged: I don't know the feature sufficiently
I understand the good intent of the feedback, even if I find -1 a little bit
strong: I did what I could, believe in my good intent too doing that release
Regards,
,
Hervé
Le samedi 17 février 2024, 19:00:47 CET Hervé Boutemy a écrit :
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&ve
> rsion=12352505&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/
1 - 100 of 1349 matches
Mail list logo
