Hello I work on a larger project consisting of cca 210 projects. Most of them are compiled to bundles. There are also projects for GWT, compiled to javascript and projects generating form validation for GWT from annotated DTOs. And also some supporting projects.
Currently we are handling build-time dependency and bootstrap bundle deployment with Apache Ivy. Project artifacts can be published to our Ivy repository. If bundles are published, a script on the ivy repository server will generate obr.xml file for all bundles in the repository, using bindex. We use no Ant or Maven but rather our own builder. It integrates Apache Ivy, Bnd, GWT compiler, JavaDoc, JUnit testing and Bindex on the repository server side. The reason for creating our own building system was many problems and complications of other building systems and we want it to be light and customized just to our needs. Now I need to handle build-time dependencies using OSGi metadata instead of current ivy.xml metadata. I checked Apache Felix Sigil and also there are some plans in current trunk of Apache Ivy, but I don't know how usable is this. I saw also other solutions, like building with headless Eclipse PDE or using Bundle Plugin for Maven or some solutions by PAX, but I have no experience with it and it seems for me not so lightweight. Therefore I am asking you for a help, hint or your experience about how you are solving this dependency problem. We have lot of *.bnd files, one for each bundle project. We also have ivy.xml for every project. I would rather not rewrite all this to some different dependency files if it is not necessary. Also OBR file is our requirement because we are using it runtime to install and update bundles. The build system should also handle custom projects, like mentioned above (GWT, ...). So, which strategy should I take? Thanks a lot in advance! -- Ing. Martin Ždila tel:+421-908-363-848 mailto:[email protected] http://www.zdila.sk/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
