The Apache Maven team is pleased to announce the release of the Apache
Maven Shared Jarsigner, version 3.1.0
https://maven.apache.org/shared/maven-jarsigner/
You should specify the version in your project's dependencies configuration:
org.apache.maven.shared
maven-jarsigner
3.1.0
You ca
Hi,
The vote has passed with the following result:
+1: Sylwester Lachiewicz, Michael Osipov, Tamás Cservenák
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
The Apache Maven team is pleased to announce the release of the Maven
Surefire version 3.4.0.
https://maven.apache.org/surefire/
Release Notes - Maven Surefire - Version 3.4.0
** Bug
* [SUREFIRE-2251] - [REGRESSION] java.lang.NoSuchMethodException:
org.apache.maven.plugin.surefire.Startu
Hi,
The vote has passed with the following result:
+1: Sylwester Lachiewicz, Michael Osipov, Tamás Cservenák, Slawomir
Jaranowski, Olivier Lamy
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
Hi,
NOTE: Read the details on this release here:
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack
we solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12354847
There are still a couple of issues left in JIRA:
https://
Hi,
NOTE: Read the details on this release here:
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack
we solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525&version=12355040
There are still a couple of issues left in JIRA:
https://
Hi,
NOTE: Read the details on this release here:
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack
we solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12355024
There are still a couple of issues left in JIRA:
https://
Hi,
NOTE: Read the details on this release here:
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack
we solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522&version=12354978
There are still a couple of issues left in JIRA:
https://
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 the right time
> > to have the discussio
The Apache Maven team is pleased to announce the release of the Maven
Fluido Skin, version 2.0.0-M10.
https://maven.apache.org/skins/maven-fluido-skin/
You should specify the version in your project's site configuration:
org.apache.maven.skins
maven-fluido-skin
2.0.0-M10
Import: This
Hi,
The vote has passed with the following result:
+1: Michael Osipov, Slawomir Jaranowski, Sylwester Lachiewicz
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file and add this release the board report.
-
I also wonder why the core needs to be sliced and diced at this level of
plugin granularity. I imagine some of ot is for historical reasons. My
comments are just born out of curiosity, this is not a criticism 😀
Gary
On Sun, Aug 18, 2024, 9:19 AM Elliotte Rusty Harold
wrote:
> Putting all plugin
Putting all plugins in a single plugin jar also makes releases more
challenging. 9 plugins might not be able to be updated because of a
critical regression in one of them.
On Sun, Aug 18, 2024 at 12:49 PM Ozgun Oz wrote:
>
> As a maven user, I agree with Konrad on the fact that putting all plugin
As a maven user, I agree with Konrad on the fact that putting all plugins
in a single plugin jar will remove the flexibility users have today to
uprade them independently in case of bug/regression/retrocompability issue
in one plugin.
Why not creating a library that regroups the duplicated code a
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't I just a single "maven-core" jar?
Gary
On Sun, Aug 18, 2024, 7:04 AM Konrad Windszus wrote:
>
>
> > On 18. Aug 2024, at 12:59, Hervé Boutemy wrote:
> >
> > with
> 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 the right time to have the
> discussion and eventually change the structure
>
> we need to clarify what "cor
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
+1
On Thu, 15 Aug 2024 at 19:38, Michael Osipov wrote:
> Hi,
>
> we solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12354803
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20
18 matches
Mail list logo
