You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <de...@tuscany.apache.org> on 2009/03/30 15:00:50 UTC

[jira] Closed: (TUSCANY-2872) Maven Bundle Plugin throws NPE when a dependent non-OSGI jar has no manifest

     [ https://issues.apache.org/jira/browse/TUSCANY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ant elder closed TUSCANY-2872.
------------------------------

    Resolution: Fixed

Applied and now included in the latest release of the plugin

> Maven Bundle Plugin throws NPE when a dependent non-OSGI jar has no manifest
> ----------------------------------------------------------------------------
>
>                 Key: TUSCANY-2872
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2872
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Build System
>            Reporter: Hasan Ceylan
>            Assignee: ant elder
>         Attachments: tuscany.patch
>
>
> Here's the stack trace:
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:584)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
> 	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:301)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:616)
> 	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)
> Caused by: org.apache.maven.plugin.MojoExecutionException
> 	at org.apache.tuscany.maven.bundle.plugin.ModuleBundlesBuildMojo.execute(ModuleBundlesBuildMojo.java:538)
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> 	... 16 more
> Caused by: java.lang.NullPointerException
> 	at org.apache.tuscany.maven.bundle.plugin.BundleUtil.getBundleSymbolicName(BundleUtil.java:76)
> 	at org.apache.tuscany.maven.bundle.plugin.ModuleBundlesBuildMojo.execute(ModuleBundlesBuildMojo.java:397)
> 	... 18 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.