Eclipse Community Forums: Equinox » serverside OSGI build coming?

Help

Home

Home » Eclipse Projects » Equinox » serverside OSGI build coming?

Show: Today's Messages :: Show Polls :: Message Navigator

serverside OSGI build coming? [message #64484]

Mon, 03 April 2006 23:58

Jim DAnjou

Messages: 25
Registered: July 2009

Junior Member

What is the outlook for a server-OSGI build inclusion in the equinox
builds? Right now we pull from head from time to time code that might be
in an unknown state and see if it works or doesn't regress.

I realize this is an incubator project and should be allowed to run faster
and loser than other projects.In lieu of a build could the server-OSGI
bundles get tagged (ordinary CVS version tags) when an appropriate code
development checkpoint has been reached. That would at least give is a
link to the source code behind the binary code we are running.

In our case we are starting to bring the server-osgi into the mainstream
of our development code and it has been included in our own builds. We
have some exposure if we don't have good traceability to the origin of the
server-osgi code we are using.

Thanks!

Jim D'Anjou

P.S. This is good stuff!

Report message to a moderator

Re: serverside OSGI build coming? [message #64645 is a reply to message #64484]

Wed, 05 April 2006 21:42

Eclipse User

Originally posted by: skaegi.sympatico.ca

Hi Jim,

> What is the outlook for a server-OSGI build inclusion in the equinox
> builds? Right now we pull from head from time to time code that might be
> in an unknown state and see if it works or doesn't regress.
I think the outlook is pretty good.
Right now all the server-side bundles are available for download at the
equinox download site but are labeled HEAD for their qualifier.
Perhaps this is just the way the incubator bundles are handled, but I'll try
to find out what's involved and see if we can't have the build time used
instead.
I'll update when I know more.

> I realize this is an incubator project and should be allowed to run faster
> and loser than other projects.In lieu of a build could the server-OSGI
> bundles get tagged (ordinary CVS version tags) when an appropriate code
> development checkpoint has been reached. That would at least give is a
> link to the source code behind the binary code we are running.
That's a good idea. From here on in I'm not really expecting any substantial
changes leading up to 3.2 so for purposes of integration tonight's build is
a good candidate for integration against M6 and later.
..
I'm also updating the website over the next few days to reflect the various
naming and API changes that have happened leading up to M6.
I'll formally add a label.when I rebuild.

> In our case we are starting to bring the server-osgi into the mainstream
> of our development code and it has been included in our own builds. We
> have some exposure if we don't have good traceability to the origin of the
> server-osgi code we are using.
I completely understand. I'll try to get something better in place.
Eventually I hope the server-side stuff will just follow the rest of equinox
and the main platform.
--
This just handles the raw bundle building.
If you or anyone are also looking to build a webapp/WAR take a look at the
webappBuilder.xml script in
org.eclipse.equinox.servlet.bridge.launcher/scripts. The script is primarily
geared for doing a build in the IDE however by overriding various properties
it might also be useful for headless builds. I'd be interested in any
feedback/ideas.

-Simon

Report message to a moderator