Hi,
The problem is in the class org.mapton.core.actions.OptionsAction
Line: *Actions.forID("Window",
"org.netbeans.modules.options.OptionsWindowAction").actionPerformed(null);*
I don't know why is it detected by nbm-maven-plugin 4.2, but if it is a
new thing, it should not check whether it is a private class but only if
the class is in the classpath...
BTW:
https://repository.apache.org/content/repositories/orgapachenetbeans-1011
is down and new repo
https://repository.apache.org/content/repositories/public(releases) has
renamed groupId from org.apache.netbeans to org.netbeans.
Is this the final version?
ArSi
------------------------------------------------------------------------
*From:* Eric Bresie <[email protected]>
*Sent:* Saturday, June 15, 2019 9:42PM
*To:* Apache Netbeans <[email protected]>
*Subject:* Re: RE: nbm-maven-plugin 4.2 fails
What version of Java module issue?
Could this be one of the apis which was an internal and now unavailable needing
change to something new?
Eric Bresie
[email protected]
On June 15, 2019 at 6:28:19 AM CDT, Eric Barboni <[email protected]> wrote:
Hi Patrik,
You may report an issue in the mavenutilities component in the JIRA
Not sure how to fix yet.
Regards
Eric
-----Message d'origine-----
De : Patrik Karlström <[email protected]>
Envoyé : samedi 15 juin 2019 07:45
À : [email protected]
Objet : Re: nbm-maven-plugin 4.2 fails
Yes, <verifyRuntime>false</verifyRuntime> got it working!
Nota bene, I don't have access at this time to all modules populating the
options dialog.
The basic ones do appear in the options dialog though.
This warning is still there:
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
Where do we go from here? Should I file a bug report, and if so, against what?
Den fre 14 juni 2019 kl 14:26 skrev Eric Barboni <[email protected]>:
Hi,
It seems that OptionsAction contains
"org.netbeans.modules.options.OptionsWindowAction"
I'm not sure why this change happen compare to previous version
You may try to configure nbm-maven-plugin for core with the following:
<verifyRuntime>false</verifyRuntime>
Regards
Eric
-----Message d'origine-----
De : Patrik Karlström <[email protected]> Envoyé : vendredi 14 juin
2019 11:33 À : [email protected] Objet : Re: nbm-maven-plugin
4.2 fails
Well, I just tried 3.1.0 & 3.1.1 to no avail.
Is there anything else I can do?
Den tors 13 juni 2019 kl 23:36 skrev Eric Barboni <[email protected]>:
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</m
anifestFile>
</archive>
</configuration>
Best Regards
Eric
-----Message d'origine-----
De : Patrik Karlström <[email protected]> Envoyé : jeudi 13 juin 2019
22:10 À : [email protected] 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.buildProj
ec
t(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProj
ec
t(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThr
ea
dedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecyc
le
Starter.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
.j
ava:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
ss
orImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Lau
nc
her.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.ja
va
:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(L
au
ncher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java
:3
56) 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.checkModuleClassP
at
h(NetBeansManifestUpdateMojo.java:755)
at
org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.execute(NetBeansM
an
ifestUpdateMojo.java:550)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Defaul
tB
uildPluginManager.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: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
