Hi Patrik, Thanks for the feedback and for early testing. It appears that due to groupID change the nbm plugin is not working well. The Apache Netbeans community has the charge now of this plugin you can find it here https://github.com/apache/incubator-netbeans-mavenutils/ you will need to mvn clean install in the following folder parent nbm-shared nbm-maven-harness nbm-maven-plugin
the reference for the plugin in the poms in mapton should be updated to <groupId>org.apache.netbeans.utilities</groupId> <artifactId>nbm-maven-plugin</artifactId> <version>4.2-SNAPSHOT</version> On your "core" module the plugin detect and error. I have not found a solution yet but you can skip it for the moment <verifyRuntime>false</verifyRuntime> Best Regards Eric -----Message d'origine----- De : Patrik Karlström <pat...@trixon.se> Envoyé : samedi 16 mars 2019 09:43 À : dev@netbeans.incubator.apache.org Objet : Re: Apache NetBeans (incubating) 10 maven artefacts Thank you, I really appreciate your work. I did a successful test with the library "almond" [1] but the "mapton" [2] program failed to build. It fails on bootstrap/launcher, why is that? [1] https://github.com/trixon/almond3/commit/b159b58ea02d329e78e4d9d6dd3e252d2d7d327e [2] https://github.com/trixon/mapton/commit/a8bd5a3513423010660b11f1397f8c9871687478 *Product Version:* Apache NetBeans IDE 10.0 (Build incubator-netbeans-release-380-on-20181217) *Java:* 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b26 *Runtime:* OpenJDK Runtime Environment 1.8.0_202-b26 *System:* Linux version 4.19.28-1-MANJARO running on amd64; UTF-8; sv_SE (nb) Reactor Summary: mapton-parent ...................................... SUCCESS [ 0.129 s] mapton-branding .................................... SUCCESS [ 1.395 s] core ............................................... SUCCESS [ 3.010 s] me-gmapsfx ......................................... SUCCESS [ 1.622 s] me-jxmapviewer2 .................................... SUCCESS [ 0.905 s] me-worldwind ....................................... SUCCESS [ 3.579 s] se-bookmarks ....................................... SUCCESS [ 0.733 s] se-geonames ........................................ SUCCESS [ 1.948 s] se-google .......................................... SUCCESS [ 1.018 s] se-nominatim ....................................... SUCCESS [ 1.013 s] te-swetrans ........................................ SUCCESS [ 0.729 s] reports ............................................ SUCCESS [ 1.552 s] wikipedia .......................................... SUCCESS [ 0.753 s] ww-eox ............................................. SUCCESS [ 1.381 s] ww-datasources ..................................... SUCCESS [ 1.483 s] datasources ........................................ SUCCESS [ 0.760 s] mapton ............................................. FAILURE [ 0.787 s] ------------------------------------------------------------------------ BUILD FAILURE ------------------------------------------------------------------------ Total time: 23.771 s Finished at: 2019-03-16T09:21:22+01:00 Final Memory: 22M/378M ------------------------------------------------------------------------ Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:cluster-app (default-cluster-app) on project mapton: We could not find org-netbeans-bootstrap among the modules in the application. Launchers could not be found. -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:cluster-app (default-cluster-app) on project mapton: We could not find org-netbeans-bootstrap among the modules in the application. Launchers could not be found. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) 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.MojoExecutionException: We could not find org-netbeans-bootstrap among the modules in the application. Launchers could not be found. at org.codehaus.mojo.nbm.CreateClusterAppMojo.getHarnessNbm(CreateClusterAppMojo.java:956) at org.codehaus.mojo.nbm.CreateClusterAppMojo.createBinEtcDir(CreateClusterAppMojo.java:795) at org.codehaus.mojo.nbm.CreateClusterAppMojo.execute(CreateClusterAppMojo.java:611) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 20 more Den fre 15 mars 2019 kl 19:42 skrev Eric Barboni <sk...@apache.org>: > Hi Apache NetBeans community > > I have prepared a staged repository for Apache NetBeans (incubating) > 10 maven artefacts. They are built using the 10.0vc5 tag that is the > release tag of Apache NetBeans (incubating) 10. > Bits are taken from a build because, Jenkins has a better connection > to central than me for an 1hour job > https://builds.apache.org/job/incubator-netbeans-r100-maven/ > > Staged repository is here: > https://repository.apache.org/content/repositories/orgapachenetbeans-1 > 011 > > Artefacts groupID is set org.apache.netbeans (our new home, and maybe > this group change may allow user to think what they are doing because > of feature missing due to code donation done in step) and future > Apache NetBeans may get the feature back > > I think that it's not possible to test with release of JDK greater > than 8 due to a limitation of the nbm-plugin NOTICE file, DISCLAMER > and LICENCE should be the same as the Apache NetBeans > (incubating) 10 release because taken from same source. > pom file are generated so maybe the ASF header is not mandatory in > this case. > > I wonder to ask community if those artefacts are technically usable > because I also wonder if it can make a valid vote candidate > > Best Regards > Eric > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: > dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
