That seems to have fixed the prereq, but now when I gen the site
(maven-dependency-plugin), I get an exception. I ran again with -U to
double check I have the latest snapshots of everything.
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO]
org.apache.maven.plugin.descriptor.Parameter.setImplementation(Ljava/lan
g
/String;)V
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NoSuchMethodError:
org.apache.maven.plugin.descriptor.Parameter.setImp
lementation(Ljava/lang/String;)V
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtrac
tor.extractParameters(JavaMojoDescriptorExtractor.java:431)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtrac
tor.createMojoDescriptor(JavaMojoDescriptorExtractor.java:303)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtrac
tor.execute(JavaMojoDescriptorExtractor.java:500)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePlug
inDescriptor(DefaultMojoScanner.java:69)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(Abstract
GeneratorMojo.java:103)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
cle(DefaultLifecycleExecutor.java:891)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
aultLifecycleExecutor.java:734)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:525)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.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(DelegatingMethodAcces
sorImpl.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)
[INFO]
------------------------------------------------------------------------
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 2:56 PM
To: Maven Developers List
Subject: Re: parent 4-snapshot
I'm deploying a snapshot of the plugin plugin now which hopefully
resolves that.
On 07/11/2006, at 6:50 AM, Brian E. Fox wrote:
> Brett, the 4-SNAPSHOT version still seems to want Maven 2.0.5.
>
> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 27, 2006 6:51 PM
> To: Maven Developers List
> Subject: Re: parent 4-snapshot
>
>
> On 26/10/2006, at 7:02 PM, Brian E. Fox wrote:
>
>> All the plugins where updated to use the new snapshot 4 of the
>> parent.
>> This includes versions of maven-plugin-plugin that need 2.0.5-
>> SNAPSHOT.
>
> No, I fixed that.
>
>> Is there a major reason why the plugins must use this version? I'm
>> finishing up the plugin but also using it internally in production
>> and
>
>> can't be dependant on 2.0.5 until it's released.
>
> Documentation reasons.
>
> They only depend on the plugin tools, which can be released whenever.
>
> - Brett
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
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]
