Thanks Sławomir
+1 from me
Delany
On Tue, 28 Mar 2023 at 01:09, Slawomir Jaranowski
wrote:
> Please try: https://github.com/delanym/MINVOKER-283/pull/1
>
> wt., 28 mar 2023 o 00:36 Delany napisał(a):
>
> > 3.5.0 wasn't working because of
> > https://issues.apache.org/jira/browse/MINVOKER-328
+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&version=12349526
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MSCMPUB/issues
>
> Sta
Please try: https://github.com/delanym/MINVOKER-283/pull/1
wt., 28 mar 2023 o 00:36 Delany napisał(a):
> 3.5.0 wasn't working because of
> https://issues.apache.org/jira/browse/MINVOKER-328
>
> There's a reproducer on the issue (with wrong issue number)
>
> On Tue, 28 Mar 2023, 00:32 Slawomir Ja
3.5.0 wasn't working because of
https://issues.apache.org/jira/browse/MINVOKER-328
There's a reproducer on the issue (with wrong issue number)
On Tue, 28 Mar 2023, 00:32 Slawomir Jaranowski,
wrote:
> wt., 28 mar 2023 o 00:23 Delany napisał(a):
>
> > -1
> >
> > Fine on jdk11. On jdk17:
> >
> >
wt., 28 mar 2023 o 00:23 Delany napisał(a):
> -1
>
> Fine on jdk11. On jdk17:
>
>
Delany thanks for testing ...
- does 3.5.0 - works for your project / test?
- how can I reproduce it?
-
> [INFO] java.lang.NoClassDefFoundError: Could not initialize class
> org.codehaus.groovy.vmplugin.v7.Java7
-1
Fine on jdk11. On jdk17:
[INFO] java.lang.NoClassDefFoundError: Could not initialize class
org.codehaus.groovy.vmplugin.v7.Java7
[INFO] at
org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
[INFO] at
org.codehaus.groovy.reflection.GroovyClassValueFactory.(GroovyClassValue
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525&version=12352974
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC
So you mean maven 5 will need to rename and rerelease all plugins even if
they will be compatible thanks the policy versioning rule + new API?
Npm and webpacks are not great rerefences since they don't aim at being
stable as we intend.
Look at javaee (before the jakarta big bang which broke this as
The advantage is simple.
With "maven4" in the module name, you don't need a compatibility matrix on
every plugins homepage or readme.
Just look at npm modules and webpack... Tables over tables...
On Sun, 26 Mar 2023, 19:29 Michael Osipov, wrote:
> Am 2023-03-26 um 19:02 schrieb Romain Manni-
Am 2023-03-26 um 19:51 schrieb Michael Osipov:
Hi,
We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317920&version=12349526
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MSCMPUB/issues
Staging repo:
https://reposi
10 matches
Mail list logo