App will not run after forking and building

Issue #1 closed
Bruce Schubert created an issue

The Terramenta Application will not run. I forked the repository, added the worldwind jars, and built the Terramenta project. When I run the app (from within NetBeans 8.2) the following appears in the output log:

Can't process ..\..\..\terramenta-globe\target\classes
[INFO] java.io.FileNotFoundException: ..\..\..\terramenta-globe\target\classes (Access is denied)
[INFO]  at java.util.zip.ZipFile.open(Native Method)
[INFO]  at java.util.zip.ZipFile.<init>(ZipFile.java:219)
[INFO]  at java.util.zip.ZipFile.<init>(ZipFile.java:149)
[INFO]  at java.util.jar.JarFile.<init>(JarFile.java:166)
[INFO]  at java.util.jar.JarFile.<init>(JarFile.java:130)
[INFO] [catch] at org.netbeans.core.netigso.Netigso.findRecursivePkgs(Netigso.java:760)
[INFO]  at org.netbeans.core.netigso.Netigso.substitutePkg(Netigso.java:738)
[INFO]  at org.netbeans.core.netigso.Netigso.fakeBundle(Netigso.java:608)
[INFO]  at org.netbeans.core.netigso.Netigso.fakeOneModule(Netigso.java:503)
[INFO]  at org.netbeans.core.netigso.Netigso.prepare(Netigso.java:176)
[INFO]  at org.netbeans.NetigsoHandle.turnOn(NetigsoHandle.java:138)
[INFO]  at org.netbeans.ModuleManager.enable(ModuleManager.java:1353)
[INFO]  at org.netbeans.ModuleManager.enable(ModuleManager.java:1170)
[INFO]  at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:340)
[INFO]  at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:276)
[INFO]  at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:301)
[INFO]  at org.netbeans.core.startup.Main.getModuleSystem(Main.java:181)
[INFO]  at org.netbeans.core.startup.Main.getModuleSystem(Main.java:150)
[INFO]  at org.netbeans.core.startup.Main.start(Main.java:307)
[INFO]  at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:123)
[INFO]  at java.lang.Thread.run(Thread.java:745)
[INFO] java.lang.NullPointerException
[INFO]  at org.netbeans.core.netigso.Netigso.findRecursivePkgs(Netigso.java:781)
[INFO]  at org.netbeans.core.netigso.Netigso.substitutePkg(Netigso.java:738)
[INFO]  at org.netbeans.core.netigso.Netigso.fakeBundle(Netigso.java:608)
[INFO]  at org.netbeans.core.netigso.Netigso.fakeOneModule(Netigso.java:503)
[INFO]  at org.netbeans.core.netigso.Netigso.prepare(Netigso.java:176)
[INFO]  at org.netbeans.NetigsoHandle.turnOn(NetigsoHandle.java:138)
[INFO]  at org.netbeans.ModuleManager.enable(ModuleManager.java:1353)
[INFO]  at org.netbeans.ModuleManager.enable(ModuleManager.java:1170)
[INFO]  at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:340)
[INFO]  at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:276)
[INFO]  at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:301)
[INFO]  at org.netbeans.core.startup.Main.getModuleSystem(Main.java:181)
[INFO]  at org.netbeans.core.startup.Main.getModuleSystem(Main.java:150)
[INFO]  at org.netbeans.core.startup.Main.start(Main.java:307)
[INFO]  at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:123)
[INFO]  at java.lang.Thread.run(Thread.java:745)

Comments (3)

  1. Bruce Schubert reporter

    This issue can be resolved by setting useOSGiDependencies to false in the super POM.

    Edit the nbm-maven-plugin plugin configuration in the super POM and change the <useOSGiDependencies /> value.

    Example:

        <build>
            <pluginManagement>
                <plugins>
                    ...
                    <plugin>
                        <groupId>org.codehaus.mojo</groupId>
                        <artifactId>nbm-maven-plugin</artifactId>
                        <version>${nbm-maven-plugin.version}</version>
                        <extensions>true</extensions>
                        <configuration>
                            <useOSGiDependencies>false</useOSGiDependencies>
                            <brandingToken>${brandingToken}</brandingToken>
                            <cluster>${brandingToken}</cluster>
                        </configuration>
                    </plugin>
                </plugins>
            </pluginManagement>
             ...
         </build>
    
  2. Log in to comment