+1
On Thu, 21 Jul 2022 at 03:18, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12351652
>
> Changes since the last release:
>
> https://github.com/apache/maven-parent/compare/maven-parent-36...maven-
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220&version=12352095
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20resolution%20%3D%20Unresolved
Staging repo:
https://re
Am 2022-07-20 um 15:48 schrieb Tamás Cservenák:
Howdy,
The master branch is ready for 3.4.2
https://github.com/apache/maven-assembly-plugin
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20fixVersion%20%3D%203.4.2
Anyone?
I will roll for you!
---
+1
śr., 20 lip 2022 o 22:32 Tamás Cservenák napisał(a):
>
> +1
>
> On Wed, Jul 20, 2022, 22:10 Michael Osipov wrote:
>
> > Hi,
> >
> > We solved 5 issues:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352050
> >
> > There are still a couple of issues
+1
On Wed, Jul 20, 2022, 22:10 Michael Osipov wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352050
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MS
Am 2022-07-20 um 22:10 schrieb Michael Osipov:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352050
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolutio
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352050
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%20m
+1
śr., 20 lip 2022, 19:33 użytkownik Karl Heinz Marbaise
napisał:
> Hi,
>
> +1 from me.
>
> Kind regards
> Karl Heinz Marbaise
> On 20.07.22 19:17, Slawomir Jaranowski wrote:
> > Hi,
> >
> > We solved 9 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&vers
On 19. 07. 22 16:26, Tamás Cservenák wrote:
> Howdy,
>
> We fixed one regression in install-file Mojo
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINSTALL%20AND%20fixVersion%20%3D%203.0.1
>
> Staged repository:
> https://repository.apache.org/content/repositories/maven-1784
>
>
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 20.07.22 19:17, Slawomir Jaranowski wrote:
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12351652
Changes since the last release:
https://github.com/apache/maven-parent/compare/mave
+1
On Wed, Jul 20, 2022 at 7:18 PM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12351652
>
> Changes since the last release:
>
> https://github.com/apache/maven-parent/compare/maven-parent-36...mave
Am 2022-07-20 um 19:17 schrieb Slawomir Jaranowski:
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12351652
Changes since the last release:
https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37
Staging repo:
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12351652
Changes since the last release:
https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37
Staging repo:
https://repository.apache.org/content/repositories/mav
Hello Björn,
Thanks for reaching out. I think your observations a right, making this
_really_ an up-for-grabs issue.
Given that most Maven users only enable debug logging for
troubleshooting purposes, they will usually not see it. So we would
indeed need a small code change to make the infor
Yes, I agree with Romain (and also many others that have the same
concerns), expecting that the behavior of testing with one JDK that
targets a lower JDK will "just works" is naive.
There are differences at bytecode level, just compile a class with
JDK17 --release 11 and the same class with JDK11
Was more due to tests failling but there is no guarantee there is no
difference in the bytecode on one side and the most important IMHO is the
fact the run behavior can be different so at the end of the day you cant
assume that because your build with java17 -release 8 worked that it will
run on yo
Le mer. 20 juil. 2022 à 15:39, Karl Heinz Marbaise a
écrit :
> Hi,
>
> On 20.07.22 13:04, Romain Manni-Bucau wrote:
> > > There is no need to use toolchain to run your build with JDK17 and
> > > create code for Java 8... you can use --release 8
> > > (8)...
> > >
> > > No toolchain needed.
>
Howdy,
The master branch is ready for 3.4.2
https://github.com/apache/maven-assembly-plugin
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20fixVersion%20%3D%203.4.2
Anyone?
Thanks
Tamas
Hi,
On 20.07.22 13:04, Romain Manni-Bucau wrote:
> There is no need to use toolchain to run your build with JDK17 and
> create code for Java 8... you can use --release 8
> (8)...
>
> No toolchain needed.
So you run tests with java 17? This is not what you want if your prod is
in java 8, yo
Created https://github.com/apache/maven-remote-resources-plugin/pull/8
On Wed, Jul 20, 2022 at 1:56 PM Tamás Cservenák wrote:
> Bah, that was me:
>
> https://github.com/apache/maven-remote-resources-plugin/commit/66b6074ef1715f1198fbee13bf8673a495f20319#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f902
Bah, that was me:
https://github.com/apache/maven-remote-resources-plugin/commit/66b6074ef1715f1198fbee13bf8673a495f20319#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L73
T
On Wed, Jul 20, 2022 at 1:48 PM Piotr Żygieło
wrote:
> > Howdy,
> >
> > The Apache Maven team is p
> Howdy,
>
> The Apache Maven team is pleased to announce the release of
> Maven Remote Resources Plugin 3.0.0.
>
Strange, but the site seems to have some filtering broken:
https://maven.apache.org/plugins/maven-remote-resources-plugin/usage.html
says:
> To handle filtering this version of Maven
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Shared Maven Common Artifact Filters 3.3.1 component.
Site: https://maven.apache.org/shared/maven-common-artifact-filters/
Release Notes - Maven Shared Components - Version
maven-common-artifact-filters-3.3.1
** Bug
* [
> There is no need to use toolchain to run your build with JDK17 and
> create code for Java 8... you can use --release 8
> (8)...
>
> No toolchain needed.
So you run tests with java 17? This is not what you want if your prod is in
java 8, you can still get surprises so you need toolchain in your b
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Remote Resources Plugin 3.0.0.
Plugin is Java7 level and compatible with Maven 3.2.5+
Site: https://maven.apache.org/plugins/maven-remote-resources-plugin/
Release Notes - Maven Remote Resources Plugin - Version 3.0.0
** I
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Rar Plugin 3.0.0.
Plugin is Java7 level and compatible with Maven 3.3.9+
Site: https://maven.apache.org/plugins/maven-rar-plugin/
Release Notes - Maven RAR Plugin - Version 3.0.0
** Bug
* [MRAR-41] - Update plexus-inte
Howdy,
The vote has passed with the following result:
+1 : Michael, Sylwester, Karl-Heinz, Guillaume
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The vote has passed with the following result:
+1 : Michael, Sylwester, Karl-Heinz, Guillaume
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The vote has passed with the following result:
+1 : Michael, Sylwester, Karl-Heinz
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
> >
> > Fair enough, they can remain just for backward compatibility, but even
> > if javac does not remove it, it doesn't mean that are useful having
> > --release, and there are probably more for backward compatibility than
> > anything else, again, this is just to drop legacy baggage.
>
> That's
Hi,
On 20.07.22 10:32, Romain Manni-Bucau wrote:
Hi,
Think we have multiple topics there:
1. Which version to *build*, using jdk17 would enable to have some
advanced usage of the JDK and nice build features (IO and concurrent API
are enhanced and can benefit a build when using custom tasks but
I have a plexus component annotated with
@Component(role = MyService.class, instantiationStrategy =
Strategies.PER_LOOKUP)
public class MyService {
}
Can I somehow find out the object (or at least realm or class) where it
was created for?
eg with MyMojo {
@Component
MyService servic
Hi,
Think we have multiple topics there:
1. Which version to *build*, using jdk17 would enable to have some advanced
usage of the JDK and nice build features (IO and concurrent API are
enhanced and can benefit a build when using custom tasks but AFAIK we don't
do it much) but this has no link to
33 matches
Mail list logo
