maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barrie Treloar (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MECLIPSE-194) NPE during eclipse:make-artifacts
Date Wed, 17 Sep 2008 04:32:48 GMT

     [ http://jira.codehaus.org/browse/MECLIPSE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Barrie Treloar closed MECLIPSE-194.
-----------------------------------

    Resolution: Won't Fix

MakeArtifactsMojo has been deprecated in favor of EclipseToMavenMojo.

If you can reproduce with this new mojo please re-open.

> NPE during eclipse:make-artifacts
> ---------------------------------
>
>                 Key: MECLIPSE-194
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-194
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>         Environment: I'm using maven with ubuntu edgy. Running eclipse 3.2.1 with many
installed features/plugins.
>            Reporter: Markus Wolf
>
> During the eclipse:make-artifacts goal is a NPE for the org.apache.geronimo.runtime.v1_1.0.0
plugin with the following stacktrace:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.eclipse.MakeArtifactsMojo.processSingleFile(MakeArtifactsMojo.java:288)
>         at org.apache.maven.plugin.eclipse.MakeArtifactsMojo.execute(MakeArtifactsMojo.java:199)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:219)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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(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)

-- 
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

        

Mime
View raw message