Yeah seems like JDom 1.0 which is a transitive dependency of rome. Looks
like JDom2 and JDom (vers 2 and above) does not use the default
package. Any chance we could upgrade to rome 1.5.0 or above? That is
dependent on JDOM 2.0.2.
- Bob
On 9/3/2015 1:35 PM, Yaniv Kunda wrote:
Probably JDom:
http://www.jdom.org/pipermail/jdom-interest/2008-November/016226.html
https://developer.atlassian.com/docs/faq/plugin-framework-faq/using-jdom-in-osgi
On Sep 3, 2015 9:05 PM, "Allison, Timothy B." <[email protected]> wrote:
Interesting, thank you.
I wasn't getting any pointers to the offending class before I removed the
plugin.
Any recommendations on finding the offender?
-----Original Message-----
From: Bob Paulin [mailto:[email protected]]
Sent: Thursday, September 03, 2015 11:21 AM
To: [email protected]
Subject: Re: OSGi exceptions in trunk w Intellij +Osmorc
It's likely one of the embedded dependencies have class files in the
default package. If these classes are not being used they could just be
removed as suggested here:
https://techotom.wordpress.com/2014/10/21/fixing-the-default-package-is-not-permitted-by-the-import-package-syntax-with-maven-bundle-plugin/
Do we know which dependency this might be? I agree that it would be
better if this all worked in Intellij with the Osmorc plugin.
- Bob
On Thu, Sep 3, 2015 at 10:10 AM, Allison, Timothy B. <[email protected]>
wrote:
All,
I'm able to build via Maven without any problem. However, within
Intellij, I'm not able to run any individual unit tests in
tika-parsers or tika-xmp because of this error:
Error:osgi: [tika-parsers] The default package '.' is not permitted by
the Import-Package syntax.
This can be caused by compile errors in Eclipse because Eclipse
creates valid class files regardless of compile errors.
The following package(s) import from the default package null
If I remove Osmorc (the OSGi plugin), all is ok, but that seems like a
really bad idea. Is this something we should fix, or is this
something that I should ignore?
Best,
Tim
