RE: Re: release of surefire M7

[Clément Gaboriau-Couanau]

Hi

Have you planned a vote to release the M7 version during this week?

Regards,

Clément

On 2022/05/26 07:37:16 Olivier Lamy wrote:
> On Thu, 26 May 2022 at 16:27, Hervé BOUTEMY  wrote:
> 
> > +1 to not have this content in this plugin's index
> > but remove or move to a separate page?
> 
> 
> > and reading the current content, this page would be better named "history"
> > than "roadmap"
> >
> 
> yup this will be a move to an history page
> 
> 
> >
> > Le mercredi 25 mai 2022, 09:50:17 CEST Slawomir Jaranowski a écrit :
> > > +1 for removing road map
> > >
> > > IMHO in a simple way an open source project should always be ready for
> > the
> > > next release, even if we have a few fixes, like now.
> > >
> > > We have a jira for such tasks.
> > >
> > > śr., 25 maj 2022 o 09:37 Olivier Lamy  napisał(a):
> > > > On Wed, 25 May 2022 at 16:55, Slawomir Jaranowski <
> > s.jaranow...@gmail.com>
> > > >
> > > > wrote:
> > > > > Hi,
> > > > >
> > > > > Good idea.
> > > > >
> > > > > Please also update "road map" [1] before release to be consistent ...
> > > >
> > > > with
> > > >
> > > > > released content :-)
> > > > >
> > > > > https://maven.apache.org/surefire/maven-surefire-plugin/
> > > >
> > > > you mean removing it? :)
> > > > TBH I don't think we need that.. I would expect to get documentation on
> > > > the
> > > > plugins here rather than this.
> > > >
> > > > > śr., 25 maj 2022 o 01:54 Olivier Lamy  napisał(a):
> > > > > > Hi
> > > > > > I'd like to release M7 because of this blocker issue
> > > > > > https://issues.apache.org/jira/browse/SUREFIRE-2057
> > > > > >
> > > > > > I will start release process by the end of this week and move
> > current
> > > >
> > > > non
> > > >
> > > > > > fixed issue to M8
> > > > > >
> > > > > > cheers
> > > > > > Olivier
> > > > >
> > > > > --
> > > > > Sławomir Jaranowski
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>


Clément GABORIAU COUANAU

[VOTE] Release Apache Maven PMD Plugin version 3.17.0

[Andreas Dangel]

Hi,

We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351350=Text=12317621

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPMD%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1756/
https://repository.apache.org/content/repositories/maven-1756/org/apache/maven/plugins/maven-pmd-plugin/3.17.0/maven-pmd-plugin-3.17.0-source-release.zip

Source release checksum(s):
maven-pmd-plugin-3.17.0-source-release.zip sha512:
b95a6f1b54332747c09af93ddbda6ef3d49745bb5a2a31fadf43221549919c7eb7a20541234eb9f8f02b1dfd75b9b94305322097194d98cb7e837328493673a3

Staging site:
https://maven.apache.org/plugins-archives/maven-pmd-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


Regards,
Andreas


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

[VOTE] Release Maven Indexer 6.2.1

[Tamás Cservenák]

Howdy,

We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12351791

There are still some issues left in JIRA:
https://issues.apache.org/jira/projects/MINDEXER/

Staging repository:
https://repository.apache.org/content/repositories/maven-1755

Source SHA512 checksum:
8db83401137d06b83637f656393a65ecccae81d9878677ed7401fd41493c468fe6665f32cfa746ff8a9bca4b33b245894b8f6ed39f26b729da8ab9c7c0ed70a4

Staged site:
https://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Re: Releasing a Parent POM procedure - improvement

[Olivier Lamy]

On Tue, 31 May 2022 at 18:22, Slawomir Jaranowski 
wrote:

> wt., 31 maj 2022 o 09:58 Olivier Lamy  napisał(a):
>
> > On Tue, 31 May 2022 at 02:22, Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > On page Releasing A Parent POM [1] we have Call the vote template with
> > > info:
> > >
> > > "In the vote, instead of providing links to JIRA, the parent POMs
> should
> > > include a link to the Git changes since the last release:"
> > >
> > > It can be understood by someone that we don't need to create release
> > notes
> > > in jira for parent poms.
> > > For historical releases we did release notes in jira, we also sent
> > release
> > > notes in announcements about poms release.
> > >
> > > So to be consistent we can:
> > >
> > > 1. Change template with information that  links to the Git changes is
> > > additional to the jira link.
> >
> > or
> > > 2. Put clear confirm that we don't need jira release notes and don't
> > track
> > > issues in jira for parents poms ...
> > >
> >
> > +1 (maybe github release notes generated by release drafter? (well it
> works
> > if everything has been done via PR otherwise need some manual entries to
> be
> > added) )
>
>
> To be clear GitHub releases notes generated by release drafter are
> additionally to jira - not instead of. Right?
>


your 2. says "we do not need jira release notes"
as you mention Jita I'm lost now :)
frankly not sure we need jira etc.. for parent poms especially plugins or
shared etc...
Those parent poms are very internal and most of the time the activity is
merging dependabot PRs.
so just having PRs which automatically generate a release note and voila.


>
>
> >
> >
> >
> > > Please vote for 1 or 2 ... or provide another idea :-)
> >
> >
> > > [1]
> > >
> > >
> >
> https://maven.apache.org/developers/release/parent-pom-release.html#call-the-vote
> > >
> > > --
> > > Sławomir Jaranowski
> > >
> >
>
>
> --
> Sławomir Jaranowski
>

Re: Releasing a Parent POM procedure - improvement

[Slawomir Jaranowski]

wt., 31 maj 2022 o 09:58 Olivier Lamy  napisał(a):

> On Tue, 31 May 2022 at 02:22, Slawomir Jaranowski 
> wrote:
>
> > Hi,
> >
> > On page Releasing A Parent POM [1] we have Call the vote template with
> > info:
> >
> > "In the vote, instead of providing links to JIRA, the parent POMs should
> > include a link to the Git changes since the last release:"
> >
> > It can be understood by someone that we don't need to create release
> notes
> > in jira for parent poms.
> > For historical releases we did release notes in jira, we also sent
> release
> > notes in announcements about poms release.
> >
> > So to be consistent we can:
> >
> > 1. Change template with information that  links to the Git changes is
> > additional to the jira link.
>
> or
> > 2. Put clear confirm that we don't need jira release notes and don't
> track
> > issues in jira for parents poms ...
> >
>
> +1 (maybe github release notes generated by release drafter? (well it works
> if everything has been done via PR otherwise need some manual entries to be
> added) )


To be clear GitHub releases notes generated by release drafter are
additionally to jira - not instead of. Right?


>
>
>
> > Please vote for 1 or 2 ... or provide another idea :-)
>
>
> > [1]
> >
> >
> https://maven.apache.org/developers/release/parent-pom-release.html#call-the-vote
> >
> > --
> > Sławomir Jaranowski
> >
>


-- 
Sławomir Jaranowski

Re: Releasing a Parent POM procedure - improvement

[Olivier Lamy]

On Tue, 31 May 2022 at 02:22, Slawomir Jaranowski 
wrote:

> Hi,
>
> On page Releasing A Parent POM [1] we have Call the vote template with
> info:
>
> "In the vote, instead of providing links to JIRA, the parent POMs should
> include a link to the Git changes since the last release:"
>
> It can be understood by someone that we don't need to create release notes
> in jira for parent poms.
> For historical releases we did release notes in jira, we also sent release
> notes in announcements about poms release.
>
> So to be consistent we can:
>
> 1. Change template with information that  links to the Git changes is
> additional to the jira link.

or
> 2. Put clear confirm that we don't need jira release notes and don't track
> issues in jira for parents poms ...
>

+1 (maybe github release notes generated by release drafter? (well it works
if everything has been done via PR otherwise need some manual entries to be
added) )


>
> Please vote for 1 or 2 ... or provide another idea :-)


> [1]
>
> https://maven.apache.org/developers/release/parent-pom-release.html#call-the-vote
>
> --
> Sławomir Jaranowski
>

Re: Upcoming Maven 3.8.6

[Olivier Lamy]

snapshots are always here as it's done automatically by Jenkins after each
push to master, 3.9.x or 3.8.x


On Tue, 31 May 2022 at 17:24, Hervé BOUTEMY  wrote:

> good idea: done
>
> Regards,
>
> Hervé
>
> Le mardi 31 mai 2022, 08:18:50 CEST Dan Tran a écrit :
> > Hi,
> >
> > possible to have 3.8.6-SNAPSHOT upload to https://repository.apache.org
> ?
> >
> > Thanks
> >
> > -D
> >
> > On Mon, May 30, 2022 at 12:35 PM Michael Osipov 
> wrote:
> > > Folks,
> > >
> > > Maven 3.8.6 is complete, no more open issues. Thank you gnodet@!
> > >
> > > I'll leave people this business week to work/discuss on potential
> issues
> > > for 3.8.x. My plan is to start the release around 2022-06-06.
> > >
> > > Michael
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven plugins - injecting Maven components

[Slawomir Jaranowski]

Hi Romain

Did you find  - discussions and reported issues?




pt., 20 maj 2022 o 23:18 Romain Manni-Bucau 
napisał(a):

> Le ven. 20 mai 2022 à 22:21, Slawomir Jaranowski 
> a
> écrit :
>
> > I was convinced that plexus is deprecated [1] [2], but  you propose that
> > users writing plugins outside the Maven core team should use it.
> > Maybe I missed something?
> >
>
> There are multiple discussions - can try to find them back next week if
> needed - explaning why using JSR does not comply to maven pluggable
> design and how an antipattern and a promise of issues it is.
> So until we have a clean API we have to stay in the status-quo which is
> plexus AFAIK today.
>
>
> >
> > There is no information [3] that JSR303 should be used only in Maven core
> > plugins / components.
> >
>
> Let's add that then :).
>
>
> >
> > [1] https://codehaus-plexus.github.io/plexus-containers/index.html
> > [2]
> >
> >
> https://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/
> > [3] https://maven.apache.org/maven-jsr330.html
> >
> >
> > pt., 20 maj 2022 o 21:13 Romain Manni-Bucau 
> > napisał(a):
> >
> > > I'm not sure for shared, I always considered them as internals of maven
> > > projects and rarely saw them reused except a very few times but
> reasoning
> > > is the same whatever module we speak about: does it impact external
> > > consumer? If yes -> only org.apache.maven API or
> assimilated/assimilable
> > > (plexus is today I think), else we don't care and do what we like IMHO.
> > >
> > >
> > > Le ven. 20 mai 2022 à 21:01, Sylwester Lachiewicz <
> slachiew...@gmail.com
> > >
> > > a
> > > écrit :
> > >
> > > > And what about shared libraries?  they can be used by plugins or even
> > > > externally.
> > > > Sylwester
> > > >
> > > > pt., 20 maj 2022, 19:15 użytkownik Romain Manni-Bucau <
> > > > rmannibu...@gmail.com>
> > > > napisał:
> > > >
> > > > > It is quite simple:
> > > > >
> > > > > Maven plugin: maven API or plexus annotations are preferred
> > > > > Maven core: JSR 330 is out internal API for IoC lookups/injections
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau  |  Blog
> > > > >  | Old Blog
> > > > >  | Github <
> > > > > https://github.com/rmannibucau> |
> > > > > LinkedIn  | Book
> > > > > <
> > > > >
> > > >
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > > > >
> > > > >
> > > > >
> > > > > Le ven. 20 mai 2022 à 18:08, Slawomir Jaranowski <
> > > s.jaranow...@gmail.com
> > > > >
> > > > > a
> > > > > écrit :
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm a little confused - what should be conclusions from this
> > > > discussion?
> > > > > >
> > > > > > I asked about using JSR330 with maven components like
> MavenProject,
> > > > > > MavenSession ... in plugin Mojo code.
> > > > > > But I see discussion about using JSR330 at general in Maven
> plugins
> > > > > >
> > > > > > Currently we widely use  JSR330 in core Maven plugins as
> > replacement
> > > > for
> > > > > > plexus annotations.
> > > > > >
> > > > > > Can anybody else summarize it? ... Maybe I wrong understood this
> > > > > > discussion.
> > > > > >
> > > > > >
> > > > > > śr., 18 maj 2022 o 16:07 Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > > > > > napisał(a):
> > > > > >
> > > > > > > Le mer. 18 mai 2022 à 15:19, Stuart McCulloch <
> mccu...@gmail.com
> > >
> > > a
> > > > > > écrit
> > > > > > > :
> > > > > > >
> > > > > > > > On Wed, 18 May 2022 at 14:15, Romain Manni-Bucau <
> > > > > > rmannibu...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Le mer. 18 mai 2022 à 15:03, Stuart McCulloch <
> > > mccu...@gmail.com
> > > > >
> > > > > a
> > > > > > > > écrit
> > > > > > > > > :
> > > > > > > > >
> > > > > > > > > > I do wonder whether we're conflating the real issues of
> > > > exposing
> > > > > > the
> > > > > > > > CDI
> > > > > > > > > > API (for @Typed) with the much smaller JSR330 API
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Yes as soon as you have a different version needed by a
> > plugin
> > > > and
> > > > > > the
> > > > > > > > api
> > > > > > > > > exposed (parent first forced - and if not forced we dont
> know
> > > if
> > > > it
> > > > > > > > works).
> > > > > > > > >
> > > > > > > >
> > > > > > > > There's only ever been one version of the JSR 330 API because
> > > it's
> > > > so
> > > > > > > small
> > > > > > > > and complete (and I'd be surprised if the jakarta.inject API
> is
> > > any
> > > > > > > > different...)
> > > > > > > >
> > > > > > >
> > > > > > > We probably also thought javax.annotation would never get dead
> > > > > > annotations
> > > > > > > nor build time annotations and it just did so not sure I would
> > bet.
> > > > > > > Size is not much an issue too, actually new API are fine but
> > > > modifying
> > > > > > > 

Re: Upcoming Maven 3.8.6

[Hervé BOUTEMY]

good idea: done

Regards,

Hervé

Le mardi 31 mai 2022, 08:18:50 CEST Dan Tran a écrit :
> Hi,
> 
> possible to have 3.8.6-SNAPSHOT upload to https://repository.apache.org ?
> 
> Thanks
> 
> -D
> 
> On Mon, May 30, 2022 at 12:35 PM Michael Osipov  wrote:
> > Folks,
> > 
> > Maven 3.8.6 is complete, no more open issues. Thank you gnodet@!
> > 
> > I'll leave people this business week to work/discuss on potential issues
> > for 3.8.x. My plan is to start the release around 2022-06-06.
> > 
> > Michael
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org





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

Re: Upcoming Maven 3.8.6

[Dan Tran]

Hi,

possible to have 3.8.6-SNAPSHOT upload to https://repository.apache.org ?

Thanks

-D

On Mon, May 30, 2022 at 12:35 PM Michael Osipov  wrote:

> Folks,
>
> Maven 3.8.6 is complete, no more open issues. Thank you gnodet@!
>
> I'll leave people this business week to work/discuss on potential issues
> for 3.8.x. My plan is to start the release around 2022-06-06.
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>