Le 02/12/14 19:43, Stefan Seelmann a écrit : > Hi all, > > As you know we try to migrate Studio to Tycho build, and always want to > use the latest and greates build of JDBM, Mavibot, API, and ApacheDS. It > happened the released artifacts are no valid OSGi bundles or have > invalid MANIFEST.MF. But even worse is that in the Tycho build the error > messages are not really explicit, it is very hard to find the problem. > > What I dream from is to have some mechanism to avoid that problems and > to identify OSGi related problems early. I don't have enough knowledge > which tools exists out there, so maybe an OSGi export can help.
I'll ask some fellow OSGi open-sourcers to see if they have some good tools/best practices to solve this painfull issue. Obviously, we can't keep going the way we do atm, it's just too much a pain. A single error in a dependency manifest (like the one in ldap-client-api), and you are doomed to serach for yours what's wrong... (I have to say that I wonder how you did found this one, Stefan...) > > First idea I have is to have a test that checks that each single > artifact is a valid bundle. We can add a ant task that does that in our maven build, or add a script in project/resources that does this check. > > Second thing would be some kind of integration test that starts an OSGi > runtime (preferred both Equinox and Felix/Karaf) and installs all > ApacheDS bundles, to verify that all dependencies can be resolved. That would be great to have. > > Third idea would be to even startup ApacheDS in that runtime, but maybe > that requires more work. That precludes teh first two steps have been fulfilled. I'll be back with some more (usefull) ideas later...
