You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Will Horn <wi...@gmail.com> on 2009/05/12 05:34:40 UTC
maven-bundle-plugin:bundleall throws NullPointerException
I have attached a test case where I get an NPE while running the bundleall
goal. The scenario is this:
bundle-all-test: root project, defines dependency on log4j with a version
range and runtime scope in dependencyManagement
proj1: jar project depending on log4j, reducing scope to compile
proj2: pom project depending on proj1
To reproduce, run 'mvn install
org.apache.felix:maven-bundle-plugin:bundleall' in the base directory. I
wanted to post here first since I am unsure if this is a problem with the
maven-bundle-plugin or not. If so, I would be happy to file a bug. If not,
please direct me to the appropriate place to continue my complaint :o)
Thanks so much,
Will
http://www.nabble.com/file/p23495574/bundle-all-test.zip bundle-all-test.zip
--
View this message in context: http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23495574.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: maven-bundle-plugin:bundleall throws NullPointerException
Posted by Will Horn <wi...@gmail.com>.
I don't know why I can't reproduce that. I even re-downloaded the zip I
uploaded and cleared my local repo. I'm using maven 2.0.0 of the plugin and
tried on both 2.0.9 and 2.1.0 of maven.
Stuart McCulloch wrote:
>
> 2009/5/13 Will Horn <wi...@gmail.com>
>
>>
>> Stuart McCulloch wrote:
>> >
>> > this is a separate issue (different to the one in your original
>> testcase
>> > configuration)
>> >
>> > the narrow version range is causing an error inside the Maven
>> dependency
>> > code,
>> > if it's a mistake in the pom we should report it properly (without the
>> > exception trace)
>> > but if it's a problem in the dependency code then we might need to work
>> > around it
>> >
>> > feel free to open a separate issue for this, as it's a different
>> problem
>> >
>> Ok. This is actually the issue I was talking about and was intending the
>> test case to reproduce :o) I have been able to further reproduce it in a
>> JUnit test for maven-dependency-tree
>> http://jira.codehaus.org/browse/MNG-4159 so I don't think it is a
>> bundleall
>> problem anymore. There is a workaround - for me to change the strict
>> version range to a loose one, i.e. from "[1.2.13]" to "1.2.13", but that
>> breaks the maven "rules" for my project.
>>
>> I'm not sure I understand the other issue (the first one) you are talking
>> about. The only NPE I have seen is the one in the stack trace I pasted
>> into
>> my last post. Maybe we should close my bug (FELIX-1148) and open a new
>> one
>> for the first issue you saw. But what was it that you saw?
>>
>
> when running the bundleall goal from the top root project I get:
>
> at
> org.apache.maven.shared.osgi.DefaultMaven2OsgiConverter.getBundleSymbolicName(DefaultMaven2OsgiConver
> ter.java:105)
> at
> org.apache.maven.shared.osgi.DefaultMaven2OsgiConverter.getBundleFileName(DefaultMaven2OsgiConverter.
> java:237)
> at
> org.apache.felix.bundleplugin.BundleAllPlugin.getBundleName(BundleAllPlugin.java:437)
> at
> org.apache.felix.bundleplugin.BundleAllPlugin.getOutputFile(BundleAllPlugin.java:544)
> at
> org.apache.felix.bundleplugin.BundleAllPlugin.getBuiltFile(BundleAllPlugin.java:470)
> at
> org.apache.felix.bundleplugin.BundleAllPlugin.alreadyBundled(BundleAllPlugin.java:443)
> at
> org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:179)
> at
> org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:165)
> at
> org.apache.felix.bundleplugin.BundleAllPlugin.execute(BundleAllPlugin.java:152)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.ja
> va:553)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExec
> utor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java
> :332)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> 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)
> Caused by: java.util.zip.ZipException: error in opening zip file
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.<init>(ZipFile.java:203)
> at java.util.jar.JarFile.<init>(JarFile.java:132)
> at java.util.jar.JarFile.<init>(JarFile.java:112)
> at
> org.apache.maven.shared.osgi.DefaultMaven2OsgiConverter.getBundleSymbolicName(DefaultMaven2OsgiConver
> ter.java:88)
> ... 26 more
>
> because it tries to treat the pom as a jarfile, which is of course
> wrong...
>
> Thanks for your help with this,
>> Will
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23507035.html
>> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>> --
> Cheers, Stuart
>
>
--
View this message in context: http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23508287.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: maven-bundle-plugin:bundleall throws NullPointerException
Posted by Stuart McCulloch <mc...@gmail.com>.
2009/5/13 Will Horn <wi...@gmail.com>
>
> Stuart McCulloch wrote:
> >
> > this is a separate issue (different to the one in your original testcase
> > configuration)
> >
> > the narrow version range is causing an error inside the Maven dependency
> > code,
> > if it's a mistake in the pom we should report it properly (without the
> > exception trace)
> > but if it's a problem in the dependency code then we might need to work
> > around it
> >
> > feel free to open a separate issue for this, as it's a different problem
> >
> Ok. This is actually the issue I was talking about and was intending the
> test case to reproduce :o) I have been able to further reproduce it in a
> JUnit test for maven-dependency-tree
> http://jira.codehaus.org/browse/MNG-4159 so I don't think it is a
> bundleall
> problem anymore. There is a workaround - for me to change the strict
> version range to a loose one, i.e. from "[1.2.13]" to "1.2.13", but that
> breaks the maven "rules" for my project.
>
> I'm not sure I understand the other issue (the first one) you are talking
> about. The only NPE I have seen is the one in the stack trace I pasted
> into
> my last post. Maybe we should close my bug (FELIX-1148) and open a new one
> for the first issue you saw. But what was it that you saw?
>
when running the bundleall goal from the top root project I get:
at
org.apache.maven.shared.osgi.DefaultMaven2OsgiConverter.getBundleSymbolicName(DefaultMaven2OsgiConver
ter.java:105)
at
org.apache.maven.shared.osgi.DefaultMaven2OsgiConverter.getBundleFileName(DefaultMaven2OsgiConverter.
java:237)
at
org.apache.felix.bundleplugin.BundleAllPlugin.getBundleName(BundleAllPlugin.java:437)
at
org.apache.felix.bundleplugin.BundleAllPlugin.getOutputFile(BundleAllPlugin.java:544)
at
org.apache.felix.bundleplugin.BundleAllPlugin.getBuiltFile(BundleAllPlugin.java:470)
at
org.apache.felix.bundleplugin.BundleAllPlugin.alreadyBundled(BundleAllPlugin.java:443)
at
org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:179)
at
org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:165)
at
org.apache.felix.bundleplugin.BundleAllPlugin.execute(BundleAllPlugin.java:152)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.ja
va:553)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExec
utor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java
:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
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)
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:203)
at java.util.jar.JarFile.<init>(JarFile.java:132)
at java.util.jar.JarFile.<init>(JarFile.java:112)
at
org.apache.maven.shared.osgi.DefaultMaven2OsgiConverter.getBundleSymbolicName(DefaultMaven2OsgiConver
ter.java:88)
... 26 more
because it tries to treat the pom as a jarfile, which is of course wrong...
Thanks for your help with this,
> Will
>
> --
> View this message in context:
> http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23507035.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
> --
Cheers, Stuart
Re: maven-bundle-plugin:bundleall throws NullPointerException
Posted by Will Horn <wi...@gmail.com>.
Stuart McCulloch wrote:
>
> this is a separate issue (different to the one in your original testcase
> configuration)
>
> the narrow version range is causing an error inside the Maven dependency
> code,
> if it's a mistake in the pom we should report it properly (without the
> exception trace)
> but if it's a problem in the dependency code then we might need to work
> around it
>
> feel free to open a separate issue for this, as it's a different problem
>
Ok. This is actually the issue I was talking about and was intending the
test case to reproduce :o) I have been able to further reproduce it in a
JUnit test for maven-dependency-tree
http://jira.codehaus.org/browse/MNG-4159 so I don't think it is a bundleall
problem anymore. There is a workaround - for me to change the strict
version range to a loose one, i.e. from "[1.2.13]" to "1.2.13", but that
breaks the maven "rules" for my project.
I'm not sure I understand the other issue (the first one) you are talking
about. The only NPE I have seen is the one in the stack trace I pasted into
my last post. Maybe we should close my bug (FELIX-1148) and open a new one
for the first issue you saw. But what was it that you saw?
Thanks for your help with this,
Will
--
View this message in context: http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23507035.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: maven-bundle-plugin:bundleall throws NullPointerException
Posted by Stuart McCulloch <mc...@gmail.com>.
2009/5/13 Will Horn <wi...@gmail.com>
> Stuart McCulloch wrote:
> >
> > the "bundleall" goal assumes you're running it against a jar/bundle
> > project
> > - it should be more forgiving
> >
> Is this all that is going on? If I change proj2 to be a jar project, I get
> the same exception. The exception happens in the dependency tree builder
> [1]. To me (disclaimer: not familiar at all with the code), there seems to
> be an issue with version ranges.
>
this is a separate issue (different to the one in your original testcase
configuration)
the narrow version range is causing an error inside the Maven dependency
code,
if it's a mistake in the pom we should report it properly (without the
exception trace)
but if it's a problem in the dependency code then we might need to work
around it
feel free to open a separate issue for this, as it's a different problem
[ the bundleall goal has not had much testing against reactor projects or
projects
with version ranges, as it was originally designed for a simple project
use-case ]
I created a bug https://issues.apache.org/jira/browse/FELIX-1148 and we can
> continue the discussion there. I'd be happy to investigate/work on a
> patch,
> but I'm not what to change in the bundle plugin to avoid the exception.
>
> -Will
>
> [1] java.lang.NullPointerException: version was null for log4j:log4j
> at
>
> org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362)
> at
> org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225)
> at
>
> org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.manageArtifactScope(DependencyTreeResolutionListener.java:358)
> at
>
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:547)
> at
>
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:500)
> at
>
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.manageArtifact(DefaultArtifactCollector.java:438)
> at
>
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:307)
> at
>
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:408)
> at
>
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76)
> at
>
> org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102)
> at
>
> org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:196)
> at
>
> org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:165)
> at
>
> org.apache.felix.bundleplugin.BundleAllPlugin.execute(BundleAllPlugin.java:152)
> 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.java: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)
> --
> View this message in context:
> http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23506238.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
Cheers, Stuart
Re: maven-bundle-plugin:bundleall throws NullPointerException
Posted by Will Horn <wi...@gmail.com>.
Stuart McCulloch wrote:
>
> the "bundleall" goal assumes you're running it against a jar/bundle
> project
> - it should be more forgiving
>
Is this all that is going on? If I change proj2 to be a jar project, I get
the same exception. The exception happens in the dependency tree builder
[1]. To me (disclaimer: not familiar at all with the code), there seems to
be an issue with version ranges.
I created a bug https://issues.apache.org/jira/browse/FELIX-1148 and we can
continue the discussion there. I'd be happy to investigate/work on a patch,
but I'm not what to change in the bundle plugin to avoid the exception.
-Will
[1] java.lang.NullPointerException: version was null for log4j:log4j
at
org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362)
at
org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225)
at
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.manageArtifactScope(DependencyTreeResolutionListener.java:358)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:547)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(DefaultArtifactCollector.java:500)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.manageArtifact(DefaultArtifactCollector.java:438)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:307)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:408)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76)
at
org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:102)
at
org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:196)
at
org.apache.felix.bundleplugin.BundleAllPlugin.bundleAll(BundleAllPlugin.java:165)
at
org.apache.felix.bundleplugin.BundleAllPlugin.execute(BundleAllPlugin.java:152)
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.java: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)
--
View this message in context: http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23506238.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: maven-bundle-plugin:bundleall throws NullPointerException
Posted by Stuart McCulloch <mc...@gmail.com>.
2009/5/12 Will Horn <wi...@gmail.com>
>
> I have attached a test case where I get an NPE while running the bundleall
> goal. The scenario is this:
>
> bundle-all-test: root project, defines dependency on log4j with a version
> range and runtime scope in dependencyManagement
>
> proj1: jar project depending on log4j, reducing scope to compile
>
> proj2: pom project depending on proj1
>
> To reproduce, run 'mvn install
> org.apache.felix:maven-bundle-plugin:bundleall' in the base directory. I
> wanted to post here first since I am unsure if this is a problem with the
> maven-bundle-plugin or not. If so, I would be happy to file a bug. If
> not,
> please direct me to the appropriate place to continue my complaint :o)
>
looks like a bug to me (and the same exception occurs with previous
releases, so it's not a regression)
the "bundleall" goal assumes you're running it against a jar/bundle project
- it should be more forgiving
please open an issue at http://issues.apache.org/jira/browse/FELIX along
with a patch if you have one ;)
> Thanks so much,
> Will
>
> http://www.nabble.com/file/p23495574/bundle-all-test.zipbundle-all-test.zip
> --
> View this message in context:
> http://www.nabble.com/maven-bundle-plugin%3Abundleall-throws-NullPointerException-tp23495574p23495574.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
--
Cheers, Stuart