Re: [ANN] Apache Maven Compiler Plugin 3.13.0 Released

[Slawomir Jaranowski]

pon., 18 mar 2024 o 23:35 Mark Derricutt  napisał(a):

> Interesting - I just hit:
>
> Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.13.0:compile failed: An
> API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-compiler-plugin:3.13.0:compile:
> java.lang.NoSuchMethodError:
>
> org.codehaus.plexus.compiler.javac.JavacCompiler.buildCompilerArguments(Lorg/codehaus/plexus/compiler/CompilerConfiguration;[Ljava/lang/String;)[Ljava/lang/String;
> [ERROR] -
> [ERROR] realm =
>  plugin>org.apache.maven.plugins:maven-compiler-plugin:3.13.0
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
>
> file:/Users/amrk/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/3.13.0/maven-compiler-plugin-3.13.0.jar
> [ERROR] urls[1] =
> file:/Users/amrk/.m2/repository/org/ow2/asm/asm/9.6/asm-9.6.jar
> [ERROR] urls[2] =
>
> file:/Users/amrk/.m2/repository/org/codehaus/plexus/plexus-compiler-javac-errorprone/2.8.6/plexus-compiler-javac-errorprone-2.8.6.jar
>
>

Please also try to upgrade plexus-compiler-javac-errorprone to version
2.15.0

Without an example of your configuration I only guess.


> on most of my projects.  Using Mvn 3.9.6
>
>
>
>
> --
> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
> Porcupine Tree
>
>
> On Tue, Mar 19, 2024 at 7:20 AM Slawomir Jaranowski <
> sjaranow...@apache.org>
> wrote:
>
> > The Apache Maven team is pleased to announce the release of the Apache
> > Maven Compiler Plugin, version 3.13.0
> >
> > The Compiler Plugin is used to compile the sources of your project.
> >
> > https://maven.apache.org/plugins/maven-compiler-plugin/
> >
> > You should specify the version in your project's plugin configuration:
> >
> > 
> >   org.apache.maven.plugins
> >   maven-compiler-plugin
> >   3.13.0
> > 
> >
> > You can download the appropriate sources etc. from the download page:
> >
> > https://maven.apache.org/plugins/maven-compiler-plugin/download.cgi
> >
> > Release Notes - Maven Compiler Plugin - Version 3.13.0
> >
> > ** Bug
> > * [MCOMPILER-548] - JDK 21 throws annotations processing warning that
> > can not be turned off
> >
> > ** New Feature
> > * [MCOMPILER-582] - Automatic detection of release option for JDK < 9
> > * [MCOMPILER-583] - Require Maven 3.6.3
> >
> > ** Improvement
> > * [MCOMPILER-570] - Javadoc: Add link to javac references from JDK17
> > * [MCOMPILER-574] - AbstractCompilerMojo::execute should propagate
> > exception cause
> > * [MCOMPILER-576] - Deprecate parameter "compilerVersion"
> > * [MCOMPILER-577] - Rename parameter "forceJavacCompilerUse"
> >
> > ** Task
> > * [MCOMPILER-584] - Refresh page - Using Non-Javac Compilers
> > * [MCOMPILER-585] - Refresh plugins versions in ITs
> >
> > ** Dependency upgrade
> > * [MCOMPILER-575] - Bump plexus-compiler to 2.15.0
> >
> > Enjoy,
> > -The Apache Maven team
> >
>


-- 
Sławomir Jaranowski

Re: [ANN] Apache Maven Compiler Plugin 3.13.0 Released

[Mark Derricutt]

Interesting - I just hit:

Execution default-compile of goal
org.apache.maven.plugins:maven-compiler-plugin:3.13.0:compile failed: An
API incompatibility was encountered while executing
org.apache.maven.plugins:maven-compiler-plugin:3.13.0:compile:
java.lang.NoSuchMethodError:
org.codehaus.plexus.compiler.javac.JavacCompiler.buildCompilerArguments(Lorg/codehaus/plexus/compiler/CompilerConfiguration;[Ljava/lang/String;)[Ljava/lang/String;
[ERROR] -
[ERROR] realm =
 plugin>org.apache.maven.plugins:maven-compiler-plugin:3.13.0
[ERROR] strategy =
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/amrk/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/3.13.0/maven-compiler-plugin-3.13.0.jar
[ERROR] urls[1] =
file:/Users/amrk/.m2/repository/org/ow2/asm/asm/9.6/asm-9.6.jar
[ERROR] urls[2] =
file:/Users/amrk/.m2/repository/org/codehaus/plexus/plexus-compiler-javac-errorprone/2.8.6/plexus-compiler-javac-errorprone-2.8.6.jar

on most of my projects.  Using Mvn 3.9.6




-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree


On Tue, Mar 19, 2024 at 7:20 AM Slawomir Jaranowski 
wrote:

> The Apache Maven team is pleased to announce the release of the Apache
> Maven Compiler Plugin, version 3.13.0
>
> The Compiler Plugin is used to compile the sources of your project.
>
> https://maven.apache.org/plugins/maven-compiler-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   3.13.0
> 
>
> You can download the appropriate sources etc. from the download page:
>
> https://maven.apache.org/plugins/maven-compiler-plugin/download.cgi
>
> Release Notes - Maven Compiler Plugin - Version 3.13.0
>
> ** Bug
> * [MCOMPILER-548] - JDK 21 throws annotations processing warning that
> can not be turned off
>
> ** New Feature
> * [MCOMPILER-582] - Automatic detection of release option for JDK < 9
> * [MCOMPILER-583] - Require Maven 3.6.3
>
> ** Improvement
> * [MCOMPILER-570] - Javadoc: Add link to javac references from JDK17
> * [MCOMPILER-574] - AbstractCompilerMojo::execute should propagate
> exception cause
> * [MCOMPILER-576] - Deprecate parameter "compilerVersion"
> * [MCOMPILER-577] - Rename parameter "forceJavacCompilerUse"
>
> ** Task
> * [MCOMPILER-584] - Refresh page - Using Non-Javac Compilers
> * [MCOMPILER-585] - Refresh plugins versions in ITs
>
> ** Dependency upgrade
> * [MCOMPILER-575] - Bump plexus-compiler to 2.15.0
>
> Enjoy,
> -The Apache Maven team
>

[ANN] Apache Maven Compiler Plugin 3.13.0 Released

[Slawomir Jaranowski]

The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.13.0

The Compiler Plugin is used to compile the sources of your project.

https://maven.apache.org/plugins/maven-compiler-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-compiler-plugin
  3.13.0


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-compiler-plugin/download.cgi

Release Notes - Maven Compiler Plugin - Version 3.13.0

** Bug
* [MCOMPILER-548] - JDK 21 throws annotations processing warning that
can not be turned off

** New Feature
* [MCOMPILER-582] - Automatic detection of release option for JDK < 9
* [MCOMPILER-583] - Require Maven 3.6.3

** Improvement
* [MCOMPILER-570] - Javadoc: Add link to javac references from JDK17
* [MCOMPILER-574] - AbstractCompilerMojo::execute should propagate
exception cause
* [MCOMPILER-576] - Deprecate parameter "compilerVersion"
* [MCOMPILER-577] - Rename parameter "forceJavacCompilerUse"

** Task
* [MCOMPILER-584] - Refresh page - Using Non-Javac Compilers
* [MCOMPILER-585] - Refresh plugins versions in ITs

** Dependency upgrade
* [MCOMPILER-575] - Bump plexus-compiler to 2.15.0

Enjoy,
-The Apache Maven team

[ANN] Apache Maven Assembly Plugin 3.7.1 Released

[Slawomir Jaranowski]

The Apache Maven team is pleased to announce the release of the Apache
Maven Assembly Plugin, version 3.7.1

The Assembly Plugin for Maven enables developers to combine project output
into a single distributable archive that also contains dependencies,
modules, site documentation, and other files.

https://maven.apache.org/plugins/maven-assembly-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-assembly-plugin
  3.7.1


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-assembly-plugin/download.cgi

Release Notes - Maven Assembly Plugin - Version 3.7.1

** Bug
* [MASSEMBLY-1020] - Cannot invoke "java.io.File.isFile()" because
"this.inputFile" is null
* [MASSEMBLY-1021] - Nullpointer in assembly:single when upgrading to
3.7.0
* [MASSEMBLY-1022] - Unresolved artifacts should be not processed

** Dependency upgrade
* [MASSEMBLY-1023] - Bump org.apache.maven.shared:maven-filtering from
3.3.1 to 3.3.2
* [MASSEMBLY-1024] - Bump org.apache.commons:commons-compress from
1.25.0 to 1.26.1
* [MASSEMBLY-1025] - Bump org.codehaus.plexus:plexus-archiver from
4.9.1 to 4.9.2


Enjoy,
-The Apache Maven team

[RESULT] [VOTE] Release Apache Maven Compiler Plugin version 3.13.0

[Slawomir Jaranowski]

Hi,

The vote has passed with the following result:

+1: Tamás Cservenák, Karl Heinz Marbaise, Sylwester Lachiewicz, Herve
Boutemy, Olivier Lamy

PMC quorum: reached

I will promote the source release zip file to the Apache distribution area
and the artifacts to the central repo.

-- 
Sławomir Jaranowski

[RESULT] [VOTE] Release Apache Maven Assembly Plugin version 3.7.1

[Slawomir Jaranowski]

Hi,

The vote has passed with the following result:

+1: Tamás Cservenák, Karl Heinz Marbaise, Sylwester Lachiewicz, Herve
Boutemy

PMC quorum: reached

I will promote the source release zip file to the Apache distribution area
and the artifacts to the central repo.

-- 
Sławomir Jaranowski

[ANN] Apache Maven GPG Plugin 3.2.1 Released

[Tamás Cservenák]

Howdy,

The Apache Maven team is pleased to announce the release of the Apache
Maven GPG Plugin, version 3.2.1

This release is a bugfix, restoring plugin ability to pick up GPG
passphrase from settings.xml. Have to be noted though, that this method of
getting passphrases is considered "bad practice".

This plugin signs all of the project's attached artifacts with GnuPG or BC.

https://maven.apache.org/plugins/maven-gpg-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-gpg-plugin
  3.2.1


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-gpg-plugin/download.cgi

Release Notes - Maven GPG Plugin - Version 3.2.1

** Bug
* [MGPG-112] - Upgrading from 3.1.0 to 3.2.0 with no other changes
causes "gpg: signing failed: No pinentry"
** Dependency upgrade
* [MGPG-111] - Clean up dependency declarations

Have fun,
-The Apache Maven team

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.13.0

[Olivier Lamy]

+1

On Fri, 15 Mar 2024 at 17:37, Slawomir Jaranowski
 wrote:
>
> Hi,
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12354079
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2072/
> https://repository.apache.org/content/repositories/maven-2072/org/apache/maven/plugins/maven-compiler-plugin/3.13.0/maven-compiler-plugin-3.13.0-source-release.zip
>
> Source release checksum(s):
> maven-compiler-plugin-3.13.0-source-release.zip - SHA-512 :
> 99897c8350e50ba0ad9fcba210dad772d7f9e465358c35752942b71e3c7d2ca54d1e9115cc657130829135f1598a091436463744ef00de0cbee6042862abddf5
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-compiler-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release Apache Maven GPG Plugin version 3.2.1

[Tamás Cservenák]

Howdy,

The vote has passed with the following result:

+1: Slawomir, Karl-Heinz, Sylwester, Herve, Olivier

PMC quorum: reached

I will promote the artifacts to the central repo, the source release ZIP
file and add this release to the board report.

Thanks
T

Re: Notes on maven-compiler-plugin work

[sebb]

On Mon, 18 Mar 2024 at 07:50, Romain Manni-Bucau  wrote:
>
> Hi Martin,
>
> Since we'll go v4 and really change the impl I guess we can drop all the
> compiler args from properties and the not relevant options.

It would be helpful if there was a migration page that explained to
users how to handle settings that are no longer supported. This could
be quoted in the relevant error message.

> Ultimately the only options would be:
>
> * fork options
> * compiler args
> * log/outputs options
>
> Anything else brings confusion and prevents us to validate properly the
> command before it is executed (as of today).
>
> +1 to not "preparePaths" and just let the compilation be native.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
>
>
> Le lun. 18 mars 2024 à 00:31, Martin Desruisseaux <
> martin.desruisse...@geomatys.com> a écrit :
>
> > Hello all
> >
> > I'm not yet ready to submit a pull request for the reworked
> > maven-compiler-plugin, but I would like to report some details about
> > changes that would come, if accepted. This work is for Maven 4 only, the
> > plugin for Maven 3 will stay unaffected.
> >
> > As proposed on GitHub comment [1], I'm modifying the implementation for
> > using the standard javax.tools.JavaCompiler interface instead of the
> > Plexus compiler. That interface is part of standard JDK since Java 6. It
> > seems that the Eclipse compiler provides also an implementation of that
> > interface, so compiler independence should be preserved. Forked
> > compilation is handled by a custom implementation of that interface. The
> > javax.tools.JavaCompiler interface has some methods needed for Java
> > modules, for which I saw no direct equivalence in Plexus API. The gap
> > may grow larger if future Java versions bring more evolution to the
> > compiler API. The standard interface also has a cache mechanism that may
> > bring performance improvements (to be verified) when compiling more than
> > one set of sources, e.g. for multi-versions. It also opens the door for
> > handling source and classes that are not files, for example by doing
> > everything in memory (I have no plan to use this features now, but it
> > become a possibility for the future).
> >
> > The way to handle compiler options has been modified. Previously, the
> > Maven plugin validated some options before to pass them to the compiler.
> > For example, if the  value contains anything else than
> > "lines", "vars" or "source", the plugin raised an error. The intend was
> > to provide more informative message. But in the javax.tools.JavaCompiler
> > interface, there is an API telling us whether an option is supported.
> > Therefor, the new plugin version first asks to the compiler whether the
> > option is supported, and only if the compiler said "no", the validation
> > is performed for producing the error message. Consequently, if the
> > compiler claims to support the "-g:foo" option, then the plugin will no
> > longer block the use of the "foo" value in  even if the
> > plugin does not know that value.
> >
> > The set of plugin parameters is the same as before: no addition and no
> > removal, but there is some deprecation. Of course, what to deprecate or
> > not is open to discussion. In the current state of work, the following
> > parameters are deprecated but are still working:
> >
> >   *  (a single String): already replaced by
> >  (a list of Strings) since Maven 3.1.
> >   * : replaced by ordinary dependencies with
> > proc, a new artifact type introduced in Maven 4-alpha13.
> >
> > The following parameters are marked as deprecated for removal in the
> > current state of work. They all became no-op in the new plugin:
> >
> >   * : the documentation is not really explicit,
> > but it seems to be about forcing the use of java.lang.Compiler
> > instead of javax.tools.JavaCompiler (it does not seem to be about
> > the javac command). The java.lang.Compiler class was deprecated
> > since Java 9 and no longer exists in Java 21.
> >   * : bundling many class files into a single file can
> > be considered as the task of separated plugins, for example the JAR
> > plugin. Furthermore, this parameter does not fit well in the context
> > of Module Source Hierarchy, because the output is not a single JAR.
> >   * : the way that the javax.tools.JavaCompiler
> > API is designed, this parameter does not seem relevant to instances
> > of that interface. The parameter may be partially relevant to some
> > objects used by JavaCompiler, but not fully (e.g. the "reuseSame"
> > parameter value stay inapplicable). I suggest to let those decisions
> > as plugin implementation details.
> >  

Re: [VOTE] Release Apache Maven GPG Plugin 3.2.1

[Olivier Lamy]

+1

On Fri, 15 Mar 2024 at 6:25 PM, Tamás Cservenák  wrote:

> Howdy,
>
> Note: this is a bugfix release for
> https://issues.apache.org/jira/browse/MGPG-112
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354394
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MGPG/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2074/
>
> Source release checksum SHA512:
>
> 19bb9d57b2caec3524ecc3abc8efb818061541874011763c474c0d60608a3b156eb0ad92299bba2a24ba86b8021c2b5d89c2531a918e913453e170dcfa125d1e
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

Re: Notes on maven-compiler-plugin work

[Romain Manni-Bucau]

Hi Martin,

Since we'll go v4 and really change the impl I guess we can drop all the
compiler args from properties and the not relevant options.
Ultimately the only options would be:

* fork options
* compiler args
* log/outputs options

Anything else brings confusion and prevents us to validate properly the
command before it is executed (as of today).

+1 to not "preparePaths" and just let the compilation be native.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 18 mars 2024 à 00:31, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :

> Hello all
>
> I'm not yet ready to submit a pull request for the reworked
> maven-compiler-plugin, but I would like to report some details about
> changes that would come, if accepted. This work is for Maven 4 only, the
> plugin for Maven 3 will stay unaffected.
>
> As proposed on GitHub comment [1], I'm modifying the implementation for
> using the standard javax.tools.JavaCompiler interface instead of the
> Plexus compiler. That interface is part of standard JDK since Java 6. It
> seems that the Eclipse compiler provides also an implementation of that
> interface, so compiler independence should be preserved. Forked
> compilation is handled by a custom implementation of that interface. The
> javax.tools.JavaCompiler interface has some methods needed for Java
> modules, for which I saw no direct equivalence in Plexus API. The gap
> may grow larger if future Java versions bring more evolution to the
> compiler API. The standard interface also has a cache mechanism that may
> bring performance improvements (to be verified) when compiling more than
> one set of sources, e.g. for multi-versions. It also opens the door for
> handling source and classes that are not files, for example by doing
> everything in memory (I have no plan to use this features now, but it
> become a possibility for the future).
>
> The way to handle compiler options has been modified. Previously, the
> Maven plugin validated some options before to pass them to the compiler.
> For example, if the  value contains anything else than
> "lines", "vars" or "source", the plugin raised an error. The intend was
> to provide more informative message. But in the javax.tools.JavaCompiler
> interface, there is an API telling us whether an option is supported.
> Therefor, the new plugin version first asks to the compiler whether the
> option is supported, and only if the compiler said "no", the validation
> is performed for producing the error message. Consequently, if the
> compiler claims to support the "-g:foo" option, then the plugin will no
> longer block the use of the "foo" value in  even if the
> plugin does not know that value.
>
> The set of plugin parameters is the same as before: no addition and no
> removal, but there is some deprecation. Of course, what to deprecate or
> not is open to discussion. In the current state of work, the following
> parameters are deprecated but are still working:
>
>   *  (a single String): already replaced by
>  (a list of Strings) since Maven 3.1.
>   * : replaced by ordinary dependencies with
> proc, a new artifact type introduced in Maven 4-alpha13.
>
> The following parameters are marked as deprecated for removal in the
> current state of work. They all became no-op in the new plugin:
>
>   * : the documentation is not really explicit,
> but it seems to be about forcing the use of java.lang.Compiler
> instead of javax.tools.JavaCompiler (it does not seem to be about
> the javac command). The java.lang.Compiler class was deprecated
> since Java 9 and no longer exists in Java 21.
>   * : bundling many class files into a single file can
> be considered as the task of separated plugins, for example the JAR
> plugin. Furthermore, this parameter does not fit well in the context
> of Module Source Hierarchy, because the output is not a single JAR.
>   * : the way that the javax.tools.JavaCompiler
> API is designed, this parameter does not seem relevant to instances
> of that interface. The parameter may be partially relevant to some
> objects used by JavaCompiler, but not fully (e.g. the "reuseSame"
> parameter value stay inapplicable). I suggest to let those decisions
> as plugin implementation details.
>   * : deprecated as a consequence of
>  deprecation.
>
> The following parameters had their default value modified:
>
>   *  and : removed the default value and added a Javadoc
> saying "As of Java 9, the --release option is preferred." Its
> default value (if any) has not yet been chosen.
>
> Finally, the CompilerMojo and TestCompilerMojo subclasses contained
> magic in their preparePaths(…) method 

Re: [VOTE] Release Apache Maven GPG Plugin 3.2.1

[Herve Boutemy]

+1

Reproducible Build ok: reference build done with JDK 21 on *nix with umask 022

Regards,

Hervé

On 2024/03/15 08:25:07 Tamás Cservenák wrote:
> Howdy,
> 
> Note: this is a bugfix release for
> https://issues.apache.org/jira/browse/MGPG-112
> 
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354394
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MGPG/issues
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2074/
> 
> Source release checksum SHA512:
> 19bb9d57b2caec3524ecc3abc8efb818061541874011763c474c0d60608a3b156eb0ad92299bba2a24ba86b8021c2b5d89c2531a918e913453e170dcfa125d1e
> 
> Staging site:
> https://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for at least 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Assembly Plugin version 3.7.1

[Herve Boutemy]

+1

Reproducible Build ok: reference build done with JDK 21 on *nix with umask 022

Regards,

Hervé

On 2024/03/15 07:58:49 Slawomir Jaranowski wrote:
> Hi,
> 
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12354406
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2073/
> https://repository.apache.org/content/repositories/maven-2073/org/apache/maven/plugins/maven-assembly-plugin/3.7.1/maven-assembly-plugin-3.7.1-source-release.zip
> 
> Source release checksum(s):
> maven-assembly-plugin-3.7.1-source-release.zip - SHA-512 :
> 599fb208058b2fea3ea6af6db6e56bd1d2653f8d36061c46c0fb0634f5e7b6fd7eb968fb05754538001ee692c21f4ae4289d040f74a9d327f1a4cd2eba38
> 
> Staging site:
> https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for at least 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -- 
> Sławomir Jaranowski
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.13.0

[Herve Boutemy]

+1

Reproducible Build ok: reference done with JDK 21 on *nix and umask 022

Regards,

Hervé

On 2024/03/15 07:36:15 Slawomir Jaranowski wrote:
> Hi,
> 
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12354079
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2072/
> https://repository.apache.org/content/repositories/maven-2072/org/apache/maven/plugins/maven-compiler-plugin/3.13.0/maven-compiler-plugin-3.13.0-source-release.zip
> 
> Source release checksum(s):
> maven-compiler-plugin-3.13.0-source-release.zip - SHA-512 :
> 99897c8350e50ba0ad9fcba210dad772d7f9e465358c35752942b71e3c7d2ca54d1e9115cc657130829135f1598a091436463744ef00de0cbee6042862abddf5
> 
> Staging site:
> https://maven.apache.org/plugins-archives/maven-compiler-plugin-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for at least 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -- 
> Sławomir Jaranowski
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org