[ANN] Apache Maven Build cache extension

2024-05-12 Thread Olivier Lamy
The Apache Maven team is pleased to announce the release of the Apache
Maven Build cache extension, version 1.2.0

Build cache is an extension that makes large Maven builds more efficient.

A combination of features achieves that:
- Incremental builds work on the modified part of the project graph part only
- Project state restoration (partial) avoids repeating expensive tasks
like code generation
- etc...

More details available:
https://maven.apache.org/extensions/maven-build-cache-extension/

You can look at the configuration to use it:
https://maven.apache.org/extensions/maven-build-cache-extension/getting-started.html


Release Notes - Maven Build Cache Extension - Version 1.2.0

** Bug
* [MBUILDCACHE-76] - pom project version change not detected
* [MBUILDCACHE-79] - MBUILDCACHE-67 broke the partial restore process
* [MBUILDCACHE-80] - Incremental builds with a higher goal than
the highest cached goal is rebuilding the full project from scratch
* [MBUILDCACHE-81] - Add an option to include project version as
part of the cache hash key
* [MBUILDCACHE-88] - Tests in failure when ran on jdk21

** New Feature
* [MBUILDCACHE-90] - Configuration option to make mandatory the
use of the clean phase in order to cache the build result
* [MBUILDCACHE-93] - Command line configuration to disable saving in cache

** Improvement
* [MBUILDCACHE-71] - buildinfo.xml should be stored after storing
the project's artifacts
* [MBUILDCACHE-86] - Bugfix and enhancements with the restoration
of outputs on disk

Enjoy,

-The Apache Maven team

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



[RESULT] [VOTE] Apache Maven Build cache extension 1.2.0

2024-05-12 Thread Olivier Lamy
Hi
The vote has passed with the following result:
+1 Romain, Kevin,  Slawomir, Tamas, Olivier

I will finish the release process.

Cheers
Olivier

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



[VOTE] Release Apache Maven Dependency Analyzer version 1.14.0

2024-05-12 Thread Slawomir Jaranowski
Hi,

We solved 10 issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20fixVersion%20%3D%2012353840%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-dependency-analyzer

Staging repo:
https://repository.apache.org/content/repositories/maven-2115/
https://repository.apache.org/content/repositories/maven-2115/org/apache/maven/shared/maven-dependency-analyzer/1.14.0/maven-dependency-analyzer-1.14.0-source-release.zip

Source release checksum(s):
maven-dependency-analyzer-1.14.0-source-release.zip - SHA-512 :
177624ae1f2cff0a05bd694a70f7e139f7cad79db63287644dfbf307cc5be09624202f2ff00f16125926a4614553065603eb61143f690bf38e347ff6b2d00282

Staging site:
https://maven.apache.org/shared-archives/maven-dependency-analyzer-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


Re: Sisu Plexus release?

2024-05-12 Thread Eclipse Management Office EMO
Dear all,
the Eclipse Sisu project has not been engaging in our regular EDP processes
regarding releases. Seeing that the project is overdue for a review, I've
scheduled the following:
https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/740
Please subscribe to the issue to stay up-to-date regarding the EMO feedback
that will be provided in the upcoming days.
Kind regards,
Maria Teresa Delgado

On Wed, May 8, 2024 at 1:58 AM Christoph Läubrich 
wrote:

> Hi Tamás,
>
> According to [1] there is no planned release, I also see now milestones
> [2] or something planned here [3], maybe it would help to just create a
> Github Milestone and assign issues/prs to it so people can see how
> far/close a possible release currently is?
>
> Beside that, everything is fine from my side, I just wanted to jump in
> and help in case there is a problem with the project unable to actually
> do a release, if the (sisu) mailinglist is not appropriate to ask
> questions maybe you want to enable github discussion we made some good
> experience with that in the eclipse-platform and related projects.
>
> best
> Christoph
>
> [1] https://projects.eclipse.org/projects/technology.sisu/governance
> [2] https://github.com/eclipse/sisu.plexus/milestones
> [3] https://github.com/eclipse/sisu.plexus/releases
>
>
> Am 08.05.24 um 09:04 schrieb Tamás Cservenák:
> > Howdy,
> >
> > Olivier, I find this quite interesting, that according to you doing an
> > Eclipse release (even M one) is "just push a few buttons and run
> > something for a minute".
> > On the other hand, on Slack you educate Christoph about the "Apache way".
> > Please calm down and remain respectful.
> >
> > Your PR [1] has been reviewed by Sisu project lead (Stuart McCulloch) and
> > is merged. All is fine.
> >
> > The problem is in the "release must happen RIGHT NOW" stance of yours
> (for
> > whatever reason).
> > No Sisu committer will or can throw away everything they currently do (or
> > planned to do), just to make Sisu release happen, as you ask for it.
> > We are doing our best, and release for sure will happen soonish, as there
> > are several merged, but also several ongoing changes to be done yet (see
> > open PRs).
> >
> > [1] https://github.com/eclipse/sisu.plexus/pull/52
> >
> > On Wed, May 8, 2024 at 7:55 AM Christoph Läubrich 
> > wrote:
> >
> >> Hi Olivier,
> >>
> >> I'm not 100% sure about the sisu[1] problem at Eclipse BUT usually there
> >> is no need for a vote or similar but from tiem to time there is a
> >> release or progress review. If I look here
> >> https://projects.eclipse.org/projects/technology.sisu/who you have 100%
> >> commits over the last three month, so it would make sense that @Konrad
> >> Windszus or @cstamas simply start a committer vote to make you a
> >> committer of the project, after that I would (if Stuart is non
> >> responsive anymore) start a Project Lead election for either any of you,
> >> at that point you then can do what ever is required (even though any
> >> committer can technically perform a release or ask for a release review
> >> some actions might require a Project Lead approval e.g. pushing to
> >> central), if you have any questions regarding Eclipse process you can
> >> ask the Eclipse EMO (e...@eclipse.org added as CC).
> >>
> >> If you need any help I can offer to give some help from my experience in
> >> other Eclipse Projects, at a first glance looking at the release page[1]
> >> a release review seems overdue but I'm not an expert on this specific
> >> topic, it just wont hurt to schedule one just to be sure.
> >>
> >> HTH
> >> Christoph
> >>
> >> [1] https://projects.eclipse.org/projects/technology.sisu
> >> [2] https://projects.eclipse.org/projects/technology.sisu/governance
> >>
> >> Am 07.05.24 um 23:23 schrieb Olivier Lamy:
> >>> Hi,
> >>> Sure but as a long-term developer, I cannot release this plexus part
> >> anymore.
> >>> It used to be very easy to release this major part of the system (but
> >>> for some reason this has been moved somewhere else. not something to
> >>> discuss again, of course)
> >>> I have been asking sisu dev mailing list for a release, but no answer
> >> yet.
> >>> I have been looking at this project mailing list archive.
> >>> There is an email about a possible process
> >>> (https://www.eclipse.org/lists/sisu-dev/msg00116.html), but as far as
> >>> I can see, this 0.9.0.M2 release has been done without any voting
> >>> process etc.
> >>> So releasing looks to be only a matter of having a few minutes to run
> >>> m-release-p and publish. (being contributor to another Eclipse
> >>> project, I cannot see anything with vote mandatory).
> >>>
> >>> If it's easier we can certainly move this sisu plexus project back to
> >>> where it was few years ago under the groupId org.codehaus.plexus and
> >>> releasing will not be a problem for maven contributors.
> >>>
> >>> regards
> >>> Olivier
> >>>
> >>>
> >>> On Mon, 6 May 2024 at 20:16, Tamás Cservenák 
> >> wrote:
> 
>  Bt

maven-checkstyle-plugin doesn't support sarify type

2024-05-12 Thread コ ウ
Dear Developer of maven:

apache/maven-checkstyle-plugin  is only support xml and plain,
I wanna add sarif type support for this plugin.
If you satisfy my suggestion, can you create a JIRA Ticket for me or may I get 
a JIRA account and create a ticket for this suggestion.

exiahuang


Deprecate dependency:purge-local-repository, build-helper:remove-project-artifact

2024-05-12 Thread Slawomir Jaranowski
Hi

We have similar goals in two plugins:
 -
https://www.mojohaus.org/build-helper-maven-plugin/remove-project-artifact-mojo.html
 -
https://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html

By the way, using such goals is not recommended today with Maven 3 and so
much with Maven 4
Even more, when we remove one artifact from a local repository meta-data
information is not fixed.

We can achieve some of the requirements by using Enhanced LRM with Split
Local Repository - so installed artifacts can be separated for each build
and can be easily removed.
https://maven.apache.org/resolver/local-repository.html

We can use -Dmaven.repo.local to be sure that the build uses a clean one.

Also today there is no problem downloading artifacts from remote
repositories, so cleaning the whole remote repo from time to time can be a
good idea.

I'm interested in which scenarios those goals are used and who needs it.

For reference there was a discussion:
https://lists.apache.org/thread/nnqfjq4y8g56cdq38mo5mv9ov156797t

-- 
Sławomir Jaranowski