Hi Patrik,

I see that you use a "modern" jar plugin
Can you configure it like that and see if it's better

<groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-jar-plugin</artifactId>
        <version>a superior version than 3.0.2</version>
        <configuration>
            <archive>
                
<manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
            </archive>
</configuration>

Best Regards
Eric

-----Message d'origine-----
De : Patrik Karlström <pat...@trixon.se> 
Envoyé : jeudi 13 juin 2019 22:10
À : dev@netbeans.apache.org
Objet : nbm-maven-plugin 4.2 fails

Hi Eric, as always, it's really nice to see the progress made on the maven 
related side of netbeans, thank you.

So, I manage to build a library project using 4.2, but I get the following 
failure when trying to build the Mapton application[1]:

Private classes referenced in module:
[org.netbeans.modules.options.OptionsWindowAction]
Project depends on packages not accessible at runtime in module
org.netbeans.api:org-netbeans-modules-options-api:jar:RELEASE110

Failed to execute goal
org.apache.netbeans.utilities:nbm-maven-plugin:4.2:manifest
(default-manifest) on project core: Uncategorized problems with NetBeans 
dependency verification (maybe MNBMODULE-102 or wrong maven dependency 
metadata). Supposedly external classes are used in the project's binaries but 
the classes are not found on classpath. Class usages:
[org.netbeans.core.actions.LogAction] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.netbeans.utilities:nbm-maven-plugin:4.2:manifest
(default-manifest) on project core: Uncategorized problems with NetBeans 
dependency verification (maybe MNBMODULE-102 or wrong maven dependency 
metadata). Supposedly external classes are used in the project's binaries but 
the classes are not found on classpath. Class usages:
[org.netbeans.core.actions.LogAction]
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.MojoFailureException: Uncategorized problems 
with NetBeans dependency verification (maybe MNBMODULE-102 or wrong maven 
dependency metadata). Supposedly external classes are used in the project's 
binaries but the classes are not found on classpath. Class
usages: [org.netbeans.core.actions.LogAction]
at
org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.checkModuleClassPath(NetBeansManifestUpdateMojo.java:755)
at
org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.execute(NetBeansManifestUpdateMojo.java:550)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more

I'm not sure if the fault is in Mapton, in 
org.netbeans.modules.options.OptionsWindowAction or in the nbm-maven-plugin.


[1] https://github.com/trixon/mapton/tree/apache-nbm-maven-plugin


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to