Re: Suggestion about packaging of osgi applications through features maven archetype (SMX4)
Guillaume Nodet <gnodet@...
2009-03-02 07:22:24 GMT
2009/2/27 cmoulliard <cmoulliard@...>:
> I work very hard since a couple of days on SMX4 (kernel, fuse, ... versions)
> and I'm terribly frustrated about the difficulty to package a application
> (bnd, pax construct, ...) top of an OSGI server when we have by example non
> osgi bundles like iText, JasperReport, Hibernate, ... combined with our osgi
> In a development team, the work and workload is distributed between
> different team and developers. In consequence, the packaging of such
> application where we don't EAR, WAR tools is a critical factor that the
> project manager will put in the 'balance' before to take the decision to use
> such technology. Moreover, imagine How you will explain to deployer team of
> big companies (with poor or insufficient knowledge in java, maven, ant, ...
> except maybe if you ask them to copy a file from a folder to another, ...)
> how they will deploy your osgi projects in acceptance and next production
> This is why I would like to make the following suggestion to help the debate
> about OSGI packaging and distribution.
> Obviously, this idea is based on the features (see file :
> org.apache.servicemix.features.cfg) available under SMX4.
> idea : create a maven archetype with the following goal to :
> - Create features file : will create a src folder with an empty feature.xml
> file. By adding in the pom.xml file the module names of the osgi projects,