date:20230124

JDK 20 Rampdown Phase 2 & JMX Heads-up

2023-01-24 Thread David Delabassee


Hi,

First off, on behalf of Oracle’s Java Team, I’d like to wish you a happy 
and prosperous new year!


In 2023, two Java releases will be made available: JDK 20 (March) &  JDK 
21 (September).


JDK 20 [1] has entered Rampdown Phase Two (RDP2) [2], its initial 
Release Candidate is planned for February 9. Given that and to be better 
prepared for the future, it makes sense to begin testing your project(s) 
using JDK 21 early-access (EA) builds. Your feedback allows us to 
evaluate and address issues you find while testing EA builds.


[1] https://jdk.java.net/20/
[2] https://mail.openjdk.org/pipermail/jdk-dev/2023-January/007308.html
[3] https://jdk.java.net/21/


## Heads-up - JDK 21: JMX Subject Delegation & Fine-grained Security 
Deprecation


JMX has some features that rely on Security Manager APIs which are 
deprecated for removal (see JEP 411 [4]). These features are "Subject 
Delegation" and "Fine-grained Security", which both seem to be generally 
unused, and would require significant investment to implement without 
touching the deprecated APIs. As a consequence, "Subject Delegation" is 
being proposed for deprecation in JDK 21 [5].


Fine-grained Security is also being considered for deprecation at the 
same time. This feature [6] has allowed configuration of a security 
policy to restrict or permit access to specific MBean actions. It is 
expected that this feature is generally unused, possibly because there 
is simply no demand for such detailed control, and that it is too 
complex to create and maintain the policies.


[4] https://openjdk.org/jeps/411
[5] https://bugs.openjdk.org/browse/JDK-8298966
[6] 
https://docs.oracle.com/en/java/javase/19/jmx/fine-grained-security-example.html



## JDK 20 Early-Access builds

The latest early-access builds of JDK 20 (builds 32) are available [7], 
and are provided under the GNU General Public License v2, with the 
Classpath Exception. The Release Notes are available here [8].


[7] https://openjdk.org/projects/jdk/20/
[8] https://jdk.java.net/20/release-notes

### JEPs integrated into JDK 20:

- JEP 429: Scoped Values (Incubator)
- JEP 432: Record Patterns (2nd Preview)
- JEP 433: Pattern Matching for switch (4th Preview)
- JEP 434: Foreign Function & Memory API (2nd Preview)
- JEP 436: Virtual Threads (2nd Preview)
- JEP 437: Structured Concurrency (2nd Incubator)

### Changes in recent JDK 20 builds that may be of interest:

- JDK-8298525: javadoc crashes with "UnsupportedOperationException: Not 
yet implemented" in SeeTaglet.inherit [Reported by Apache Ant]

- JDK-8298893: Rename option UsePolyIntrinsics to UsePoly1305Intrinsics
- JDK-8287411: Enhance DTLS Performance
- JDK-8293554: Enhanced DH Key Exchanges


## JDK 21 Early-Access builds

The latest early-access builds of JDK 21 (builds 6) are available [9], 
and are provided under the GNU General Public License v2, with the 
Classpath Exception. The related EA API Javadoc is also available [10].


[9] https://jdk.java.net/21/
[10] https://download.java.net/java/early_access/jdk21/docs/api/

### Changes in recent JDK 21 builds that may be of interest:

- JDK-8297295: Remove ThreadGroup.allowThreadSuspension
- JDK-8287411: Enhance DTLS performance
- JDK-8233269: Improve handling of JAVA_ARGS
- JDK-8297933: Compiler should only use verified interface types for 
optimization

- JDK-8298381: Improve handling of session tickets for multiple SSLContexts
- JDK-8299501: Usage of constructors of primitive wrapper classes should 
be avoided in java.util API docs
- JDK-8299475: Enhance SocketException by cause where it is missing in 
net and nio area
- JDK-8299544: Improve performance of CRC32C intrinsics (non-AVX-512) 
for small inputs

- JDK-8299576: Reimplement java.io.Bits using VarHandle access
- JDK-8278326: Socket close is not thread safe and other cleanup
- JDK-8299673: Simplify object pinning interactions with string 
deduplication



## JavaFX 20 & 21 Early-Access Builds

These are early-access builds of the JavaFX Runtime, built from 
openjdk/jfx [11]. Those EA builds are intended to allow JavaFX 
application developers to build and test their applications with JavaFX 
20 on JDK 20. The latest EA builds (JavaFX 20 EA b16 2023/1/14) are now 
available [12] and are provided under the GNU General Public License, 
version 2, with the Classpath Exception. Please note that initial JavaFX 
21 early-access builds (JavaFX 21 b1 2023/1/19) are now available [13] 
as well.

Feedback should be reported to the openjfx-dev mailing list [14].

[11] https://github.com/openjdk/jfx
[12] https://jdk.java.net/javafx20/
[13] https://jdk.java.net/javafx21/
[14] http://mail.openjdk.org/mailman/listinfo/openjfx-dev


## Topics of Interest:

- On Markdown in (Java) documentation comments
https://mail.openjdk.org/pipermail/javadoc-dev/2023-January/005563.html

- Lifetimes in the Foreign Function & Memory API
https://cr.openjdk.java.net/~mcimadamore/panama/why_lifetimes.html

- Java's Plans for 2023 - Inside Java

Re: Do we plan to support extensions with java 17?

2023-01-24 Thread Romain Manni-Bucau

Hmm, technically you can use most of guice without asm and replace its
visitors by reflection/meta read and proxying by build time generation in
the custom annot proc.

Not saying it is one liner but it would be what sounds more long term to
me...we can also drop guice for v4/v5 since we dont expose it strictly
speaking, would enable to clean up things and the stack inconsistency but
agree it is quite some work for less shirt term gain.

Le mar. 24 janv. 2023 à 20:31, Tamás Cservenák  a
écrit :

> Howdy,
>
> Plexus-shim is built on top of Sisu, and Sisu is built on top of Guice.
> Maven is tied to plexus-shim very much.
>
> Guice shades ASM as well (current version 5.1.0 has support for Java17:
> https://github.com/google/guice/wiki/Guice510 )
>
> Hence, our stack is pretty much tied to Guice. I hope Guice will be fast
> enough to support at least LTS Java versions as they come out, while we, at
> Sisu, will need to speed up the release process and "follow" Guice more
> closely... Currently there was a gap, Sisu lagged a bit but hopefully
> things will catch up soon.
>
> That's the best I can come up with right now.
>
> HTH
> Tamas
>
> On Tue, Jan 24, 2023 at 7:54 PM Romain Manni-Bucau 
> wrote:
>
> > Again: cause the PR which is not merged is already not sufficient for the
> > LTS of september. Asm version is a running forward game and technically
> we
> > don't need it _there_ so if we can make it effortless I think it could
> only
> > have a positive impact on the project. Concretely the 9.4 (the PR) does
> not
> > support the next LTS (21), see
> >
> >
> https://gitlab.ow2.org/asm/asm/-/blob/master/asm/src/main/java/org/objectweb/asm/Opcodes.java#L289
> > and compare to 9.4 release/branch for ex.
> >
> >
> > Le mar. 24 janv. 2023 à 19:01, Tamás Cservenák  a
> > écrit :
> >
> > > Howdy,
> > >
> > > Why again?
> > >
> > > There is ongoing effort (master is already updated), but also to raise
> > > whole Java level of Sisu, see
> > > https://github.com/eclipse/sisu.inject/pull/72
> > > Hopefully soon new sisu release will happen that will contain updated
> ASM
> > > and allow using Java11+ bytecode.
> > >
> > > Thanks
> > > T
> > >
> > >
> > > On Tue, Jan 24, 2023 at 6:58 PM Romain Manni-Bucau <
> > rmannibu...@gmail.com>
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > We are hit again by sisu asm, we cant write a component using sisu
> > Named
> > > > SPI if compiled with java 17 (since then it will be visited with a
> too
> > > old
> > > > asm - exception at the end), do we want to upgrade asm there, do we
> > want
> > > to
> > > > plan drop it - guess we can using the annot processor to collect more
> > > data?
> > > >
> > > >
> > > > Exception:
> > > >
> > > > java.lang.IllegalArgumentException
> > > > at
> org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:170)
> > > > at
> org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:153)
> > > > at
> org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:424)
> > > > at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:102)
> > > > at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:78)
> > > > at org.eclipse.sisu.space
> > > > .SpaceModule.scanForElements(SpaceModule.java:168)
> > > > at org.eclipse.sisu.space
> .SpaceModule.configure(SpaceModule.java:129)
> > > > at
> > > >
> > > >
> > >
> >
> org.eclipse.sisu.plexus.PlexusAnnotatedBeanModule.configure(PlexusAnnotatedBeanModule.java:102)
> > > > at
> > > >
> > > >
> > >
> >
> org.eclipse.sisu.plexus.PlexusBindingModule.configure(PlexusBindingModule.java:63)
> > > > at
> > > >
> > com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> > > > at com.google.inject.spi.Elements.getElements(Elements.java:108)
> > > > at com.google.inject.spi.Elements.getElements(Elements.java:101)
> > > > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:75)
> > > > at
> > > >
> > com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> > > > at com.google.inject.spi.Elements.getElements(Elements.java:108)
> > > > at
> > > >
> > > >
> > >
> >
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:160)
> > > > at
> > > >
> > > >
> > >
> >
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> > > > at com.google.inject.Guice.createInjector(Guice.java:87)
> > > > at com.google.inject.Guice.createInjector(Guice.java:69)
> > > > at com.google.inject.Guice.createInjector(Guice.java:59)
> > > > at
> > > >
> > > >
> > >
> >
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> > > > at
> > > >
> > > >
> > >
> >
> org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206)
> > > > at org.apache.maven.cli.MavenCli.container(MavenCli.java:585)
> > > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:274)
> > > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau

Re: Do we plan to support extensions with java 17?

2023-01-24 Thread Tamás Cservenák

Howdy,

Plexus-shim is built on top of Sisu, and Sisu is built on top of Guice.
Maven is tied to plexus-shim very much.

Guice shades ASM as well (current version 5.1.0 has support for Java17:
https://github.com/google/guice/wiki/Guice510 )

Hence, our stack is pretty much tied to Guice. I hope Guice will be fast
enough to support at least LTS Java versions as they come out, while we, at
Sisu, will need to speed up the release process and "follow" Guice more
closely... Currently there was a gap, Sisu lagged a bit but hopefully
things will catch up soon.

That's the best I can come up with right now.

HTH
Tamas

On Tue, Jan 24, 2023 at 7:54 PM Romain Manni-Bucau 
wrote:

> Again: cause the PR which is not merged is already not sufficient for the
> LTS of september. Asm version is a running forward game and technically we
> don't need it _there_ so if we can make it effortless I think it could only
> have a positive impact on the project. Concretely the 9.4 (the PR) does not
> support the next LTS (21), see
>
> https://gitlab.ow2.org/asm/asm/-/blob/master/asm/src/main/java/org/objectweb/asm/Opcodes.java#L289
> and compare to 9.4 release/branch for ex.
>
>
> Le mar. 24 janv. 2023 à 19:01, Tamás Cservenák  a
> écrit :
>
> > Howdy,
> >
> > Why again?
> >
> > There is ongoing effort (master is already updated), but also to raise
> > whole Java level of Sisu, see
> > https://github.com/eclipse/sisu.inject/pull/72
> > Hopefully soon new sisu release will happen that will contain updated ASM
> > and allow using Java11+ bytecode.
> >
> > Thanks
> > T
> >
> >
> > On Tue, Jan 24, 2023 at 6:58 PM Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> > > Hi all,
> > >
> > > We are hit again by sisu asm, we cant write a component using sisu
> Named
> > > SPI if compiled with java 17 (since then it will be visited with a too
> > old
> > > asm - exception at the end), do we want to upgrade asm there, do we
> want
> > to
> > > plan drop it - guess we can using the annot processor to collect more
> > data?
> > >
> > >
> > > Exception:
> > >
> > > java.lang.IllegalArgumentException
> > > at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:170)
> > > at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:153)
> > > at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:424)
> > > at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:102)
> > > at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:78)
> > > at org.eclipse.sisu.space
> > > .SpaceModule.scanForElements(SpaceModule.java:168)
> > > at org.eclipse.sisu.space.SpaceModule.configure(SpaceModule.java:129)
> > > at
> > >
> > >
> >
> org.eclipse.sisu.plexus.PlexusAnnotatedBeanModule.configure(PlexusAnnotatedBeanModule.java:102)
> > > at
> > >
> > >
> >
> org.eclipse.sisu.plexus.PlexusBindingModule.configure(PlexusBindingModule.java:63)
> > > at
> > >
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> > > at com.google.inject.spi.Elements.getElements(Elements.java:108)
> > > at com.google.inject.spi.Elements.getElements(Elements.java:101)
> > > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:75)
> > > at
> > >
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> > > at com.google.inject.spi.Elements.getElements(Elements.java:108)
> > > at
> > >
> > >
> >
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:160)
> > > at
> > >
> > >
> >
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> > > at com.google.inject.Guice.createInjector(Guice.java:87)
> > > at com.google.inject.Guice.createInjector(Guice.java:69)
> > > at com.google.inject.Guice.createInjector(Guice.java:59)
> > > at
> > >
> > >
> >
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> > > at
> > >
> > >
> >
> org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206)
> > > at org.apache.maven.cli.MavenCli.container(MavenCli.java:585)
> > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:274)
> > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> > >
> > > 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
> > > >
> > >
> >
>

Re: Do we plan to support extensions with java 17?

2023-01-24 Thread Romain Manni-Bucau

Again: cause the PR which is not merged is already not sufficient for the
LTS of september. Asm version is a running forward game and technically we
don't need it _there_ so if we can make it effortless I think it could only
have a positive impact on the project. Concretely the 9.4 (the PR) does not
support the next LTS (21), see
https://gitlab.ow2.org/asm/asm/-/blob/master/asm/src/main/java/org/objectweb/asm/Opcodes.java#L289
and compare to 9.4 release/branch for ex.


Le mar. 24 janv. 2023 à 19:01, Tamás Cservenák  a
écrit :

> Howdy,
>
> Why again?
>
> There is ongoing effort (master is already updated), but also to raise
> whole Java level of Sisu, see
> https://github.com/eclipse/sisu.inject/pull/72
> Hopefully soon new sisu release will happen that will contain updated ASM
> and allow using Java11+ bytecode.
>
> Thanks
> T
>
>
> On Tue, Jan 24, 2023 at 6:58 PM Romain Manni-Bucau 
> wrote:
>
> > Hi all,
> >
> > We are hit again by sisu asm, we cant write a component using sisu Named
> > SPI if compiled with java 17 (since then it will be visited with a too
> old
> > asm - exception at the end), do we want to upgrade asm there, do we want
> to
> > plan drop it - guess we can using the annot processor to collect more
> data?
> >
> >
> > Exception:
> >
> > java.lang.IllegalArgumentException
> > at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:170)
> > at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:153)
> > at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:424)
> > at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:102)
> > at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:78)
> > at org.eclipse.sisu.space
> > .SpaceModule.scanForElements(SpaceModule.java:168)
> > at org.eclipse.sisu.space.SpaceModule.configure(SpaceModule.java:129)
> > at
> >
> >
> org.eclipse.sisu.plexus.PlexusAnnotatedBeanModule.configure(PlexusAnnotatedBeanModule.java:102)
> > at
> >
> >
> org.eclipse.sisu.plexus.PlexusBindingModule.configure(PlexusBindingModule.java:63)
> > at
> > com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> > at com.google.inject.spi.Elements.getElements(Elements.java:108)
> > at com.google.inject.spi.Elements.getElements(Elements.java:101)
> > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:75)
> > at
> > com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> > at com.google.inject.spi.Elements.getElements(Elements.java:108)
> > at
> >
> >
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:160)
> > at
> >
> >
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> > at com.google.inject.Guice.createInjector(Guice.java:87)
> > at com.google.inject.Guice.createInjector(Guice.java:69)
> > at com.google.inject.Guice.createInjector(Guice.java:59)
> > at
> >
> >
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> > at
> >
> >
> org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206)
> > at org.apache.maven.cli.MavenCli.container(MavenCli.java:585)
> > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:274)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> >
> > 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
> > >
> >
>

Re: Do we plan to support extensions with java 17?

2023-01-24 Thread Tamás Cservenák

Howdy,

Why again?

There is ongoing effort (master is already updated), but also to raise
whole Java level of Sisu, see https://github.com/eclipse/sisu.inject/pull/72
Hopefully soon new sisu release will happen that will contain updated ASM
and allow using Java11+ bytecode.

Thanks
T


On Tue, Jan 24, 2023 at 6:58 PM Romain Manni-Bucau 
wrote:

> Hi all,
>
> We are hit again by sisu asm, we cant write a component using sisu Named
> SPI if compiled with java 17 (since then it will be visited with a too old
> asm - exception at the end), do we want to upgrade asm there, do we want to
> plan drop it - guess we can using the annot processor to collect more data?
>
>
> Exception:
>
> java.lang.IllegalArgumentException
> at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:170)
> at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:153)
> at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:424)
> at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:102)
> at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:78)
> at org.eclipse.sisu.space
> .SpaceModule.scanForElements(SpaceModule.java:168)
> at org.eclipse.sisu.space.SpaceModule.configure(SpaceModule.java:129)
> at
>
> org.eclipse.sisu.plexus.PlexusAnnotatedBeanModule.configure(PlexusAnnotatedBeanModule.java:102)
> at
>
> org.eclipse.sisu.plexus.PlexusBindingModule.configure(PlexusBindingModule.java:63)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> at com.google.inject.spi.Elements.getElements(Elements.java:108)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:75)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
> at com.google.inject.spi.Elements.getElements(Elements.java:108)
> at
>
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:160)
> at
>
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at com.google.inject.Guice.createInjector(Guice.java:69)
> at com.google.inject.Guice.createInjector(Guice.java:59)
> at
>
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> at
>
> org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206)
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:585)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:274)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
>
> 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
> >
>

Do we plan to support extensions with java 17?

2023-01-24 Thread Romain Manni-Bucau

Hi all,

We are hit again by sisu asm, we cant write a component using sisu Named
SPI if compiled with java 17 (since then it will be visited with a too old
asm - exception at the end), do we want to upgrade asm there, do we want to
plan drop it - guess we can using the annot processor to collect more data?


Exception:

java.lang.IllegalArgumentException
at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:170)
at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:153)
at org.eclipse.sisu.space.asm.ClassReader.(ClassReader.java:424)
at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:102)
at org.eclipse.sisu.space.SpaceScanner.accept(SpaceScanner.java:78)
at org.eclipse.sisu.space.SpaceModule.scanForElements(SpaceModule.java:168)
at org.eclipse.sisu.space.SpaceModule.configure(SpaceModule.java:129)
at
org.eclipse.sisu.plexus.PlexusAnnotatedBeanModule.configure(PlexusAnnotatedBeanModule.java:102)
at
org.eclipse.sisu.plexus.PlexusBindingModule.configure(PlexusBindingModule.java:63)
at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
at com.google.inject.spi.Elements.getElements(Elements.java:108)
at com.google.inject.spi.Elements.getElements(Elements.java:101)
at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:75)
at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
at com.google.inject.spi.Elements.getElements(Elements.java:108)
at
com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:160)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
at com.google.inject.Guice.createInjector(Guice.java:87)
at com.google.inject.Guice.createInjector(Guice.java:69)
at com.google.inject.Guice.createInjector(Guice.java:59)
at
org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
at
org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206)
at org.apache.maven.cli.MavenCli.container(MavenCli.java:585)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:274)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book

Re: Maven 3.9,0 plan

2023-01-24 Thread Falko Modler


Thanks Slawomir!

Tested via
https://github.com/gitflow-incremental-builder/gitflow-incremental-builder,
no issues!

Might try Quarkus next.

Cheers,

Falko

Am 19.01.2023 um 23:11 schrieb Slawomir Jaranowski:

Build on Jenkins deploys snapshot artifacts to ASF repository,

https://repository.apache.org/#nexus-search;gav~org.apache.maven~apache-maven~3.9.0-SNAPSHOT~~


czw., 19 sty 2023 o 22:49 Falko Modler  napisał(a):


Hi there,

So, please anyone able to, test 3.9.0-SNAPSHOT if you can.

do I have to build it on my own? I've been looking in a few places
including Jenkins but I couldn't find a pre-built archive.

Thanks!

Cheers,

Falko


-
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 3.9,0 plan

2023-01-24 Thread Mark Derricutt


On 24 Jan 2023, at 21:22, Tamás Cservenák wrote:


Mark,

Can you provide more information about this error?
I understand if this plugin is internal (not OSS), but can you provide 
me
the POM of it, or at least the dependencies snippet related to Maven 
and

resolver?
"A required class is missing" is strange, especially as
BasicRepositoryConnectorFactory is provided by Maven itself?

Thanks
Tamas


Have been meaning to get this open sourced for ages, I keep thinking "I 
should really clean up the code to be more presentable first" and it 
always goes on the backbench :)


Ironically - pulling out these dependencies, I think I see my problem - 
usage of this plugin rewrites dependencies to ban transitives, and lock 
ranges to `[]` - and well, the plugin is used on itself - so we're 
locking the dependency range of resolver.


I'll update it to relax the ranges in the plugin and see if that works.


```

  org.apache.maven
  maven-artifact
  [3.8.5]
  

  *
  *

  


  org.apache.maven
  maven-resolver-provider
  [3.8.5]
  


  org.apache.maven.resolver
  maven-resolver-api
  [1.7.3]
  


  org.apache.maven.resolver
  maven-resolver-connector-basic
  [1.7.3]
  


  org.apache.maven.resolver
  maven-resolver-impl
  [1.7.3]
  


  org.apache.maven.resolver
  maven-resolver-spi
  [1.7.3]
  


  org.apache.maven.resolver
  maven-resolver-transport-file
  [1.7.3]
  


  org.apache.maven.resolver
  maven-resolver-transport-http
  [1.7.3]
  


  org.apache.maven.resolver
  maven-resolver-util
  [1.7.3]
  

```



---
"The ease with which a change can be implemented has no relevance at all 
to whether it is the right change for the (Java) Platform for all time." 
 Mark Reinhold.


Mark Derricutt
http://www.chaliceofblood.net
http://www.theoryinpractice.net
http://twitter.com/talios
http://facebook.com/mderricutt

Re: Maven 3.9,0 plan

2023-01-24 Thread Tamás Cservenák

Mark,

Can you provide more information about this error?
I understand if this plugin is internal (not OSS), but can you provide me
the POM of it, or at least the dependencies snippet related to Maven and
resolver?
"A required class is missing" is strange, especially as
BasicRepositoryConnectorFactory is provided by Maven itself?

Thanks
Tamas

On Tue, Jan 24, 2023 at 5:49 AM Mark Derricutt  wrote:

> On 19 Jan 2023, at 22:02, Tamás Cservenák wrote:
>
> > So, please anyone able to, test 3.9.0-SNAPSHOT if you can.
>
>
> Seems to run fine for my normal projects - but crashes on in my main
> $work project, due to an internal Maven Plugin I have that uses the
> maven resolver - and I've not released a version of that which uses the
> newer dependency so gets:
>
> ```
> [ERROR] Failed to execute goal
> com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps
> (default-cli) on project smx3.api: Execution default-cli of goal
> com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps failed: A
> required class was missing while executing
> com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps:
> org/eclipse/aether/connector/basic/BasicRepositoryConnectorFactory
> [ERROR] -
> [ERROR] realm =plugin>com.smxemail:rangeresolver-maven-plugin:1.1.58
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
>
> file:/Users/amrk/.m2/repository/com/smxemail/rangeresolver-maven-plugin/1.1.58/rangeresolver-maven-plugin-1.1.58.jar
> [ERROR] urls[1] =
>
> file:/Users/amrk/.m2/repository/com/smxemail/com.smxemail.rangeresolver/1.1.34/com.smxemail.rangeresolver-1.1.34.jar
> [ERROR] urls[2] =
>
> file:/Users/amrk/.m2/repository/com/google/guava/guava/31.1-jre/guava-31.1-jre.jar
> [ERROR] urls[3] =
>
> file:/Users/amrk/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> ```
>
> Likely just requires me to update my plugin, but this will likely break
> other mojos that use aether/resolver.
>
> Being a .0 release (even tho not a major) I think I'm fine with that -
> but it might be something we want to document?
>
>
>
>
>
> ---
> "The ease with which a change can be implemented has no relevance at all
> to whether it is the right change for the (Java) Platform for all time."
>  Mark Reinhold.
>
> Mark Derricutt
> http://www.chaliceofblood.net
> http://www.theoryinpractice.net
> http://twitter.com/talios
> http://facebook.com/mderricutt
>

Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M4

2023-01-24 Thread Slawomir Jaranowski

+1

- spotless and line ending code ... from source-release
- surefire, checkstyle, pmd raptors are empty

niedz., 22 sty 2023 o 20:06 Michael Osipov  napisał(a):

> Hi,
>
> IMPORTANT: Requires Doxia 2.0.0-M5 vote/staging repo!
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352772
>
> 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-reporting-api
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1857/
>
> https://repository.apache.org/content/repositories/maven-1857/org/apache/maven/reporting/maven-reporting-api/4.0.0-M4/maven-reporting-api-4.0.0-M4-source-release.zip
>
> Source release checksum(s):
> maven-reporting-api-4.0.0-M4-source-release.zip
> sha512:
>
> 92d884e2e26616be65510b64e429efa489b59e593d288ad7877272c212a2926cb43416a992428ffd209bed4303c4955ba3cf056c4c69a801512421f6a77e293e
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-api-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Sławomir Jaranowski

JDK 20 Rampdown Phase 2 & JMX Heads-up

Re: Do we plan to support extensions with java 17?

Re: Do we plan to support extensions with java 17?

Re: Do we plan to support extensions with java 17?

Re: Do we plan to support extensions with java 17?

Do we plan to support extensions with java 17?

Re: Maven 3.9,0 plan

Re: Maven 3.9,0 plan

Re: Maven 3.9,0 plan

Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M4

10 matches

Site Navigation

Mail list logo

Footer information