My later answer still holds (upgrade to alpha-2). Using alpha-1 definitely explains the exception you got as it also didn't support version discovery.
- Brett On 5/23/05, J. Matthew Pryor <[EMAIL PROTECTED]> wrote: > In answer to my own post, the addition of the goals > section to the "using" project now appears to call the > plugin, or at least start to. > > In fact the Red Herring wasn't red after all, now I am > back here. > > [INFO] Building Intermedi8 Core > [INFO] > ---------------------------------------------------------------------------- > [INFO] intermedi8-protege-plugin: using locally > installed snapshot > --------------------------------------------------- > constituent[0]: > file:/C:/dev/maven/m2dev/lib/commons-cli-1.0-beta-2.jar > constituent[1]: > file:/C:/dev/maven/m2dev/lib/maven-artifact-2.0-SNAPSHOT.jar > constituent[2]: > file:/C:/dev/maven/m2dev/lib/maven-core-2.0-SNAPSHOT.jar > constituent[3]: > file:/C:/dev/maven/m2dev/lib/maven-model-2.0-SNAPSHOT.jar > constituent[4]: > file:/C:/dev/maven/m2dev/lib/maven-monitor-2.0-SNAPSHOT.jar > constituent[5]: > file:/C:/dev/maven/m2dev/lib/maven-plugin-api-2.0-SNAPSHOT.jar > constituent[6]: > file:/C:/dev/maven/m2dev/lib/maven-plugin-descriptor-2.0-SNAPSHOT.jar > constituent[7]: > file:/C:/dev/maven/m2dev/lib/maven-project-2.0-SNAPSHOT.jar > constituent[8]: > file:/C:/dev/maven/m2dev/lib/maven-settings-2.0-SNAPSHOT.jar > constituent[9]: > file:/C:/dev/maven/m2dev/lib/plexus-container-artifact-1.0-alpha-3-SNAPSHOT.jar > constituent[10]: > file:/C:/dev/maven/m2dev/lib/plexus-i18n-1.0-beta-3.jar > constituent[11]: > file:/C:/dev/maven/m2dev/lib/wagon-http-lightweight-1.0-alpha-3-SNAPSHOT.jar > constituent[12]: > file:/C:/dev/maven/m2dev/lib/wagon-provider-api-1.0-alpha-3-SNAPSHOT.jar > --------------------------------------------------- > java.lang.NullPointerException: version was null for > org.apache.maven.plugins:maven-protege-plugin > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:246) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:159) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:77) > at > org.codehaus.plexus.DefaultArtifactEnabledContainer.addComponent(DefaultArtifactEnabledContainer.java:104) > at > org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:282) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:241) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPluginForGoal(DefaultPluginManager.java:195) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executePhase(DefaultLifecycleExecutor.java:436) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:164) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:94) > at > org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:222) > at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) > at > org.apache.maven.cli.MavenCli.main(MavenCli.java:217) > 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:324) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) > at > org.codehaus.classworlds.Launcher.launch(Launcher.java:243) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) > at > org.codehaus.classworlds.Launcher.main(Launcher.java:363) > > > Not sure where to go now? > > Matthew > > --- "J. Matthew Pryor" <[EMAIL PROTECTED]> wrote: > > In general, aside from the noted lack of > > documentation (once again happy to > > provide support here) I think the basic approach is > > the right one. > > > > Writing a Mojo with javadoc tags is definitely nice > > & straightforward. > > > > What I am confused about is how my new plugin > > actually gets called. I > > basically get the whole lifecycle/phase thing, I > > that on the money AFAIAC, > > but what I can't quite get is connecting the new > > plugin with the project > > that needs the code generated. > > > > > The problem is that you need to add > > > <goals><goal><id>bean</id></goal></goals> to the > > plugin > > > configuration to tell Maven to register the goal > > with the phase. > > > > > > > So here are you talking about the plugin or the > > project that uses the > > plugin? > > > > Assuming the later, I did this: > > > > And got this: > > > > [INFO] intermedi8-protege-plugin: using locally > > installed snapshot > > FATAL ERROR: Error executing Maven for a project > > org.apache.maven.reactor.ReactorException: Error > > executing project within > > the reactor > > at > > > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144) > > at > > > org.apache.maven.cli.MavenCli.main(MavenCli.java:217) > > 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:324) > > at > > > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) > > at > > > org.codehaus.classworlds.Launcher.launch(Launcher.java:243) > > at > > > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) > > at > > > org.codehaus.classworlds.Launcher.main(Launcher.java:363) > > Caused by: > > > org.apache.maven.lifecycle.LifecycleExecutionException: > > A goal > > 'protege:bean' was declared in pom.xml, but does not > > exist > > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.processPluginPhases(Defa > > ultLifecycleExecutor.java:293) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.processPluginConfigurati > > on(DefaultLifecycleExecutor.java:240) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLife > > cycleExecutor.java:152) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle > > Executor.java:94) > > at > > > org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:222) > > at > > > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) > > ... 9 more > > > > Very happy to keep plugigng away to get this > > resolved > > > > Matthew > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
