Hi Peter, As Karl noted, bndtools is great to use. If you plan to build with Maven, there's the bundle plugin which uses bndtools to generate the OSGi manifest. I have found this plugin to be indespensable. I also use the Felix SCR annotations to keep from manually managing xml files.
I use Eclipse with m2eclipse and am able to import all of my projects quite easily with dependency resolution. There are a few options to building your final artifact(s). The project I work on is built on Apache Sling and we use the Maven launchpad plugin[1] for building a single artifact that contains all of the bundles we want to deploy. Another option here is to use the Maven assembly plugin which can include all of your dependencies. Using the FileInstall bundle, you can automate deploying single bundles to a running server without restarting. We also use a Maven profile[2] with the Sling plugin to push bundles to a live server. Once you get the initial setup out of the way, starting a new dev on our project entails checking out the source tree, importing everything into Eclipse and running a maven build. With launchpad or assemblies, you can then have a jar to run from the command line. HTH, Carl 1 http://sling.apache.org/site/maven-launchpad-plugin.html 2 https://github.com/sakaiproject/nakamura/blob/master/pom.xml#L132-151 On Fri, Sep 2, 2011 at 3:49 PM, Karl Pauls <[email protected]> wrote: > You might want to have a look at bndtools. > > regards, > > Karl > > On Fri, Sep 2, 2011 at 8:11 PM, Peter <[email protected]> wrote: > > Hello > > > > I am evaluating osgi/felix for use in a bigger project. The technology > per > > se is not much of a concern, > > my biggest concern is the project setup. > > > > At the moment when we have a project, it is possible in almost all our > > projects to set up a running > > development environment un under 30 Minutes. > > > > Most of the time it just consists of checking out, editingone config > file, > > importing the projects/sub projects > > in eclipse, download a tomcat/jetty/etc set it up in eclipse (or > otherwise) > > and the setup is done. > > > > Also of course it is buildable in a Continous Integration environment, > and > > be buildable from the commandline > > (ant/maven/gradle/etc...) > > > > I was wondering if it is possible to have similar setups with osgi. One > of > > my concern is, that the dependencies > > of the project in osgi are not included in the realeased Product but need > to > > be deployed on the server. > > > > So when I change the version of one of the dependencies I have to notify > all > > developers and they have to change > > it manually. which is not very nice. > > > > An incremental deployment would be nice, too (aut deploy only modules > that > > have changed after a recompile) > > > > Are there reasonably simble solutions for this, All the tutorials I see > > online only focus on very specific areas , but > > I have yet to find something that covers all. > > > > > > > > > > Thanks > > > > > > > > Peter > > > > > > > > -- > Karl Pauls > [email protected] > http://twitter.com/karlpauls > http://www.linkedin.com/in/karlpauls > https://profiles.google.com/karlpauls > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
