Yet I see the version is publicly available and a lot of automatic pull
requests already created to bump maven-compiler-plugin to 3.14.1.
Example:
https://github.com/neo4j/neo4j-kafka-connector/pull/419
Did something went wrong with the release process or did I miss
something ?
Filipe Roque
s detected for me on the company projects.
Filipe Roque
On Wed, 2025-03-19 at 14:20 +0100, Thomas Reinhardt wrote:
>
> For example we import com.fasterxml.jackson:jackson-parent which
> fixes
> versions of about 60 artifacts. Of course we don't use all of those
> but
> if we add e.g. some new transport mechanism, we are automatically
> getting the c
https://issues.apache.org/jira/browse/MNG-8333 duplicate-finder-maven
starts to fail with 4.0.0-beta-5
I was also having problems with git-commit-id-maven-plugin but
upgrading it to 8.0.2 solves it.
flip
On Sat, 2024-10-19 at 20:26 +0200, Tamás Cservenák wrote:
> Howdy,
>
> We solved 68 issues
Detected an issue with maven cache extension
https://issues.apache.org/jira/browse/MNG-8123
Filipe Roque
On Tue, 2024-05-14 at 13:58 +0200, Mateusz Gajewski wrote:
> -1 from our testing at Trino
> (https://github.com/trinodb/trino/pull/21966)
>
> Previous alphas worked for us, be
mail announcement but is not easy way to find release
notes.
Filipe Roque
On Mon, 2024-03-11 at 00:09 +0100, Slawomir Jaranowski wrote:
> The Apache Maven team is pleased to announce the release of the
> Apache
> Maven Assembly Plugin, version 3.7.0
>
> The Assembly Plugi
elease with a fix for MENFORCER-394.
Filipe Roque
was also asking here last week about any plans for a
3.0.0-M4 release [1].
The lastest version 3.0.0-M3 was released in November 2019.
[1]
https://mail-archives.apache.org/mod_mbox/maven-dev/202101.mbox/%3CCAG-XB5YtM5DhR5dyN2fzfFn7d8wBcAmhV6Bm%2BKR3CATtWiiLpQ%40mail.gmail.com%3E
Filipe Roque
