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 >> https://developer.atlassian.com/docs/faq/plugin-framework-faq/using-jdom-in-osgi >> 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. > >> 5) OSGi does not really like SNAPSHOT a lot. I still have to firgure >> oiut how to use them (there must be a solution, I just didn't had time >> to investigate too much) > Right, instead of -SNAPSHOT one has to use .qualifier. The > maven-bundle-plugin should convert that automatically. But I agree it is > confusing. It's not confusing, it's completely broken. The OSGi guys are totally fucked up here. Just because their tools are expecting the version to always increase (compared to Maven where x.y.z-SNAPSHOT < x.y.z), you can't use SNAPSHOTS. And they rejected the proposal to include SNAPSHOT versionning scheme for stupid reasons... Anyway, at some point in the future, there will be an epiphany on thir side, or they will lose the battle for something smarter. May be Java 9 or Java 10 will make then OSGi completely useless... How to transform a good idea to a bad one by simply not fixing their tools !
