Hi,
I envision that the OSGi enablement will bring a new foundation for the
Tuscany code base with modularity and formalized SPI visibility enforced by
the OSGi within both the development IDE and maven build.
We are taking a staged approach as I described before and we are making good
progress. I'm not particularly concerned about where the work is being done.
If the community is ready to embrace it (probably when we get into step 5
and 6), we can move it into trunk. It really depends on how comfortable we
are with the fact that the code will be under construction for a period of
time until it's solid, consistent and clean enough to serve as a new
foundation to build other things on top of it.
Thanks,
Raymond
From: Simon Laws
Sent: Thursday, October 30, 2008 3:26 PM
To: dev@tuscany.apache.org
Subject: Re: Update on the Equinox branch
On Thu, Oct 30, 2008 at 5:32 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
At the moment, I still view the sca-equinox branch as "under construction"
phase to build an OSGi-based runtime.
The current stage is to create a good story to develop tuscany modules as
OSGi bundles with the help from Eclipse tooling. We are still working toward
it.
The integration with OSGi validation will expose all kinds of OSGi access
violations. That would create good opportunities for you to help fix these
problems :-).
Then we can start to bring up the existing modules with samples and itests.
I see this stage as the foundation to add new functional pieces.
Thanks,
Raymond
From: ant elder
Sent: Thursday, October 30, 2008 9:12 AM
To: dev@tuscany.apache.org
Subject: Re: Update on the Equinox branch
Ok thanks for the info.
So...now that we've all been invited to come help on the branch what is the
intention for it and where does that leave the existing trunk? Is this still
just something to look at and learn from? Is it at a stage we could try to
merge it into the existing trunk, or should we use this as a base for the
new trunk?
...ant
On Thu, Oct 30, 2008 at 3:48 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
The build is not clean yet. There are test case failures (some due to a
partial merge of the AnyElementProcessor, some due to Policy code
refactoring).
Thanks,
Raymond
From: ant elder
Sent: Thursday, October 30, 2008 7:26 AM
To: dev@tuscany.apache.org
Subject: Re: Update on the Equinox branch
On Wed, Oct 29, 2008 at 6:47 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
We have been working on the sca-equinox branch to create a smooth developer
experience to work with OSGi-enabled Tuscany. There are some good
progresses. We also see some challenges too.
Here are some of the items or goals we are working toward:
1) Make it easy and straightforward for developers to check out the tuscany
modules and load them into Eclipse which has good tooling support for OSGi.
- We are documenting the instructions as some of them require manual steps.
Stay tuned ...
2) Configure the projects in such a way so that Eclipse PDE compiles and
validates our OSGi bundles by honoring the directives in the OSGi manifest.
- We are adding a maven plugin to generate Eclipse plugin .classpath and
.project files so that we can leverage the Eclipse PDE tools
3) Configure maven to build the Tuscany modules using Eclipse compiler and
support the OSGi class visibility.
- We are adding the Eclipse compiler to be used maven compiler plugin (the
compilation is much faster now :-). More work to be done to honor the OSGi
bundle manifest.
4) Build distributions in a much faster fashion (with 1-2 mins) to support
the test automation or bundle development against the 3rd party jars (as
bundles).
- Now we can build the distribution on disk very fast. One of the
distribution can be used to set up the Eclipse target platform.
5) Clean up and fix the test cases and samples to be compiled and run with
OSGi
- We have a few test cases and samples working with OSGi.
6) Bring up the core functions so that other pieces can be ported over or
built on.
- Please come and help. :-).
If you are comfortable to swim in the muddy water, you are very welcome to
jump in and help.
Thanks,
Raymond
What is the expected build status of this, i get build failures in the
assembly-xml and binding-ws-axis2 in the modules folder and then lots of
fails in itests etc. Is that expected?
...ant
Hi Raymond
Great write up, thanks for taking time. I'd like to understand whether you
intend to do just enough work in the branch to prove the principal or
whether you envisage a complete conversion of the Tuscany code base to OSGi?
If the former then it sounds completely reasonable to get to the point, in
the branch, where you/we are convinced it's workable and what that means
before adopting the approach. If the latter then it sounds like you/we are
committing to the approach and seems like something we should be doing in
trunk.
If the answer is you don't know then I would put that in the first category
of "we don't know how it will be picked up and it should be considered an
experiment".
Simon
