Re: plugin for nb contains osgi bundles

Perhaps your configuration is wrong. Try to debug the Maven-plugin. It is
quite easy https://dzone.com/articles/debugging-maven-mojo-plugin

Den 14 nov. 2016 20:30 skrev "jiří svatoš" <[email protected]>:

> Hi,
>
> we are trying to user NB platform instead of eclipse in our company. Now,
> we have to show, that it is possible.
>
> Task is easy:
>
> Create plugin for NB with rest interface and use standart project UI for
> java project.
>
> All project are under maven control, some project are OSGi bundle -
> because compatibility with rest of system.
>
> For rest I used jersey in OSGi bundles:
>
>        <dependency>
>             <groupId>org.glassfish.jersey.containers</groupId>
>             <artifactId>jersey-container-servlet-core</artifactId>
>             <version>2.23.2</version>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.felix</groupId>
>             <artifactId>org.apache.felix.http.bundle</artifactId>
>             <version>2.2.0</version>
>         </dependency>
>
> I dont know, if it is the best solution, but better something then nothing.
>
> I am not able to create one big nbm as plugin or better generate zip
> "netbeans_site" distribution site.
>
> Nbm:standalone-zip
> Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:3.13:standalone-zip
> (default-cli) on project ppt.client.rest: MojoExecutionException:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:nbm-maven-plugin:3.13:standalone-zip (default-cli)
> on project ppt.client.rest:
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:217)
> 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:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.
> singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.
> execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException:
>
> please help,
>
> with best regards, Jiri Svatos
>