You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ricardo Catalfo (JIRA)" <ji...@codehaus.org> on 2010/03/04 19:13:56 UTC
[jira] Created: (MECLIPSE-643) java.lang.NullPointerException
(EclipsePlugin.isAvailableAsAWorkspaceProject)
java.lang.NullPointerException (EclipsePlugin.isAvailableAsAWorkspaceProject)
-----------------------------------------------------------------------------
Key: MECLIPSE-643
URL: http://jira.codehaus.org/browse/MECLIPSE-643
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Workspace settings
Affects Versions: 2.7
Environment: C:\Documents and Settings\catalrc\WorkspaceXYZ\FlexGN>mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_16
Java home: C:\Program Files\Java\jdk1.6.0_16\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Reporter: Ricardo Catalfo
Priority: Minor
I found an issue when executing mvn eclipse:eclipse on my workspace. Below is the stack trace and the reason of it:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] ------------------------------------------------------------------------
[INFO] Building FlexGN
[INFO] task-segment: [eclipse:eclipse]
[INFO] ------------------------------------------------------------------------
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse {execution: default-cli}]
[INFO] Using Eclipse Workspace: C:\Documents and Settings\catalrc\WorkspaceXYZ
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.plugin.eclipse.EclipsePlugin.isAvailableAsAWorkspaceProject(EclipsePlugin.java:1889)
at org.apache.maven.plugin.eclipse.EclipsePlugin.useProjectReference(EclipsePlugin.java:1932)
at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution(AbstractIdeSupportMojo.java:683)
at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:507)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
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] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Thu Mar 04 12:54:48 EST 2010
[INFO] Final Memory: 7M/15M
[INFO] ------------------------------------------------------------------------
---
The pom.xml for this project (FlexGN) was fine. However, I detected that another project in the same workspace had the following pom.xml:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
</project>
I don't know how I got this file, I guess because we are migrating our projects to Maven.
Solution / Workaround:
The "NullPointerException...isAvailableAsAWorkspaceProject" issue with the plugin is gone when you complete the minimal POM configuration (it also works when you delete or rename the file).
However,
I don't see why an invalid pom.xml in a particular project has to prevent me on executing this plugin in ANY PROJECT of the same workspace.
Thanks!
--
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
[jira] (MECLIPSE-643) java.lang.NullPointerException
(EclipsePlugin.isAvailableAsAWorkspaceProject)
Posted by "Stefan Cordes (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313109#comment-313109 ]
Stefan Cordes commented on MECLIPSE-643:
----------------------------------------
You can find the "invalid" pom.xml by executing
{{mvn -X eclipse:eclipse}}
and searching for "null" in lines with "found workspace artefact".
The line above (starting with " read workpsace project") shows you the location of the pom.xml without groupId/artifactId.
> java.lang.NullPointerException (EclipsePlugin.isAvailableAsAWorkspaceProject)
> -----------------------------------------------------------------------------
>
> Key: MECLIPSE-643
> URL: https://jira.codehaus.org/browse/MECLIPSE-643
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Workspace settings
> Affects Versions: 2.7
> Environment: C:\Documents and Settings\catalrc\WorkspaceXYZ\FlexGN>mvn -v
> Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_16
> Java home: C:\Program Files\Java\jdk1.6.0_16\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Ricardo Catalfo
> Priority: Minor
>
> I found an issue when executing mvn eclipse:eclipse on my workspace. Below is the stack trace and the reason of it:
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building FlexGN
> [INFO] task-segment: [eclipse:eclipse]
> [INFO] ------------------------------------------------------------------------
> [INFO] Preparing eclipse:eclipse
> [INFO] No goals needed for project - skipping
> [INFO] [eclipse:eclipse {execution: default-cli}]
> [INFO] Using Eclipse Workspace: C:\Documents and Settings\catalrc\WorkspaceXYZ
> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.maven.plugin.eclipse.EclipsePlugin.isAvailableAsAWorkspaceProject(EclipsePlugin.java:1889)
> at org.apache.maven.plugin.eclipse.EclipsePlugin.useProjectReference(EclipsePlugin.java:1932)
> at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution(AbstractIdeSupportMojo.java:683)
> at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:507)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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:597)
> 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] ------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Mar 04 12:54:48 EST 2010
> [INFO] Final Memory: 7M/15M
> [INFO] ------------------------------------------------------------------------
> ---
> The pom.xml for this project (FlexGN) was fine. However, I detected that another project in the same workspace had the following pom.xml:
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> </project>
> I don't know how I got this file, I guess because we are migrating our projects to Maven.
> Solution / Workaround:
> The "NullPointerException...isAvailableAsAWorkspaceProject" issue with the plugin is gone when you complete the minimal POM configuration (it also works when you delete or rename the file).
> However,
> I don't see why an invalid pom.xml in a particular project has to prevent me on executing this plugin in ANY PROJECT of the same workspace.
> Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-643) java.lang.NullPointerException
(EclipsePlugin.isAvailableAsAWorkspaceProject)
Posted by "Markus KARG (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287050#comment-287050 ]
Markus KARG commented on MECLIPSE-643:
--------------------------------------
Confirm bug happens in my environment, too. Is a blocker for me, don't know how to run eclipse:eclipse without getting NPE. JDK 1.7.0_02, Maven 3.0.3, Win 7 (32 Bit), de_DE. I would rate this as critical, as in my environment there are rather lots of projects, so I have to check ALL of them now... :-(
> java.lang.NullPointerException (EclipsePlugin.isAvailableAsAWorkspaceProject)
> -----------------------------------------------------------------------------
>
> Key: MECLIPSE-643
> URL: https://jira.codehaus.org/browse/MECLIPSE-643
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Workspace settings
> Affects Versions: 2.7
> Environment: C:\Documents and Settings\catalrc\WorkspaceXYZ\FlexGN>mvn -v
> Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_16
> Java home: C:\Program Files\Java\jdk1.6.0_16\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Ricardo Catalfo
> Priority: Minor
>
> I found an issue when executing mvn eclipse:eclipse on my workspace. Below is the stack trace and the reason of it:
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building FlexGN
> [INFO] task-segment: [eclipse:eclipse]
> [INFO] ------------------------------------------------------------------------
> [INFO] Preparing eclipse:eclipse
> [INFO] No goals needed for project - skipping
> [INFO] [eclipse:eclipse {execution: default-cli}]
> [INFO] Using Eclipse Workspace: C:\Documents and Settings\catalrc\WorkspaceXYZ
> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.maven.plugin.eclipse.EclipsePlugin.isAvailableAsAWorkspaceProject(EclipsePlugin.java:1889)
> at org.apache.maven.plugin.eclipse.EclipsePlugin.useProjectReference(EclipsePlugin.java:1932)
> at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution(AbstractIdeSupportMojo.java:683)
> at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:507)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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:597)
> 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] ------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Mar 04 12:54:48 EST 2010
> [INFO] Final Memory: 7M/15M
> [INFO] ------------------------------------------------------------------------
> ---
> The pom.xml for this project (FlexGN) was fine. However, I detected that another project in the same workspace had the following pom.xml:
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> </project>
> I don't know how I got this file, I guess because we are migrating our projects to Maven.
> Solution / Workaround:
> The "NullPointerException...isAvailableAsAWorkspaceProject" issue with the plugin is gone when you complete the minimal POM configuration (it also works when you delete or rename the file).
> However,
> I don't see why an invalid pom.xml in a particular project has to prevent me on executing this plugin in ANY PROJECT of the same workspace.
> Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-643) java.lang.NullPointerException
(EclipsePlugin.isAvailableAsAWorkspaceProject)
Posted by "Endre Moen (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300385#comment-300385 ]
Endre Moen commented on MECLIPSE-643:
-------------------------------------
I am also getting this error. Running with -X option and it looks like other projects are scanned too. Why is eclipse:eclipse scanning other projects when current pom has no parents defined?
> java.lang.NullPointerException (EclipsePlugin.isAvailableAsAWorkspaceProject)
> -----------------------------------------------------------------------------
>
> Key: MECLIPSE-643
> URL: https://jira.codehaus.org/browse/MECLIPSE-643
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Workspace settings
> Affects Versions: 2.7
> Environment: C:\Documents and Settings\catalrc\WorkspaceXYZ\FlexGN>mvn -v
> Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_16
> Java home: C:\Program Files\Java\jdk1.6.0_16\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Ricardo Catalfo
> Priority: Minor
>
> I found an issue when executing mvn eclipse:eclipse on my workspace. Below is the stack trace and the reason of it:
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building FlexGN
> [INFO] task-segment: [eclipse:eclipse]
> [INFO] ------------------------------------------------------------------------
> [INFO] Preparing eclipse:eclipse
> [INFO] No goals needed for project - skipping
> [INFO] [eclipse:eclipse {execution: default-cli}]
> [INFO] Using Eclipse Workspace: C:\Documents and Settings\catalrc\WorkspaceXYZ
> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.maven.plugin.eclipse.EclipsePlugin.isAvailableAsAWorkspaceProject(EclipsePlugin.java:1889)
> at org.apache.maven.plugin.eclipse.EclipsePlugin.useProjectReference(EclipsePlugin.java:1932)
> at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution(AbstractIdeSupportMojo.java:683)
> at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:507)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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:597)
> 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] ------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Mar 04 12:54:48 EST 2010
> [INFO] Final Memory: 7M/15M
> [INFO] ------------------------------------------------------------------------
> ---
> The pom.xml for this project (FlexGN) was fine. However, I detected that another project in the same workspace had the following pom.xml:
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> </project>
> I don't know how I got this file, I guess because we are migrating our projects to Maven.
> Solution / Workaround:
> The "NullPointerException...isAvailableAsAWorkspaceProject" issue with the plugin is gone when you complete the minimal POM configuration (it also works when you delete or rename the file).
> However,
> I don't see why an invalid pom.xml in a particular project has to prevent me on executing this plugin in ANY PROJECT of the same workspace.
> Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira