Le 02/12/14 19:16, Stefan Seelmann a écrit : > Hi Emmanuel, > > there are some problems I identified so far: > > * JDBM 2.0.0-M3 has an invalid manifest.mf, it includes the snapshop > version. I fixed it by using maven-bundle-plugin that generates the > manifest. Hell !
> > * Mavibot 1.0.0-M6 has no manifest at all. Here I also added the > maven-bundle-plugin. great. > > * api-ldap-schema-converter 1.0.0-M26 has the pb that exported > org.commons.lang.exception;version is "2.6", somehow in the tycho build > this package can't be resolved. I removed this explicit version and let > maven-bundle-plugin generate the manifest entry for it which then > results in "[2.6,3)", which works in the tycho build. Ok, good move. > > * api-ldap-client-api 1.0.0-M26 manifest contains wrong export-package names grrrr... > > I'll commit my changes right now. Super ! > > I know that you had problems with using JDBM in Fortress when using > packaging=bundle, as I changed it back to bundle can you please check > what was the problmen with it? You can keep M2 if it works, we will figure out what the pb is with Fortress. Sadly, I'm afraid that we will have to get a new release of ApacheDS if we want the bundle version of JDBM to be used. We *have* to get rid of JDBM as fast as we can ! > > The next problem is that the p2-maven-plugin in the tycho build I'm > using doesn't support snapshot dependencies well. Which is ok, we are not supposed to use SNAPSHOT anyway. > > Sorry but I didn't find time since ApacheCon to continue to work on it, > hopefully next weekend. Me neither, don't worry. I'm back to Studio in order to get the config plugin to work, as we have made some changes in the apacheDS config, and I'm not exactly in a hurry here. The thing is that the error messages we get are everything but explicit about the cause of failure :/ Thanks Stefan !
