[VOTE] Import mvndaemon/mvnd project @ Apache

2021-06-15 Thread Olivier Lamy
Hi As already proposed by Guillaume, it looks to be a good idea to import mvndaemon/mvnd here at Apache. I'd like to propose a vote for this. +1: import the project here 0 : no real idea -1 : no (please explain why) cheers -- Olivier PS: Actually I have no idea how binding works in such vote.

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Guillaume Nodet
Well, my point was not really to find a workaround, but rather to start a discussion around "maven jvm customization from files is not well supported for now" ... :-) Le mer. 16 juin 2021 à 07:24, Romain Manni-Bucau a écrit : > Le mar. 15 juin 2021 à 23:39, Guillaume Nodet a écrit > : > > > In

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Romain Manni-Bucau
Le mar. 15 juin 2021 à 23:39, Guillaume Nodet a écrit : > In my case, it was a test in mvnd which is using some low level > reflection. I do agree this is not the best example, because an easy > workaround can be done by configuring surefire to use a fork. However, if > a plugin does the same t

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Guillaume Nodet
In my case, it was a test in mvnd which is using some low level reflection. I do agree this is not the best example, because an easy workaround can be done by configuring surefire to use a fork. However, if a plugin does the same thing, there's no easy way to workaround it. Le mar. 15 juin 2021

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Romain Manni-Bucau
Hi, There are two levels for me: 1. Maven itself -> maven opts works not bad but we should work ootb 2. Forks -> each plugin must support that and it cna be made dynamic with an extension which autoadjust the conf block Wdyt? Le mar. 15 juin 2021 à 22:02, Benjamin Marwell a écrit : > Hi Tamá

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Benjamin Marwell
Hi Tamás, So hazelcast runs in the module path. Maven used the class path only. Thus, add-opens does not do anything. UNLESS... you start sub pocesses from Maven, eg using the exec plugin. This means we still need an example where you have this issue with Maven. On Tue, 15 Jun 2021, 20:27 Tamás

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Tamás Cservenák
Or xstream for that matter... ToP On Tue, Jun 15, 2021, 20:26 Tamás Cservenák wrote: > Just try to run hazelcast 3 (latest of 3.x) on java11. It will log what it > needs to be opened up. > > T on phone > > On Tue, Jun 15, 2021, 20:19 Benjamin Marwell wrote: > >> Tamás, >> >> which module do yo

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Tamás Cservenák
Just try to run hazelcast 3 (latest of 3.x) on java11. It will log what it needs to be opened up. T on phone On Tue, Jun 15, 2021, 20:19 Benjamin Marwell wrote: > Tamás, > > which module do you open? > > In most cases I have encountered, adding jaxb as a dependency to the > project is sufficien

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Benjamin Marwell
Tamás, which module do you open? In most cases I have encountered, adding jaxb as a dependency to the project is sufficient. But to be sure, we would need to see an example. I think this would have long been noticed if it was a common problem. Ben On Tue, 15 Jun 2021, 19:18 Tamás Cservenák,

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Tamás Cservenák
Howdy, Robert, I think you are wrong: from Java 11 migration guide --add-opens If you have to allow code on the class path to do deep reflection to access nonpublic members, then use the --add-opens runtime option. Some libraries do deep reflection, meaning setAccessible(true), so they can acces

Re: Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Robert Scholte
AFAIK the --add-opens is only useful when using the module path. Maven itself and the plugins use the classpath, so I would like to have an example to better understand your issue. thanks, Robert On 15-6-2021 18:43:35, Guillaume Nodet wrote: Hi everyone ! There are some small incompatibilities

Supporting building with incompatible JDK versions on a single project

2021-06-15 Thread Guillaume Nodet
Hi everyone ! There are some small incompatibilities between JDK around the supported command line versions. Usually, those do not cause any real problems. However, the "--add-opens" are sometimes necessary and only supported on JDK >= 9, as the JVM exits with an error on JDK 8. Some plugins may

Re: Software Heritage connector to Maven repositories

2021-06-15 Thread Boris Baldassari
On 15/06/2021 02:25, Bernd Eckenfels wrote: Hello Boris. Hi Bernd, I know that opening a Nexus JIRA is the usual way to get responses. Good point for the JIRA, Thanks! https://issues.sonatype.org/browse/MVNCENTRAL-6804 BTW also consider scraping the SCM URLs from the POM files and contact t