directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <>
Subject Re: [Studio] heads up
Date Sun, 21 Dec 2014 08:28:13 GMT
Le 21/12/14 09:04, Emmanuel Lécharny a écrit :
> Le 20/12/14 20:28, Stefan Seelmann a écrit :
>>> 4) I have tried with the latest LDAP-API SNAPSHOT, but then I'm facing
>>> another issue : there is one dependency that has some class at the top
>>> level, which is stricly verboten. I still have to figure out which one
>>> (see
>>> for more insight on why could be the pb).
>> Which dependency is that? jdom? Do we use jdom? I thought we only use
>> dom4j, but that is also a problematic dependency.
> We don't use jdom, I just posted the URL to expose the potential pb if
> there is a jar with a class on teh top level.



Have a look at that :

It says : "You probably have Eclipse open on this project" (you bet I
have !) "and there are compile errors" (MANY !). "Eclipse still outputs
a class file for java sources with compile errors" (Stupid eclipse...)
"but these classesare weird. In particular they depend on the default
package "." " WHAT????

Yes, you get it now : Eclipse creates weird .class files into the
default package, and when you run mavn-bundle-plugin, it will throw
error messages because if this stupid useless class being around.

The solution :

mvn -f pom-first.xml ***clean*** bundle:manifest

The "clean" phase will remove all the .class files and then, the
MANIFEST.MF will be correctly built...

I can't believe it :/

View raw message