I just want to throw my 0.02 cents here... I haven't made up my mind if these multiple distros are going to really help or not, but once we implement this, we will need very clear user documentation, to avoid confusion. We should also state very clear the limitations, otherwise people will start to download distribution A and will start to ask how to add binding X, etc...
Also, we should double check all modules that have derby db in SVN and make that created by the build process. This would also help on reducing the size of distributions. On Jan 24, 2008 9:59 AM, Raymond Feng <[EMAIL PROTECTED]> wrote: > There are two tools in Apache felix can probably help: > > 1) mangen - OSGi Bundle Manifest generator > http://cwiki.apache.org/confluence/display/FELIX/Bundle+Manifest+Generator+%28mangen%29 > > We could use it to create OSGi bundles out of the existing jars. > > 2) Maven Bundle Plugin 1.2.0 > > We could use it to automate the generating OSGi manifests as part of the > maven build. > > Thanks, > Raymond > > ----- Original Message ----- > From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]> > To: <tuscany-dev@ws.apache.org> > > Sent: Thursday, January 24, 2008 9:46 AM > Subject: Re: Distribution zips and what they contain, was: SCA runtimes > > > > Rajini Sivaram wrote: > >> Would it be possible to add an OSGi manifest header into these zip files > >> so > >> that the zips can be directly installed into an OSGi runtime? The entries > >> will not have any impact when used without OSGi. > > > > +1 > > > > The only issue would be the > >> creation of these entries. We have two options - 1)generate them > >> automatically during the build process using the maven-bundle-plugin, > > > > +1 or another automated process > > > > or 2) > >> hand-code a manifest file. It would be easiest to go with option 2) to > >> start > >> with to avoid any build issues. If it becomes difficult to maintain the > >> hand-coded manifest file, we can move to option 1). > > > > I'd suggest to write it by hand once to define the target to automate, > > then automate its generation right away. > > > >> The manifest entries will contain bundle names, versions, imported > >> packages, > >> exported packages and a bundle classpath(which lists jars contained > >> inside > >> the zip). > > > > Can you post an example or put it in SVN? Thanks. > > > > -- > > Jean-Sebastien > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
