dev@glassfish.java.net

Re: V3 How to get gf:run to work

From: Stefan Arentz <stefan.arentz_at_norad.org>
Date: Fri, 11 May 2007 19:12:32 +0200

On May 11, 2007, at 7:03 PM, Stefan Arentz wrote:

> I'm hacking on a new deployer for V3. My project is completely
> standalone, I build it outside of the Glassfish build root.
> Packaging works fine, I end up with a correct HK2 module jar with a
> good looking manifest. But then when I try to run Glassfish through
> 'mvn gf:run' I get the following error:
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'gf'.
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] The plugin 'org.apache.maven.plugins:maven-gf-plugin' does
> not exist or no valid version could be found
>
> I'm not a Maven guru and I'm not sure what to do now :-)

Little update, I added:

       <plugin>
         <groupId>com.sun.enterprise.glassfish</groupId>
         <artifactId>maven-glassfish-plugin</artifactId>
         <extensions>true</extensions>
       </plugin>

To my project's pom and it can now find the maven-glassfish-plugin.
However, when I try to run:

java.lang.NullPointerException
         at com.sun.enterprise.build.RunMojo.execute(RunMojo.java:96)
         at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:412)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:534)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.java:488)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:458)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:140)
         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
322)
         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
         at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.codehaus.classworlds.Launcher.launchEnhanced
(Launcher.java:315)
         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
         at org.codehaus.classworlds.Launcher.mainWithExitCode
(Launcher.java:430)
         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

I'm sure I'm doing something silly or unsupported but I have some
time to kill at the airport so I might as well give it a try .. :-)

  S.