You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nico (JIRA)" <ji...@codehaus.org> on 2008/06/12 15:37:13 UTC
[jira] Created: (MECLIPSE-461) NPE with eclipse:install-plugins
NPE with eclipse:install-plugins
--------------------------------
Key: MECLIPSE-461
URL: http://jira.codehaus.org/browse/MECLIPSE-461
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Environment: XP / mvn 2.0.9
Reporter: Nico
Attachments: hibernate-3.2.6.ga.jar
Hi,
I'm having a NPE when doing mvn eclipse:install-plugins with a bundle that have a dependency with the bundle attached:
[WARNING] Attempting to build MavenProject instance for Artifact (org.escapek:domain-orm:0.1-20080610.073952-1) of type:
jar; constructing POM artifact instead.
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.plugin.eclipse.InstallPluginsMojo.install(InstallPluginsMojo.java:279)
at org.apache.maven.plugin.eclipse.InstallPluginsMojo.execute(InstallPluginsMojo.java:216)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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)
As i've found, this NPE occurs when the bundle has not MANIFEST.MF file. The problem is that this bundle have one.
--
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] Closed: (MECLIPSE-461) NPE with eclipse:install-plugins
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barrie Treloar closed MECLIPSE-461.
-----------------------------------
Resolution: Duplicate
> NPE with eclipse:install-plugins
> --------------------------------
>
> Key: MECLIPSE-461
> URL: http://jira.codehaus.org/browse/MECLIPSE-461
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Environment: XP / mvn 2.0.9
> Reporter: Nico
> Attachments: hibernate-3.2.6.ga.jar
>
>
> Hi,
> I'm having a NPE when doing mvn eclipse:install-plugins with a bundle that have a dependency with the bundle attached:
> [WARNING] Attempting to build MavenProject instance for Artifact (org.escapek:domain-orm:0.1-20080610.073952-1) of type:
> jar; constructing POM artifact instead.
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.maven.plugin.eclipse.InstallPluginsMojo.install(InstallPluginsMojo.java:279)
> at org.apache.maven.plugin.eclipse.InstallPluginsMojo.execute(InstallPluginsMojo.java:216)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a:330)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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)
> As i've found, this NPE occurs when the bundle has not MANIFEST.MF file. The problem is that this bundle have one.
--
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] Commented: (MECLIPSE-461) NPE with eclipse:install-plugins
Posted by "Nico (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138916#action_138916 ]
Nico commented on MECLIPSE-461:
-------------------------------
In fact the NPE doesn't come from the bundle itself but from one of its dependency which was not an OSGi bundle. Because of the error message, I thought the problem was coming from by bundle.
May be some message could be added to tell which bundle failed to be installed.
> NPE with eclipse:install-plugins
> --------------------------------
>
> Key: MECLIPSE-461
> URL: http://jira.codehaus.org/browse/MECLIPSE-461
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Environment: XP / mvn 2.0.9
> Reporter: Nico
> Attachments: hibernate-3.2.6.ga.jar
>
>
> Hi,
> I'm having a NPE when doing mvn eclipse:install-plugins with a bundle that have a dependency with the bundle attached:
> [WARNING] Attempting to build MavenProject instance for Artifact (org.escapek:domain-orm:0.1-20080610.073952-1) of type:
> jar; constructing POM artifact instead.
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.maven.plugin.eclipse.InstallPluginsMojo.install(InstallPluginsMojo.java:279)
> at org.apache.maven.plugin.eclipse.InstallPluginsMojo.execute(InstallPluginsMojo.java:216)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a:330)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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)
> As i've found, this NPE occurs when the bundle has not MANIFEST.MF file. The problem is that this bundle have one.
--
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