my JAVA_HOME varible is pointing to the following address.
C:\Arquivos de programas\Java\jdk1.5.0_05

:D

should I clean my maven's local repository and let it download all the
dependencies again? Should I delete ant from the local repository since the
error is happening because of it?

Thanks in advance. :)

Flávio Oliva

On Tue, Feb 26, 2008 at 5:17 PM, Matt Raible <[EMAIL PROTECTED]> wrote:

> That's a new one that I haven't seen before. Can you verify your
> JAVA_HOME is pointing to a JDK and not a JRE?
>
> Matt
>
> On 2/26/08, Flavio Froes <[EMAIL PROTECTED]> wrote:
> > I tryed to execute the following maven command and I got the following
> > error...
> >
> > [WARNING] repository metadata for: 'snapshot
> > com.mycompany.app:myproject-core:1.
> > 0-SNAPSHOT' could not be retrieved from repository: appfuse due to an
> error:
> > Err
> >  or transferring file
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] FATAL ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] org/apache/tools/ant/taskdefs/optional/Native2Ascii
> >  [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Trace
> > java.lang.NoClassDefFoundError:
> > org/apache/tools/ant/taskdefs/optional/Native2As
> > cii
> >         at
> > org.codehaus.mojo.native2ascii.Native2AsciiMojo.executeAnt(Native2Asc
> >  iiMojo.java:105)
> >         at
> > org.codehaus.mojo.native2ascii.Native2AsciiMojo.execute(Native2AsciiM
> > ojo.java:92)
> >         at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> > nManager.java:447)
> >          at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > ultLifecycleExecutor.java:539)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> > fecycle(DefaultLifecycleExecutor.java:480)
> >          at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
> > cle(DefaultLifecycleExecutor.java:896)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
> > aultLifecycleExecutor.java:739)
> >          at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > ultLifecycleExecutor.java:510)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> > Goal(DefaultLifecycleExecutor.java:493)
> >          at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> > ltLifecycleExecutor.java:463)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> > dleFailures(DefaultLifecycleExecutor.java:311)
> >          at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> > ts(DefaultLifecycleExecutor.java:278)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> > fecycleExecutor.java:143)
> >          at
> > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> >         at
> > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> >         at
> > org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> >         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)
> >
> > is it a bug?
> >
> > Thanks for the attention,
> >
> > Flávio Oliva
> >
>

Reply via email to