On Fri, 13 Oct 2023 at 05:52, Guillaume Nodet wrote:
>
> Le jeu. 12 oct. 2023 à 21:15, Tamás Cservenák a
> écrit :
>
> > Howdy,
> >
> > As part of the new Resolver major version, one of the goals is to introduce
> > HTTP/2 capable transports. And as always, naming...
> >
> > Current transport
+1
tested with various projects no issue found.
thanks!
On Mon, 2 Oct 2023 at 05:07, Tamás Cservenák wrote:
>
> Howdy,
>
> Note: This release completes the main goals of Maven 3.9.x lineage, among
> others moving to Java 8 and transition to latest Resolver 1.9.x features
> (new robust
+1
On Sat, 23 Sept 2023 at 04:29, Tamás Cservenák wrote:
>
> Howdy,
>
> Note: Maven Resolver 1.x lineage after this release is going into "bugfix
> only" maintenance mode (and will be branched off as maven-resolver-1.9.x),
> while master branch will become 2.x.
>
> We solved 6 issues:
>
+1
On Fri, 22 Sept 2023 at 05:53, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12353341
>
> There are still a couple of issues left in JIRA:
>
+1
On Fri, 8 Sept 2023 at 03:40, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12353576
>
> There are still a couple of issues left in JIRA:
>
Hi,
On Tue, 22 Aug 2023 at 17:36, Guillaume Nodet wrote:
>
> Hi everyone,
>
> I hope you guys have been able to rest a bit during the summer (for those
> that are back to work already)...
>
> I've pushed a few important PRs in the past months and I'd really like to
> get the discussion going
-1 Please revert this commit.
I'm the only one to express some concerns about such change.
Se conversations here
https://github.com/apache/maven-build-cache-extension/pull/88#issuecomment-1694496822
On Sat, 26 Aug 2023 at 23:33, wrote:
>
> This is an automated email from the ASF dual-hosted git
+1
On Sat, 19 Aug 2023 at 21:00, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353169
>
> There are still a couple of issues left in JIRA:
>
+1
On Fri, 4 Aug 2023 at 22:46, Tamás Cservenák wrote:
>
> Howdy,
>
> Context: This release focuses on "third party integrations" and provides a
> migration path for those who rely on deprecated `ServiceLocator`, which is
> about to be dropped in the near future (planned for 2.0.0). The main
+1
On Mon, 31 Jul 2023 at 20:29, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353369
>
> There are still a couple of issues left in JIRA:
>
really
> just an impediment these days. Classes today in resolver behave wildly
> different when used in Maven or when in SL.
>
> [1] https://issues.apache.org/jira/browse/MRESOLVER-157
>
>
> On Wed, Jul 26, 2023, 03:12 Olivier Lamy wrote:
>
> > Hi,
> > I re
Hi,
I really feel -1 regarding "Get rid of ServiceLocator in Resolver:
This will prevent a lot of consumers of resolver from upgrading.
As those consumers don't want to be forced to use all the guice stack
(or whatever or DI stack) and all the possible issues coming with this
in constrained
+1
On Mon, 24 Jul 2023 at 23:16, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12353342
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MINDEXER/issues
>
> Staging
+1
On Thu, 20 Jul 2023 at 20:16, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353358
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging
+1
On Fri, 16 Jun 2023 at 23:58, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 1 issue:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353340
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging
+1
On Wed, 14 Jun 2023 at 04:54, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12352951
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MSHADE/issues
>
> Staging
+1
On Mon, 12 Jun 2023 at 06:14, Michael Osipov wrote:
>
> Hi,
>
> we solved 17 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12350597
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MWAR/issues
>
> Staging
+1
On Mon, 12 Jun 2023 at 03:34, Michael Osipov wrote:
>
> Hi,
>
> we solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12353076
>
> There are still a couple of issues left in JIRA:
>
n always be worked around,
> as usual when you talk about upgrading to a more recent JDK, it's mostly
> improvements and standardization, it's never really blocking as people have
> long found workarounds if really needed.
+1
>
> Le ven. 9 juin 2023 à 10:58, Olivier Lamy a écrit :
this jdk discussion could be ended if someone could say we need jdk17
as a minimum because we really need this jdk feature.
Frankly, I don’t care about being jdk17 minimum and I'm fine with that
but what sort of feature do we really need?
nobody prevents users from using 17 or 21 but on the other
or
> attributes, like the priority, do not need to break the dependency tree
> of the built artifact!?!
> Otherwise one library using a newer maven version as its build tool will
> break any consumer utilizing an older maven version.
>
>
> Just my 2 cent
> MfG (Kind reg
Hi,
The vote has passed with the following result:
+1: Karl, Sylwester, Romain, Guillaume, Olivier
The vote passed, and I will finish the release process.
cheers
Olivier
-
To unsubscribe, e-mail:
sounds like a new feature (MNG-7804)
The only problem I can imagine is with tools/ide consuming the build
pom if they do not respect the xmlns and schemaLocation by validating
the pom with a hardcoded version of the schema.
But frankly let's consider this as a bug in the tool/ide doing so.
On
+1
On Tue, 6 Jun 2023 at 21:51, Olivier Lamy wrote:
>
> Hi,
> I'd like to release Maven Build Cache Extension 1.0.1
> We fixed 13 issues
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352469=Text=12324820=Create
>
> Staging repo: https://reposito
d plugins they are only 0.0.1
increment even with improvements so this is following a similar
pattern.
>
> Sylwester
>
> wt., 6 cze 2023, 13:51 użytkownik Olivier Lamy napisał:
>
> > Hi,
> > I'd like to release Maven Build Cache Extension 1.0.1
> > We fixed 13 issues
>
epo. At a quick glance, one looks
> like it perhaps should be closed unmerged, and the other needs to
> rebase onto master and be merged.
>
> On Tue, Jun 6, 2023 at 7:51 AM Olivier Lamy wrote:
> >
> > Hi,
> > I'd like to release Maven Build Cache Extension 1.0.1
&
Hi,
I'd like to release Maven Build Cache Extension 1.0.1
We fixed 13 issues
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352469=Text=12324820=Create
Staging repo: https://repository.apache.org/content/repositories/maven-1953/
source zip:
+1
On Sun, 4 Jun 2023 at 05:32, Michael Osipov wrote:
>
> Hi,
>
> we solved 15 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12353294
>
> There are still a couple of issues left in JIRA:
>
+1
On Sat, 3 Jun 2023 at 23:10, Michael Osipov wrote:
>
> Hi,
>
> we solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12353297
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
> Staging repo:
+1
On Wed, 31 May 2023 at 07:35, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
Perso I do not have any issue using 17.
By curiosity, I wonder what sort of 17 (or 9+) features we really want/need?
Pattern matching for switch?
record (so we can get rid of Modello but record will be not compatible
with previous standard beans).
On Fri, 2 Jun 2023 at 09:17, David Jencks
Hi,
I'd like to release the build cache extension in the coming days.
If someone has something to merge or fix please let me know/
cheers
Olivier
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
On Tue, 30 May 2023 at 01:44, Hervé Boutemy wrote:
>
> Le lundi 29 mai 2023, 13:50:58 CEST Karl Heinz Marbaise a écrit :
> > To fulfill the formalism (also have documented the decision here on the
> > ML) we should start simply a VOTE to get an in general decision about
> > moving to GH-issues to
or our Wiki, where we already organized equivalent
> > updates in the past [3]
> >
> > on using GH discussions, I suppose this should be an independent next
> > discussion
> >
> >
> > [1] https://github.com/apache/maven-build-cache-extension
> >
&
;> clear practices on release and release notes could also be worked
> > >> there [2]
> > >>
> > >> we'll need to write down what practical steps such a migration requires
> > >> => probably a good fit for our Wiki, where we already organized
> &
On Sun, 28 May 2023 at 04:53, Michael Osipov wrote:
>
> Am 2023-05-27 um 12:10 schrieb Tamás Cservenák:
> > Howdy,
> >
> > I do agree with Lukasz here...but
> >
> > In general, my intention with bringing up this on Slack was motivated by
> > following reasons:
> > - we do have ML (signup needed),
Hi,
This has been already discussed in the past.
But due to recent changes in ASF Jira infrastructure (limitation of
Jira users, validation of account creation).
Maybe we could reconsider moving from Jira to GH issues and why not
simplify the workflow as well.
I imagine not having to create an
Can't we store the text warnings in a file target/mvn-warning.txt
(whatever the name is)
Then per default a single warning line telling the user there will be
potential issues with this build in maven 4.x (more details look at
target/mvn-warning.txt) and telling him the flags to have more details
+1
On Thu, 18 May 2023 at 07:41, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924=12346658
>
> There are still a couple of issues left in JIRA:
>
+1
On Tue, 16 May 2023 at 04:55, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12353247
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/SCM/issues
>
> Staging
Yes I tend to agree the user experience is really confusing currently.
Just use mvn archetype:generate with the default project and warnings
are generated.
[WARNING] Plugin validation issues were detected in 2 plugin(s)
[WARNING] * org.apache.maven.plugins:maven-site-plugin:3.12.1
[WARNING] *
+1
On Mon, 8 May 2023 at 20:40, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 12 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352958
>
> There are still a couple of issues left in JIRA:
>
+1
On Sat, 6 May 2023 at 07:31, Michael Osipov wrote:
>
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12351273
>
> There are still a couple of issues left in JIRA:
>
+1
On Wed, 3 May 2023 at 11:40, Hervé Boutemy wrote:
>
> Hi,
>
> We solved N issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12350161=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1935
>
+1
On Tue, 2 May 2023 at 18:42, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 4 issues (out of that 1 bug):
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353177
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
+1
On Fri, 28 Apr 2023 at 06:03, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 20 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12350135
>
> There are still a couple of issues left in JIRA:
>
Hi
Thanks for reporting.
The issue has been resolved within 3/4 hours.
cheers
--
Olivier
On Fri, 21 Apr 2023 at 16:00, Robert Cauble wrote:
>
> -- Forwarded message -
> From: Robert Cauble
> Date: Wed, Apr 19, 2023 at 8:00 PM
> Subject: maven2 down?
> To:
>
>
> Hi,
>
>
Hi,
the current history (https://maven.apache.org/docs/history.html) page
can be confusing and let users think we are still supporting old core
version down to 3.2.5 (not sure someone will release 3.2.6 or 3.6.4
:))
see PR https://github.com/apache/maven-site/pull/410
if there are no issues, I
+1
On Sat, 15 Apr 2023 at 22:04, Michael Osipov wrote:
>
> Hi,
>
> IMPORTANT: Requires Doxia Sitetools 2.0.0-M8 and Maven Reporting Impl
> 4.0.0-M7 vote/staging repo!
>
> we solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353122
>
> There are still
+1
On Sat, 15 Apr 2023 at 21:26, Michael Osipov wrote:
>
> Hi,
>
> we solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12353110
>
> There are still a couple of issues left in JIRA:
>
+1
On Sun, 16 Apr 2023 at 02:03, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12335470
>
> There are no issues left in JIRA:
>
LGTM
It should be linked to core version support.
Might need some update of https://maven.apache.org/docs/history.html
maybe we should write some policy such we support only last version of
3 last main branches (e,g reached GA):
- 3.6.x
- 3.8.x
- 3.9.x
then when 4.0.x reach GA we can drop 3.6.x
+1
On Mon, 27 Mar 2023 at 03:51, Michael Osipov wrote:
>
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317920=12349526
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MSCMPUB/issues
>
> Staging
+1
On Thu, 23 Mar 2023 at 20:21, Guillaume Nodet wrote:
>
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m6/
>
> This release provides distributions based on Maven 3.9.1 and 4.0.0-alpha-4
> releases.
> The release notes are available at :
>
>
NOT deprecated
> - javax.inject namespace is NOT deprecated (unless you live in Jakarta EE
> space and are pulled by community/gravity)
>
> Thanks
> T
>
> On Wed, Mar 22, 2023 at 1:43 AM Olivier Lamy wrote:
>
> > The issue with the title `Drop plexus legacy` doesn't
+1
On Wed, 22 Mar 2023 at 00:09, Sylwester Lachiewicz
wrote:
>
> +1
>
> wt., 21 mar 2023 o 00:23 Slawomir Jaranowski
> napisał(a):
>
> > +1
> >
> > pon., 20 mar 2023 o 09:03 Michael Osipov napisał(a):
> >
> > > Hi,
> > >
> > > IMPORTANT: Requires Doxia/Doxia Sitetools 2.0.0-M6, Maven Reporting
+1
On Wed, 22 Mar 2023 at 00:09, Sylwester Lachiewicz
wrote:
>
> +1
>
> wt., 21 mar 2023 o 00:01 Michael Osipov napisał(a):
>
> > Am 2023-03-20 um 23:20 schrieb Slawomir Jaranowski:
> > > +1
> > >
> > > Standard Maven team is overridden in this project
> > >
> >
The issue with the title `Drop plexus legacy` doesn't look to have a
correct title.
The code is moving to use javax.inject namespace.
As far I can see this package is deprecated and now replaced with
jakarta.inject.
So it looks like moving to something else which is already deprecated.
maybe find
+1
On Mon, 20 Mar 2023 at 06:56, Michael Osipov wrote:
>
> Hi,
>
> IMPORTANT: Requires Doxia/Doxia Sitetools 2.0.0-M6 and Maven Reporting
> API/Impl 4.0.0-M5 vote/staging repo!
>
> we solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353022
>
> There
+1
On Mon, 20 Mar 2023 at 04:00, Michael Osipov wrote:
>
> Hi,
>
> IMPORTANT: Requires Doxia 2.0.0-M6 and Maven Reporting API 4.0.0-M5
> vote/staging repo!
>
> we solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12352876
>
> There are still a couple of
page here mentioned @Required what is it? maybe worth to add full package name.
https://maven.apache.org/shared-archives/maven-filtering-LATEST/usage.html
On Tue, 21 Mar 2023 at 21:03, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 6 issues:
>
+1
On Mon, 20 Mar 2023 at 2:46 am, Michael Osipov wrote:
> Hi,
>
> IMPORTANT: Requires Doxia 2.0.0-M6 vote/staging repo!
>
> we solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353021
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Mon, 20 Mar 2023 at 2:40 am, Michael Osipov wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230=12352878
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Thu, 16 Mar 2023 at 03:14, Guillaume Nodet wrote:
>
> Hey
>
> We solved 26 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352862=12316922
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-1890
>
> Dev dist directory:
>
+1
On Wed, 15 Mar 2023 at 8:14 pm, Tamás Cservenák wrote:
> Howdy,
>
> We solved 29 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352872
>
> There are still couple of issues left in JIRA:
>
>
+1
On Sat, 11 Mar 2023 at 19:09, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12352998
>
> There are still a couple of issues left in JIRA:
>
not sure how useful this feature is...
I would say just drop it...
quick search on github cannot find usage of it...
https://github.com/search?q=%3CrunOnlyAtExecutionRoot%3E+language%3A%22Maven+POM%22=code=Maven+POM
On Fri, 10 Mar 2023 at 00:44, Tamás Cservenák wrote:
>
> Howdy,
>
> I would
yeah sounds good!
On Fri, 10 Mar 2023 at 05:52, Maarten Mulders wrote:
>
> On 09/03/2023 13:32, Gary Gregory wrote:
> > Yes please, I get a raised eyebrow when a surefire and failsafe M version
> > is reviewed in a PR...
> >
> > Gary
>
> Same here. It's hard to explain that latest Surefire is
+1
On Thu, 9 Mar 2023 at 01:12, Michael Osipov wrote:
>
> Hi,
>
> We solved 17 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352869
>
> There are still hundreds of issues left in JIRA:
>
+1
On Wed, 8 Mar 2023 at 18:46, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 4 (1 bug + 3 improvements, all transport-http related) issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12352980
>
> There are still some issues in JIRA:
>
+1
On Mon, 6 Mar 2023 at 05:16, Michael Osipov wrote:
>
> Hi,
>
> We solved 1 issue:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322=12352975
>
> There are still a couple of issues left in JIRA:
>
+1
On Fri, 3 Mar 2023 at 7:52 pm, Tamás Cservenák wrote:
> Howdy,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12352957
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging
+1
On Mon, 20 Feb 2023 at 19:45, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 9 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12352753
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging
le especially without beta or alpha first
Furthermore my question concern a more general policy about what versions
do we support.
> Sylwester
>
> niedz., 19 lut 2023, 12:21 użytkownik Olivier Lamy
> napisał:
>
> > On Sun, 19 Feb 2023 at 9:12 pm, Sylwester Lachiewicz <
Maven 3.0 is EOL.
>
> https://maven.apache.org/docs/history.html
But not 3.2.5 3.3.3 etc…
What should we marked EOL as well?
Everything up to 3.8.6?
<https://maven.apache.org/docs/history.html>
>
>
> br
>
> Sylwester
>
> niedz., 19 lut 2023 o 12:04 Olivier Lamy
king…
Do we really think we can consider 3.9.0 as really stable today?
>
> On the history page we have only information that Maven 3.0 is EOL.
>
> https://maven.apache.org/docs/history.html
>
>
> br
>
> Sylwester
>
> niedz., 19 lut 2023 o 12:04 Olivier Lam
st what do we mean by “support”?
>
> Sylwester
>
> niedz., 19 lut 2023, 11:49 użytkownik Olivier Lamy
> napisał:
>
> > Typically this issue is a problem on what core version do we support..
> > https://issues.apache.org/jira/browse/MENFORCER-468
> >
> > The n
Typically this issue is a problem on what core version do we support..
https://issues.apache.org/jira/browse/MENFORCER-468
The new code is not working with 3.8.x
On Sun, 19 Feb 2023 at 1:58 pm, Olivier Lamy wrote:
> This change means we do not have any more gha running with anything
>
This change means we do not have any more gha running with anything
else than 3.9.0
can I understand this as an implicit we do not support anything <3.9.0?
I can't find any documentation on the website related to the
version(s) we support EOL etc...
Should we have some documentation to make this
sorry for the noise! Just to confirm the problem was in front of the laptop!!
On Wed, 15 Feb 2023 at 22:11, Olivier Lamy wrote:
>
> Sounds definitely possible :)
> I will tomorrow
>
> On Wed, 15 Feb 2023 at 10:03 pm, Tamás Cservenák wrote:
>>
>> I don't see that IT or
.0 && find maven-compiler-plugin -name
> > "*MCOMPILER-517*"
> >
> > It does not return anything.
> >
> > I am not sure where is it coming from in your case.
> >
> >
> > Petr
> >
> > --- Original Message ---
> > O
et)?
>
> Thanks,
> Petr
>
> --- Original Message ---
> On Wednesday, February 15th, 2023 at 12:18, Olivier Lamy
> wrote:
>
>
> >
> >
> > +1
> > Any idea why building from the tag I got this issue:
> > https://gist.github.com/olamy/4c5
+1
Any idea why building from the tag I got this issue:
https://gist.github.com/olamy/4c5ef44755f2d99f96c533de1121dce1
whereas building from the source.zip it's fine?
On Tue, 14 Feb 2023 at 18:51, Guillaume Nodet wrote:
>
> Hi,
> I'd like to release Apache Maven Compiler Plugin 3.11.0
>
> 7
+1
On Tue, 14 Feb 2023 at 09:14, Slawomir Jaranowski
wrote:
>
> +1
>
> niedz., 12 lut 2023 o 19:50 Michael Osipov napisał(a):
>
> > IMPORTANT: Requires Maven Site Plugin 4.0.0-M5 vote/staging repo!
> >
> > Hi,
> >
> > We solved 5 issues:
> >
> >
Hi
The vote has passed with the following result
+1 Michael, Romain, Karl, Tamas, Sylwester, Delany, Slawomir, Olivier
I will finish the release process.
cheers
Olivier
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
+1
On Mon, 13 Feb 2023 at 05:42, Michael Osipov wrote:
>
> Hi,
>
> we solved 9 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12352645
>
> There are still a couple of issues left in JIRA:
>
On Sat, 11 Feb 2023 at 20:50, Michael Osipov wrote:
>
> Am 2023-02-10 um 10:21 schrieb Olivier Lamy:
> > Hi,
> > I'd like to release Apache Maven Surefire 3.0.0-M9
> > We fixed 4 issues.
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927
Hi,
I'd like to release Apache Maven Surefire 3.0.0-M9
We fixed 4 issues.
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12352730
Staging repo: https://repository.apache.org/content/repositories/maven-1867/
Staging site:
+1
But https://issues.apache.org/jira/browse/MDEPLOY-206 should not be
part of the release notes as it doesn't work yet so it's really
confusing/
On Mon, 6 Feb 2023 at 22:52, Tamás Cservenák wrote:
>
> Howdy,
>
> We fixed several issues:
>
+1
On Sat, 4 Feb 2023 at 19:06, Michael Osipov wrote:
>
> Guys, please vote.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
+1
On Sat, 4 Feb 2023 at 19:12, Michael Osipov wrote:
>
> Hi,
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322=12351555
>
> There are still a couple of issues left in JIRA:
>
+1
On Thu, 2 Feb 2023 at 04:21, Michael Osipov wrote:
>
> Am 2023-01-31 um 19:00 schrieb Michael Osipov:
> > Hi,
> >
> > we solved 10 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12352573
> >
> > There are still a couple of issues left in JIRA:
> >
+1
On Tue, 27 Dec 2022 at 18:30, Herve Boutemy wrote:
>
> +1
>
> Reproducible Builds ok: reference built with JDK 8 on Windows
>
> thanks a lot
>
> Hervé
>
> On 2022/12/24 20:20:32 Michael Osipov wrote:
> > Hi,
> >
> > We solved 19 issues:
> >
+1
On Mon, 19 Dec 2022 at 07:57, Michael Osipov wrote:
>
> Hi,
>
> We solved 1 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12352696
>
> There are still a couple of issues left in JIRA:
>
+1. (but need to find projects not using flatten-maven-plugin as this
doesn't work with core 4.0.0-alpha-3)
On Fri, 16 Dec 2022 at 23:07, Guillaume Nodet wrote:
>
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0.0-m1/
>
> Note that this release is
Hi
The vote has passed with the following result.
+1: Sylwester, Guillaume, Michael, Hervé, Slawomir, Olivier.
I will finish the release process.
Thanks,
Olivier
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
yes good catch and sorry for that. As jdk19 is the goal of this
release, I did some testing etc,... and forgot to change back
JAVA_HOME before release.
But as we have a target m-compiler-p configured this shouldn’t be a problem.
>
> Regards,
>
> Hervé
>
> Le jeudi 15 décembre 2022,
Hi,
I'd like to release Maven Script Interpreter 1.4 and Maven Invoker Plugin 3.4.0
The main goal is to support jdk19.
Maven Script Interpreter 1.4 release notes
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352358=Text=12317922=Create
Staged repo:
+1 on the release
On Wed, 14 Dec 2022 at 10:13, Slawomir Jaranowski
wrote:
>
> Even more, I'm for adding 4.x to the download site together with mvnd ;-)
oh yes please!
>
> śr., 14 gru 2022 o 01:08 Slawomir Jaranowski
> napisał(a):
>
> > +1
> >
> > To do:
> > - release notes
> > - new
+1
On Mon, 12 Dec 2022 at 06:32, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 5 issues in ASF parent:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352620
>
> We solved 7 issues in Maven parent:
>
101 - 200 of 2864 matches
Mail list logo
