You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dave Neuer <dn...@BodyMedia.Com> on 2005/08/29 22:55:16 UTC
[m2] Finding a plugin we wrote?
Hi,
In order to be able to reuse test code (see
http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/%3cD1BD
5B28AB3E404F8FC86FB05EB8552D06F3DE@mailserver.office.bodymedia.com%3e),
I've written a plugin which will create a test artifact so that other
projects can depend on that.
However, I'm only able to invoke the plugin if it's in my local
repository and I use the -no-plugin-updates option. Without that option,
I get the following stacktrace:
java.lang.NullPointerException
at
org.apache.maven.artifact.transform.AbstractVersionTransformation.resolv
eVersion(AbstractVersionTransformation.java:133)
at
org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transf
ormForResolve(ReleaseArtifactTransformation.java:51)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau
ltArtifactResolver.java:84)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveRelea
seVersion(DefaultPluginVersionManager.java:566)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
nVersion(DefaultPluginVersionManager.java:99)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
anager.java:192)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:351)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl
e(DefaultLifecycleExecutor.java:314)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
ppings(DefaultLifecycleExecutor.java:242)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:128)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:103)
at
org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:269)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
This, despite the fact that we have our own maven repo set up, and I am
pointing to it in the <pluginRepositories /> section of the POM for the
project that wants to use this.
Can anyone tell me what I need to do to use the plugin without having to
have it hosted at the Apache maven repo?
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org