[ http://jira.codehaus.org/browse/MNG-1219?page=all ]
     
Brett Porter closed MNG-1219:
-----------------------------

     Assign To: Brett Porter
    Resolution: Won't Fix

sorry, but you must upgrade to the Maven 2.0 RC,

> AssemblyMojo uses unknown methods in plexus-utils
> -------------------------------------------------
>
>          Key: MNG-1219
>          URL: http://jira.codehaus.org/browse/MNG-1219
>      Project: Maven 2
>         Type: Bug
>   Components: maven-assembly-plugin
>     Versions: 2.0-beta-3
>     Reporter: Achim Huegen
>     Assignee: Brett Porter

>
>
> Class AssemblyMojo calls method 
> org.codehaus.plexus.util.FileUtils.getDefaultExcludesAsList()
> that is not present in plexus-utils 1.0.4 which is the latest version 
> available in the ibiblio repository.
> This results in a NoSuchMethodError exception when calling m2 
> assembly:assembly :
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.codehaus.plexus.util.FileUtils.getDefaultExcludesAsList()Ljava/util/List;
>         at 
> org.apache.maven.plugin.assembly.AssemblyMojo.processFileSets(AssemblyMojo.java:401)
>         at 
> org.apache.maven.plugin.assembly.AssemblyMojo.createArchive(AssemblyMojo.java:187)
>         at 
> org.apache.maven.plugin.assembly.AssemblyMojo.execute(AssemblyMojo.java:163)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:517)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:233)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:247)
>         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 found this mail that seems to result from a failed integration build:
> http://www.mail-archive.com/dev@maven.apache.org/msg39297.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to