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: [email protected]
For additional commands, e-mail: [email protected]
