Re: maven-compiler-plugin problem
Configuration is incorrect for JDK ^9 org.apache.maven.plugins maven-compiler-plugin 9 Chris Luff | Associate Principal Engineer | UK Development - Care Insight and Delivery Dev | chris.l...@cerner.com<mailto:chris.l...@cerner.com> | +44 (0)7970 735175 | Cerner Limited<http://www.cerner.com/> On 10 Oct 2019, at 07:35, Peter Cheung mailto:mcheun...@hotmail.com>> wrote: I was creating the project using Netbeans 11.1 Thanks From Peter From: Eric Barboni mailto:sk...@apache.org>> Sent: Tuesday, October 8, 2019 12:25 AM To: dev@netbeans.apache.org<mailto:dev@netbeans.apache.org> mailto:dev@netbeans.apache.org>> Subject: RE: maven-compiler-plugin problem Hi, Not sure what to do. Peter what was your path of creating your project, you just use NetBeans or use a webpage somewhere as starting point ? Maybe redirect from mojohaus website can be set now that we have website for nbmplugin. New website, as well as the old one are Generated by maven but as not specific JIRA it would catch all changelog for NetBeans useless. There is also a relocation mechanism in maven to make clear the change of groupid. Maybe we should improve NetBeans itself to detect latest version of the plugin. Best Regards Eric -Message d'origine- De : Peter Cheung mailto:mcheun...@hotmail.com>> Envoyé : lundi 7 octobre 2019 15:48 À : dev@netbeans.apache.org<mailto:dev@netbeans.apache.org> Objet : Re: maven-compiler-plugin problem Dear Gj Sorry i am too newbie, i don't know. Hope Eric can answer. Thanks From Peter From: Geertjan Wielenga mailto:geert...@apache.org>> Sent: Monday, October 7, 2019 4:54 PM To: dev@netbeans.apache.org<mailto:dev@netbeans.apache.org> mailto:dev@netbeans.apache.org>> Subject: Re: maven-compiler-plugin problem Where can we clearly document this on netbeans.apache.org<http://netbeans.apache.org>? Gj On Mon, 7 Oct 2019 at 10:49, Eric Barboni mailto:sk...@apache.org>> wrote: Hi, You should change the group,artifact,version to match the new plugin. Donation has been completed since a while, and a release occurs in june. org.apache.netbeans.utilities nbm-maven-plugin 4.2 Regards Eric -Message d'origine- De : Peter Cheung mailto:mcheun...@hotmail.com>> Envoyé : dimanche 6 octobre 2019 05:17 À : dev@netbeans.apache.org<mailto:dev@netbeans.apache.org> Objet : Re: maven-compiler-plugin problem Thank you very much Robert From: Robert Scholte mailto:rfscho...@apache.org>> Sent: Saturday, October 5, 2019 11:29 PM To: dev@netbeans.apache.org<mailto:dev@netbeans.apache.org> mailto:dev@netbeans.apache.org>> Subject: Re: maven-compiler-plugin problem Based on the message and the stacktrace it is actually a problem with the org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. It is using a version of ASM that doesn't understand the bytecodeversion of Java 9. https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mojohaus.org%2Fplugins.html%23data=02%7C01%7CChris.Luff%40cerner.com%7Cf2dece02f86d4d1f057f08d74d4c1abc%7Cfbc493a80d244454a815f4ca58e8c09d%7C0%7C1%7C637062861785175998sdata=pwUe68yeLCom42X50O5X0Tvy4%2Baa7rxL2ClKgl9Abcw%3Dreserved=0 shows you the plugins has been moved to https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbits.netbeans.org%2Fmavenutilities%2Fnbm-maven-plugin%2Fdata=02%7C01%7CChris.Luff%40cerner.com%7Cf2dece02f86d4d1f057f08d74d4c1abc%7Cfbc493a80d244454a815f4ca58e8c09d%7C0%7C1%7C637062861785175998sdata=JjRrOk5Hfyh66b%2FfZ7l%2B9pS3lP7nRPxuVe3NsVk%2Fz7U%3Dreserved=0 From here the documentation is a little bit tricky, but you can look for the manifest goal. https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbits.netbeans.org%2Fmavenutilities%2Fnbm-maven-plugin%2Fmanifest-mojodata=02%7C01%7CChris.Luff%40cerner.com%7Cf2dece02f86d4d1f057f08d74d4c1abc%7Cfbc493a80d244454a815f4ca58e8c09d%7C0%7C1%7C637062861785175998sdata=%2ByEfubAhhxwftyDyiwQ4SJDSc8vSdPLryaYzhkB%2BE30%3Dreserved=0 .html Here you see that they changes the groupId to org.apache.netbeans.utilities Hopefully version 4.2 will fix it, otherwise https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fnetbeans-mavenutils-nbm-maven-plugindata=02%7C01%7CChris.Luff%40cerner.com%7Cf2dece02f86d4d1f057f08d74d4c1abc%7Cfbc493a80d244454a815f4ca58e8c09d%7C0%7C1%7C637062861785175998sdata=xeWgU4g6YtYGzsnP34kB171Sid%2Fx%2FtKmiKiEkNj0Sis%3Dreserved=0 describes how to report a bug/improvement. thanks, Robert On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung mailto:mcheun...@hotmail.com>> wrote: Hi I have a maven library which is used by a maven netbeans module project. This is ok: maven-compiler-plugin 3.8.1 1.8 1.8 But if change to 1.9. It has exc
Re: maven-compiler-plugin problem
I was creating the project using Netbeans 11.1 Thanks >From Peter From: Eric Barboni Sent: Tuesday, October 8, 2019 12:25 AM To: dev@netbeans.apache.org Subject: RE: maven-compiler-plugin problem Hi, Not sure what to do. Peter what was your path of creating your project, you just use NetBeans or use a webpage somewhere as starting point ? Maybe redirect from mojohaus website can be set now that we have website for nbmplugin. New website, as well as the old one are Generated by maven but as not specific JIRA it would catch all changelog for NetBeans useless. There is also a relocation mechanism in maven to make clear the change of groupid. Maybe we should improve NetBeans itself to detect latest version of the plugin. Best Regards Eric -Message d'origine- De : Peter Cheung Envoyé : lundi 7 octobre 2019 15:48 À : dev@netbeans.apache.org Objet : Re: maven-compiler-plugin problem Dear Gj Sorry i am too newbie, i don't know. Hope Eric can answer. Thanks >From Peter From: Geertjan Wielenga Sent: Monday, October 7, 2019 4:54 PM To: dev@netbeans.apache.org Subject: Re: maven-compiler-plugin problem Where can we clearly document this on netbeans.apache.org? Gj On Mon, 7 Oct 2019 at 10:49, Eric Barboni wrote: > Hi, > > You should change the group,artifact,version to match the new plugin. > Donation has been completed since a while, and a release occurs in june. > > org.apache.netbeans.utilities > nbm-maven-plugin > 4.2 > > Regards > Eric > > -Message d'origine- > De : Peter Cheung Envoyé : dimanche 6 octobre > 2019 05:17 À : dev@netbeans.apache.org Objet : Re: > maven-compiler-plugin problem > > Thank you very much Robert > > > From: Robert Scholte > Sent: Saturday, October 5, 2019 11:29 PM > To: dev@netbeans.apache.org > Subject: Re: maven-compiler-plugin problem > > Based on the message and the stacktrace it is actually a problem with > the > org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. > It is using a version of ASM that doesn't understand the > bytecodeversion of Java 9. > > https://www.mojohaus.org/plugins.html# shows you the plugins has been > moved to http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ > > From here the documentation is a little bit tricky, but you can look > for the manifest goal. > http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/manifest-mojo > .html > > Here you see that they changes the groupId to > org.apache.netbeans.utilities > > Hopefully version 4.2 will fix it, otherwise > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin > describes how to report a bug/improvement. > > thanks, > Robert > > On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung > > wrote: > > > Hi > > I have a maven library which is used by a maven netbeans module > > project. > > > > This is ok: > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.8 > > 1.8 > > > > > > > > But if change to 1.9. It has exception when building the netbeans > > module > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.9 > > 1.9 > > > > > > > > > > Error: > > > > > > [INFO] > > > > -- > > -- > > > > [INFO] BUILD FAILURE > > > > [INFO] > > > > -- > > -- > > > > [INFO] Total time: 7.443 s > > > > [INFO] Finished at: 2019-10-05T20:18:06+08:00 > > > > [INFO] > > > > -- > > -- > > > > [ERROR] Failed to execute goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) > > on project netbeans-antlr: Execution default-manifest of goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: > > IllegalArgumentException -> [Help 1] > > > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > > (default-manifest) on project netbeans-antlr: Execution > > default-manifest of goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > failed. > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:215) > > > > at org.apache.maven.lifecycle.intern
RE: maven-compiler-plugin problem
Hi, Not sure what to do. Peter what was your path of creating your project, you just use NetBeans or use a webpage somewhere as starting point ? Maybe redirect from mojohaus website can be set now that we have website for nbmplugin. New website, as well as the old one are Generated by maven but as not specific JIRA it would catch all changelog for NetBeans useless. There is also a relocation mechanism in maven to make clear the change of groupid. Maybe we should improve NetBeans itself to detect latest version of the plugin. Best Regards Eric -Message d'origine- De : Peter Cheung Envoyé : lundi 7 octobre 2019 15:48 À : dev@netbeans.apache.org Objet : Re: maven-compiler-plugin problem Dear Gj Sorry i am too newbie, i don't know. Hope Eric can answer. Thanks >From Peter From: Geertjan Wielenga Sent: Monday, October 7, 2019 4:54 PM To: dev@netbeans.apache.org Subject: Re: maven-compiler-plugin problem Where can we clearly document this on netbeans.apache.org? Gj On Mon, 7 Oct 2019 at 10:49, Eric Barboni wrote: > Hi, > > You should change the group,artifact,version to match the new plugin. > Donation has been completed since a while, and a release occurs in june. > > org.apache.netbeans.utilities > nbm-maven-plugin > 4.2 > > Regards > Eric > > -Message d'origine- > De : Peter Cheung Envoyé : dimanche 6 octobre > 2019 05:17 À : dev@netbeans.apache.org Objet : Re: > maven-compiler-plugin problem > > Thank you very much Robert > > > From: Robert Scholte > Sent: Saturday, October 5, 2019 11:29 PM > To: dev@netbeans.apache.org > Subject: Re: maven-compiler-plugin problem > > Based on the message and the stacktrace it is actually a problem with > the > org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. > It is using a version of ASM that doesn't understand the > bytecodeversion of Java 9. > > https://www.mojohaus.org/plugins.html# shows you the plugins has been > moved to http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ > > From here the documentation is a little bit tricky, but you can look > for the manifest goal. > http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/manifest-mojo > .html > > Here you see that they changes the groupId to > org.apache.netbeans.utilities > > Hopefully version 4.2 will fix it, otherwise > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin > describes how to report a bug/improvement. > > thanks, > Robert > > On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung > > wrote: > > > Hi > > I have a maven library which is used by a maven netbeans module > > project. > > > > This is ok: > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.8 > > 1.8 > > > > > > > > But if change to 1.9. It has exception when building the netbeans > > module > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.9 > > 1.9 > > > > > > > > > > Error: > > > > > > [INFO] > > > > -- > > -- > > > > [INFO] BUILD FAILURE > > > > [INFO] > > > > -- > > -- > > > > [INFO] Total time: 7.443 s > > > > [INFO] Finished at: 2019-10-05T20:18:06+08:00 > > > > [INFO] > > > > -- > > -- > > > > [ERROR] Failed to execute goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) > > on project netbeans-antlr: Execution default-manifest of goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: > > IllegalArgumentException -> [Help 1] > > > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > > (default-manifest) on project netbeans-antlr: Execution > > default-manifest of goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > failed. > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:215) > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:156) > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:148) > > > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.bui
Re: maven-compiler-plugin problem
Dear Gj Sorry i am too newbie, i don't know. Hope Eric can answer. Thanks >From Peter From: Geertjan Wielenga Sent: Monday, October 7, 2019 4:54 PM To: dev@netbeans.apache.org Subject: Re: maven-compiler-plugin problem Where can we clearly document this on netbeans.apache.org? Gj On Mon, 7 Oct 2019 at 10:49, Eric Barboni wrote: > Hi, > > You should change the group,artifact,version to match the new plugin. > Donation has been completed since a while, and a release occurs in june. > > org.apache.netbeans.utilities > nbm-maven-plugin > 4.2 > > Regards > Eric > > -Message d'origine- > De : Peter Cheung > Envoyé : dimanche 6 octobre 2019 05:17 > À : dev@netbeans.apache.org > Objet : Re: maven-compiler-plugin problem > > Thank you very much Robert > > > From: Robert Scholte > Sent: Saturday, October 5, 2019 11:29 PM > To: dev@netbeans.apache.org > Subject: Re: maven-compiler-plugin problem > > Based on the message and the stacktrace it is actually a problem with the > org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. > It is using a version of ASM that doesn't understand the bytecodeversion of > Java 9. > > https://www.mojohaus.org/plugins.html# shows you the plugins has been > moved > to http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ > > From here the documentation is a little bit tricky, but you can look for > the manifest goal. > http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/manifest-mojo.html > > Here you see that they changes the groupId to org.apache.netbeans.utilities > > Hopefully version 4.2 will fix it, otherwise > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin > describes how to report a bug/improvement. > > thanks, > Robert > > On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung > wrote: > > > Hi > > I have a maven library which is used by a maven netbeans module > > project. > > > > This is ok: > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.8 > > 1.8 > > > > > > > > But if change to 1.9. It has exception when building the netbeans > > module > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.9 > > 1.9 > > > > > > > > > > Error: > > > > > > [INFO] > > -- > > -- > > > > [INFO] BUILD FAILURE > > > > [INFO] > > -- > > -- > > > > [INFO] Total time: 7.443 s > > > > [INFO] Finished at: 2019-10-05T20:18:06+08:00 > > > > [INFO] > > -- > > -- > > > > [ERROR] Failed to execute goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) on > > project netbeans-antlr: Execution default-manifest of goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: > > IllegalArgumentException -> [Help 1] > > > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > > (default-manifest) on project netbeans-antlr: Execution > > default-manifest of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > failed. > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:215) > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:156) > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:148) > > > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec > > t > > (LifecycleModuleBuilder.java:117) > > > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec > > t > > (LifecycleModuleBuilder.java:81) > > > > at > > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea > > dedBuilder.build > > (SingleThreadedBuilder.java:56) > > > > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > > (LifecycleStarter.java:128) > > > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > > > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > > > > at org.apache.maven.DefaultMaven.execute (Defaul
Re: maven-compiler-plugin problem
Where can we clearly document this on netbeans.apache.org? Gj On Mon, 7 Oct 2019 at 10:49, Eric Barboni wrote: > Hi, > > You should change the group,artifact,version to match the new plugin. > Donation has been completed since a while, and a release occurs in june. > > org.apache.netbeans.utilities > nbm-maven-plugin > 4.2 > > Regards > Eric > > -Message d'origine- > De : Peter Cheung > Envoyé : dimanche 6 octobre 2019 05:17 > À : dev@netbeans.apache.org > Objet : Re: maven-compiler-plugin problem > > Thank you very much Robert > > > From: Robert Scholte > Sent: Saturday, October 5, 2019 11:29 PM > To: dev@netbeans.apache.org > Subject: Re: maven-compiler-plugin problem > > Based on the message and the stacktrace it is actually a problem with the > org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. > It is using a version of ASM that doesn't understand the bytecodeversion of > Java 9. > > https://www.mojohaus.org/plugins.html# shows you the plugins has been > moved > to http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ > > From here the documentation is a little bit tricky, but you can look for > the manifest goal. > http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/manifest-mojo.html > > Here you see that they changes the groupId to org.apache.netbeans.utilities > > Hopefully version 4.2 will fix it, otherwise > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin > describes how to report a bug/improvement. > > thanks, > Robert > > On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung > wrote: > > > Hi > > I have a maven library which is used by a maven netbeans module > > project. > > > > This is ok: > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.8 > > 1.8 > > > > > > > > But if change to 1.9. It has exception when building the netbeans > > module > > > > > >maven-compiler-plugin > >3.8.1 > > > > 1.9 > > 1.9 > > > > > > > > > > Error: > > > > > > [INFO] > > -- > > -- > > > > [INFO] BUILD FAILURE > > > > [INFO] > > -- > > -- > > > > [INFO] Total time: 7.443 s > > > > [INFO] Finished at: 2019-10-05T20:18:06+08:00 > > > > [INFO] > > -- > > -- > > > > [ERROR] Failed to execute goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) on > > project netbeans-antlr: Execution default-manifest of goal > > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: > > IllegalArgumentException -> [Help 1] > > > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > > (default-manifest) on project netbeans-antlr: Execution > > default-manifest of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > failed. > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:215) > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:156) > > > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:148) > > > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec > > t > > (LifecycleModuleBuilder.java:117) > > > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec > > t > > (LifecycleModuleBuilder.java:81) > > > > at > > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea > > dedBuilder.build > > (SingleThreadedBuilder.java:56) > > > > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > > (LifecycleStarter.java:128) > > > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > > > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > > > > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > > > > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > > > > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > > > >
RE: maven-compiler-plugin problem
Hi, You should change the group,artifact,version to match the new plugin. Donation has been completed since a while, and a release occurs in june. org.apache.netbeans.utilities nbm-maven-plugin 4.2 Regards Eric -Message d'origine- De : Peter Cheung Envoyé : dimanche 6 octobre 2019 05:17 À : dev@netbeans.apache.org Objet : Re: maven-compiler-plugin problem Thank you very much Robert From: Robert Scholte Sent: Saturday, October 5, 2019 11:29 PM To: dev@netbeans.apache.org Subject: Re: maven-compiler-plugin problem Based on the message and the stacktrace it is actually a problem with the org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. It is using a version of ASM that doesn't understand the bytecodeversion of Java 9. https://www.mojohaus.org/plugins.html# shows you the plugins has been moved to http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ From here the documentation is a little bit tricky, but you can look for the manifest goal. http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/manifest-mojo.html Here you see that they changes the groupId to org.apache.netbeans.utilities Hopefully version 4.2 will fix it, otherwise https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin describes how to report a bug/improvement. thanks, Robert On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung wrote: > Hi > I have a maven library which is used by a maven netbeans module > project. > > This is ok: > > >maven-compiler-plugin >3.8.1 > > 1.8 > 1.8 > > > > But if change to 1.9. It has exception when building the netbeans > module > > >maven-compiler-plugin >3.8.1 > > 1.9 > 1.9 > > > > > Error: > > > [INFO] > -- > -- > > [INFO] BUILD FAILURE > > [INFO] > -- > -- > > [INFO] Total time: 7.443 s > > [INFO] Finished at: 2019-10-05T20:18:06+08:00 > > [INFO] > -- > -- > > [ERROR] Failed to execute goal > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) on > project netbeans-antlr: Execution default-manifest of goal > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: > IllegalArgumentException -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > (default-manifest) on project netbeans-antlr: Execution > default-manifest of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed. > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:215) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec > t > (LifecycleModuleBuilder.java:117) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec > t > (LifecycleModuleBuilder.java:81) > > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea > dedBuilder.build > (SingleThreadedBuilder.java:56) > > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native > Method) > > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke (Method.java:567) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:229) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) > > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:3
Re: maven-compiler-plugin problem
Thank you very much Robert From: Robert Scholte Sent: Saturday, October 5, 2019 11:29 PM To: dev@netbeans.apache.org Subject: Re: maven-compiler-plugin problem Based on the message and the stacktrace it is actually a problem with the org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. It is using a version of ASM that doesn't understand the bytecodeversion of Java 9. https://www.mojohaus.org/plugins.html# shows you the plugins has been moved to http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ From here the documentation is a little bit tricky, but you can look for the manifest goal. http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/manifest-mojo.html Here you see that they changes the groupId to org.apache.netbeans.utilities Hopefully version 4.2 will fix it, otherwise https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin describes how to report a bug/improvement. thanks, Robert On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung wrote: > Hi > I have a maven library which is used by a maven netbeans module > project. > > This is ok: > > >maven-compiler-plugin >3.8.1 > > 1.8 > 1.8 > > > > But if change to 1.9. It has exception when building the netbeans module > > >maven-compiler-plugin >3.8.1 > > 1.9 > 1.9 > > > > > Error: > > > [INFO] > > > [INFO] BUILD FAILURE > > [INFO] > > > [INFO] Total time: 7.443 s > > [INFO] Finished at: 2019-10-05T20:18:06+08:00 > > [INFO] > > > [ERROR] Failed to execute goal > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) on > project netbeans-antlr: Execution default-manifest of goal > org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: > IllegalArgumentException -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > (default-manifest) on project netbeans-antlr: Execution default-manifest > of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed. > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:215) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native > Method) > > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke (Method.java:567) > > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:229) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) > > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:356) > > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-manifest of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest > failed. > > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:148) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > > at org.apache.maven.lifecycle.inter
Re: maven-compiler-plugin problem
Based on the message and the stacktrace it is actually a problem with the org.codehaus.mojo:nbm-maven-plugin:4.1 plugin. It is using a version of ASM that doesn't understand the bytecodeversion of Java 9. https://www.mojohaus.org/plugins.html# shows you the plugins has been moved to http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ From here the documentation is a little bit tricky, but you can look for the manifest goal. http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/manifest-mojo.html Here you see that they changes the groupId to org.apache.netbeans.utilities Hopefully version 4.2 will fix it, otherwise https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin describes how to report a bug/improvement. thanks, Robert On Sat, 05 Oct 2019 14:18:32 +0200, Peter Cheung wrote: Hi I have a maven library which is used by a maven netbeans module project. This is ok: maven-compiler-plugin 3.8.1 1.8 1.8 But if change to 1.9. It has exception when building the netbeans module maven-compiler-plugin 3.8.1 1.9 1.9 Error: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7.443 s [INFO] Finished at: 2019-10-05T20:18:06+08:00 [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) on project netbeans-antlr: Execution default-manifest of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: IllegalArgumentException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest (default-manifest) on project netbeans-antlr: Execution default-manifest of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:567) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-manifest of goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at
