-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/
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12352505&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-2065/
https://repository.apache.org/content/repositories/maven-2065/org/apache/maven/plugins/mav
Le dimanche 21 janvier 2024, 22:03:59 CET Guillaume Nodet a écrit :
> At build time, I think it's fine to bump to whatever is needed to make
> our life manageable. If 17 is required, so be it.
+1
my biggest concern with Maven 4 is not JDK runtime requirement, but plugins
future when a plugin want
uh, it had been dropped by inadvertance in
https://github.com/apache/maven-doxia-site/commit/ecd62ed94b6e9445237e780171edff8f437a4895
doxia-tools needs rework, since it's not only one component but a collection,
like plugins/ in Maven site
I'll do the update
Le dimanche 7 janvier 2024, 12:47:0
interesting details
IMHO, we're back to the HTTP wire protocol between Maven CLI and repositories
not being precisely defined on edge cases
= what to put as HTTP return code, what to put as reason phrase (deprecated in
HTTP/1.1, removed in HTTP/2), and what to get from HTTP body
idea has been s
for the records, "Maven Plugins Compatibility Plan" strategy is stored in
https://maven.apache.org/developers/compatibility-plan.html
= the doc to refer to and update if necessary after the current discussion
Le vendredi 29 décembre 2023, 14:42:17 CET Slawomir Jaranowski a écrit :
> Hi,
>
> Las
notice that it is also the javadoc spirit: when there is a long multi-line
description, table is expected to keep only first line and detail the full
description
Le samedi 23 décembre 2023, 23:29:22 CET Konrad Windszus a écrit :
> Hi,
> currently those sections deviate slightly (e.g. the overvie
in early days, from memory, there were a few fields displayed only in the
details section
https://maven.apache.org/plugins-archives/maven-compiler-plugin-2.2/compile-mojo.html
like expression: I don't find anything else (perhaps even older reports had
more fields like this one)
but you're right,
Hi Piotr,
Thinking at it carefully, AFAIK it is a design decision done in early Maven 2
design time:
- POM properties don't influence dependencies
- profile activation influence dependencies
(I don't know for CLI properties)
The rationale is that:
1. POM properties are expected to be fixed once
isted in
> https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Mapping
> _Value_Objects support conversion from string. There is nothing built in for
> complex classes containing multiple values of different types.
>
> Konrad
>
> > On 17. Nov 2023, at 08:5
my use case: I want sometimes to execute maven-toolchain-plugin or animal-
sniffer-maven-plugin on CLI without updating pom.xml
the only issue I'm facing is how to write the -D properties to populate a few
fields from Objects required in plugin configuration:
- signature groupId/artifactId/versi
no need to change the build prerequisite: just add a profile to activate the
release flag on newer JDK:
https://issues.apache.org/jira/browse/MPOM-447
Regards,
Hervé
Le lundi 13 novembre 2023, 20:38:00 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> currently we have already the build requirements
Le lundi 23 octobre 2023, 10:00:59 CEST Guillaume Nodet a écrit :
> Le sam. 21 oct. 2023 à 18:19, Herve Boutemy a écrit :
> > I updated release notes
> >
> > a few remarks/questions:
> >
> > - it would be nice to have a description in Jira issues for all the new
> > features, because some titles
+1
Reproducible Builds ok: reference build done with JDK 8 on Windows and umask
022
Regards,
Hervé
Le mardi 3 octobre 2023, 11:12:36 CEST Michael Osipov a écrit :
> Hi,
>
> IMPORTANT: Requires Doxia Sitetools 2.0.0-M12, Maven Reporting Impl
> 4.0.0-M10, Maven Reporting Exec 2.0.0-M10 vote/sta
+1
Reproducible Builds ok: reference build done with JDK 8 on Windows and umask
022
Regards,
Hervé
Le mardi 3 octobre 2023, 00:14:52 CEST Michael Osipov a écrit :
> Hi,
>
> IMPORTANT: Requires Doxia Sitetools 2.0.0-M12, Maven Reporting Impl
> 4.0.0-M10 vote/staging repo!
>
> we solved 3 issu
I updated my svn and ran:
for f in *
do
rm $f
wget
https://repository.apache.org/content/repositories/maven-1996/org/apache/maven/apache-maven/3.9.5/$f
done
both in source and binaries: this resulted in .asc change in source only,
everything else was ok
I committed the update
now we hav
yes, you can drop the staging repository and re-deploy: only the 2 -bin
archives will be different
Regards
Hervé
Le lundi 2 octobre 2023, 11:10:36 CEST Tamás Cservenák a écrit :
> Bah,
>
> This is the same problem as before... but originally it happened on my
> desktop. This time the release w
+1
Reproducible Builds ok: reference build done with JDK 8 on Windows and umask
022
Regards,
Hervé
Le dimanche 1 octobre 2023, 20:19:26 CEST Michael Osipov a écrit :
> Hi,
>
> IMPORTANT: Requires Doxia Sitetools 2.0.0-M12 vote/staging repo!
>
> we solved 3 issues:
> https://issues.apache.org
+1
Reproducible Builds ok: reference build done with JDK 8 on Windows and umask
022
Regards,
Hervé
Le dimanche 1 octobre 2023, 20:03:02 CEST Michael Osipov a écrit :
> Hi,
>
> we solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&ve
> rsion=12353413
>
The Apache Maven team is pleased to announce the release of the Apache Maven
Artifact Plugin, version 3.5.0
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, Michael Osipov, Hervé Boutemy
PMC quorum reached
I will promote the source release zip file to Apache distribution area and the
artifacts to the central repo
was intended to the list :)
-- Message transmis --
Objet : Re: [VOTE] Release Apache Maven Artifact Plugin version 3.5.0
Date : samedi 30 septembre 2023, 18:45:51 CEST
De : Michael Osipov
À : Hervé Boutemy
Am 2023-09-29 um 08:00 schrieb Hervé Boutemy:
> Hi,
>
> We
+1
Reproducible Builds ok: reference build done on *nix with JDK 11
Regards,
Hervé
Le vendredi 29 septembre 2023, 08:00:39 CEST Hervé Boutemy a écrit :
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&ve
> rsion=1235
ly to be a net security
> negative. Is there a string reason to check PGP signatures at build
> time? And if there is, why are we doing this with a fixed map instead
> of looking them up in Maven Central?
>
> On Fri, Sep 29, 2023 at 2:00 AM Hervé Boutemy wrote:
> > Hi
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12353118&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1992/
https://repository.apache.org/content/repositories/maven-1992/org/apache/maven/plugins/mav
+1
Reproducible Builds ok: reference build done with JDK 17 on *nix with umask
022
Regards,
Hervé
Le vendredi 22 septembre 2023, 20:28:55 CEST Tamás Cservenák a écrit :
> Howdy,
>
> Note: Maven Resolver 1.x lineage after this release is going into "bugfix
> only" maintenance mode (and will be
+1
Reproducible Builds ok: reference build done with JDK 17 on *nix with umask
022
Regards,
Hervé
Le jeudi 21 septembre 2023, 21:51:21 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&ve
> rsion=123533
+1
Reproducible Build not fully ok: reference build done with JDK 17 on *nix with
umask 022
maven-javadoc-plugin-3.6.0-source-release.zip is the file that is not
reproducible: it contains non-reproducible src/it/mrm/3rdparty/_doclet-1.0.jar
and src/it/mrm/repository/_mjavadoc450-static.jar
I s
can you try plexus-xml 3.0.0 and confirm this works as you expected initially,
please?
Regards,
Hervé
Le mardi 25 juillet 2023, 20:56:04 CEST Slawomir Jaranowski a écrit :
> Hi
>
> I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
> maven-enforcer
>
> In maven-enf
to 4, as it breaks (for now)
running your code in Maven 3 but requires Maven 4
Thanks for the feedback, this helped us clarify the plan
Regards,
Hervé
Le dimanche 10 septembre 2023, 18:50:27 CEST Hervé Boutemy a écrit :
> working on it, I created a branch for plexus-xml 3.x:
>
ot only to plugins but also to shared libs for
> maven (ASF also plexus and mojohous)
>
> Sylwester
>
> niedz., 10 wrz 2023, 09:00 użytkownik Hervé Boutemy
>
> napisał:
> > Le samedi 9 septembre 2023, 19:33:51 CEST Václav Haisman a écrit :
> > > On 2
Le samedi 9 septembre 2023, 19:33:51 CEST Václav Haisman a écrit :
> On 25. 07. 23 20:56, Slawomir Jaranowski wrote:
> > Hi
> >
> > I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
> > maven-enforcer
> >
> > In maven-enforcer (and in many other plugins ...) is used,
n-xml-impl update = what is causing the compatibility issue
Regards,
Hervé
Le samedi 9 septembre 2023, 11:33:59 CEST Hervé Boutemy a écrit :
> > o.c.p:p-u 4.x that depends on
> > -> o.c.p:p-xml 4 that depends on
>
> notice this dependency is *optional*
> it's useful on
ok, I updated plexus-utils and plexus-xml sites
and added a few key aspects about how these relate to old Plexus Utils 3
https://codehaus-plexus.github.io/plexus-utils/
https://codehaus-plexus.github.io/plexus-xml/
I hope this will help
Le samedi 9 septembre 2023, 11:14:52 CEST Hervé Boutemy a
> o.c.p:p-u 4.x that depends on
> -> o.c.p:p-xml 4 that depends on
notice this dependency is *optional*
it's useful only for ReaderFactory/WriterFactory, for XmlReader/Writer
fully removing the dependency would have broken full compatibility by removing
a few methods: it was preferred to mark the
yes
notice p-u site is broken https://codehaus-plexus.github.io/plexus-utils/
and we should probably also find a way to publish also latest p-u 3 javadoc in
parallel
I'll see what I can do also to help on this
Le vendredi 8 septembre 2023, 10:53:11 CEST Slawomir Jaranowski a écrit :
> Thanks, I
right conclusion
Le mercredi 26 juillet 2023, 06:55:10 CEST Christoph Läubrich a écrit :
> I tried the same with Tycho and the conclusion was that a maven plugin
> can currently not upgrade to plexus-xml4 if you still want to support
> maven 3.x
>
> Am 25.07.23 um 20:56 schrieb Slawomir Jaranowsk
in fact, whatever you do in your plugin POM, they are provided by Maven core
at runtime (ignoring the precise version the plugin asked for)
but marking them provided in your plugin pom.xml makes this fact more visible
Regards,
Hervé
Le jeudi 31 août 2023, 03:15:15 CEST Jeremy Landis a écrit :
/Git+Migration
Le samedi 26 août 2023, 09:50:28 CEST Hervé Boutemy a écrit :
> Hi Volkan,
>
> Yes, I worked a lot on this aspect fo Maven: the result is summarised here
> https://maven.apache.org/scm.html
>
> As you can see, you can get "Maven Full Sources" in one command
Hi Volkan,
Yes, I worked a lot on this aspect fo Maven: the result is summarised here
https://maven.apache.org/scm.html
As you can see, you can get "Maven Full Sources" in one command using Google
"repo" tool.
Please have a llok and we can dive into more details if you need
Regards,
Hervé
Le
you probably rebuilt the release with "mvn install" = what you need to avoid
and it seems the rebuild was done with an environment that did not give you the
same output as the reference build
FYI, I was able to rebuild Maven Resolver 1.9.14 with the same output as you
https://github.com/jvm-repo-
+1
Reproducible Build ok: reference done on *nix with JDK 17 and umask 022
Regards,
Hervé
Le jeudi 22 juin 2023, 11:47:30 CEST Slawomir Jaranowski a écrit :
> +1
>
> wt., 20 cze 2023 o 16:13 Tamás Cservenák napisał(a):
> > Howdy,
> >
> > We solved 2 issues:
> >
> > https://issues.apache.org
Le dimanche 18 juin 2023, 21:49:41 CEST Guillaume Nodet a écrit :
> Le dim. 18 juin 2023 à 21:14, Hervé Boutemy a
>
> écrit :
> > I now understand our divergence: you implicitely use Maven 4 with some
> > updates
> > already done on xsd versions that I did not
and externally for Maven Central
if one of these is chosen, I ask everybody to seriously work on it and
document all the new aspects that this reveals
Don't just say "nice"
Regards,
Hervé
Le samedi 17 juin 2023, 10:07:42 CEST Guillaume Nodet a écrit :
> Le ven. 16 juin 20
se can you check 1.9.11 as well? IMHO there must
> > be the same issue present, or if not, am even more puzzled...
> >
> > T
> >
> > On Fri, Jun 16, 2023 at 7:13 PM Hervé Boutemy
> >
> > wrote:
> >> +1
> >>
> >> notice that Repr
nced in the POM. That way you can have more
> > room to try changes to the POM format. But there really should be a
> > mechanism for pushing POM changes downstream and XSD seems like a good
> > option for that. Sorry if this is already the plan and I'm repeating what
>
+1
notice that Reproducible Builds is NOT ok on 1 file: reference build done on
*nix with JDK 17 and umask 022
the only issue is in maven-resolver-named-locks-redisson-1.9.12-bundle.zip:
│--rw--- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar
│+-rw-r--r-- 2.0 unx49423 b- de
Le lundi 12 juin 2023, 01:50:56 CEST Guillaume Nodet a écrit :
> > Don't look at Maven code to judge: the whole logic is based on "known
> > unknown"
> > = we don't know who parses POMs published to Maven Central, but there are
> > many
> > (it's easy to cite many, but not all).
>
> I can't buy th
+1
Reproducible Build ok: reference done with JDK 8 on Windows
Regards,
Hervé
Le dimanche 11 juin 2023, 22:14:08 CEST Michael Osipov a écrit :
> Hi,
>
> we solved 17 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&ve
> rsion=12350597
>
> There are still a c
since depth changes?
>
> Also drops some build meta which cant be resoled anymore portably like
> compiler setup, which graalvm version was used and lastly would need to
> drop or not props not used elsewhere.
> Think staying as close as possible of the source is overall good
wow, what a release!
+1
Reproducible build ok
Regards,
Hervé
Le dimanche 11 juin 2023, 19:02:05 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&ve
> rsion=12352680
>
> Commits:
> https://github.com/
Le vendredi 9 juin 2023, 11:22:26 CEST Guillaume Nodet a écrit :
> Le ven. 9 juin 2023 à 08:59, Hervé Boutemy a écrit :
> > adding a new POM element in build POM was supposed to be something for
> > Maven 5
> > and to trigger a POM 5 version, to make clear that we are le
adding a new POM element in build POM was supposed to be something for Maven 5
and to trigger a POM 5 version, to make clear that we are leaving the Maven 3
space (that uses POM version 4, hence the need for version clarification
between Maven and it POM model version)
if we enter that space bef
Le mardi 6 juin 2023, 20:19:23 CEST Guillaume Nodet a écrit :
> One question for people that want JDK 8 support. What IDE do they use to
> develop ? Because none of the actual IDE is running JDK 8, though they can
> be used by JDK 8, just like maven with toolchains.
good point, thanks for adding t
lt;https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> Le mar. 6 juin 2023 à 09:11, Hervé Boutemy a écrit :
> > you're right that we're currently talking about core, not plugins
> >
> > but this question will inevitably extend from
.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> Le mar. 6 juin 2023 à 08:27, Hervé Boutemy a écrit :
> > > > notice that this will also impact all plugins: and given the few work
> >
>
> > notice that this will also impact all plugins: and given the few work done
> > on
> > plugins to clearly show what plugin version remains compatible with a JDK
> > release, I feel we're not taking the topic the right way
>
> Can you detail it please? While we keep plugin-api java 8 compat - wh
Le mardi 6 juin 2023, 01:54:27 CEST Henning Schmiedehausen a écrit :
> To get this discussion a bit more back to actual substance:
>
> Do you still need toolchains with JDK 11/17? I set the release version to
> "8" (or anything else) in my builds, ripped out all the toolchains and it
> "just works
I think this difference during Maven build between compile time JDK vs tests
execution time JDK is key for normal users choice. And ease of setup if
multiple JDKs are involved (= it's not easy to have configured prerequisites in
place)
I suppose good articles showing the full setup to do so wou
it's not about *one not wanting* to upgrade (anybody can use JDK 17 if they
want currently)
it's about *one forcing everybody else* to upgrade (and enter the toolchain
setup question)
I'd be curious to see what will happen the day one of the base plugin force to
upgrade:
https://ci-maven.apac
+1
I really don't what benefit we get from going to Java 17
I perfectly see the impact we'll have on our users: for what benefit?
notice that this will also impact all plugins: and given the few work done on
plugins to clearly show what plugin version remains compatible with a JDK
release, I f
Le lundi 29 mai 2023, 13:50:58 CEST Karl Heinz Marbaise a écrit :
> To fulfill the formalism (also have documented the decision here on the
> ML) we should start simply a VOTE to get an in general decision about
> moving to GH-issues to leave JIRA behind... (not about the details) that
> can be don
+1
Reproducible Builds ok: reference build done with JDK 8 on Windows
Regards,
Hervé
Le vendredi 26 mai 2023, 21:29:11 CEST Michael Osipov a écrit :
> Hi,
>
> we solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&ve
> rsion=12353222
>
> There are stil
Le vendredi 26 mai 2023, 19:41:53 CEST Benjamin Marwell a écrit :
> Big +1, as more and more projects are already migrating (including Apache
> Shiro).
>
> I'd vote for maven-jlink-plugin: Not many issues currently.
>
> > not having to create an issue if a PR exists first
>
> I'd at least make m
on testing GH issues migration from Jira: yes
cache-extension [1] looks like an interesting example, given it has a small
history with its Jira content
we also have mvnd which uses GH issues from the start: testing and making
clear practices on release and release notes could also be worked ther
+1
Reproducible Build ok: reference build done with JDK 17 on *nix
Regards,
Hervé
Le lundi 15 mai 2023, 20:55:39 CEST Tamás Cservenák a écrit :
> Howdy,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&ve
> rsion=12353247
>
> There are still
The Apache Maven team is pleased to announce the release of the Apache Maven
3.1.0 Plugin, version 3.1.0
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 configuration
1 - 100 of 1283 matches
Mail list logo
