You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Raymond Feng <en...@gmail.com> on 2008/10/29 19:47:04 UTC
Update on the Equinox branch
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
Re: Update on the Equinox branch
Posted by Dan Becker <da...@gmail.com>.
Agreed, this is a great summary. Thanks!
Luciano Resende wrote:
> This is a great summary Raymond.
>
> [1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Development+Guide+(OSGI)
>
> On Wed, Oct 29, 2008 at 11:47 AM, Raymond Feng <en...@gmail.com> wrote:
>> 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. :-).
--
Thanks, Dan Becker
Re: Update on the Equinox branch
Posted by Luciano Resende <lu...@gmail.com>.
This is a great summary Raymond.
I have started with some cleanup and stabilization of the code, and I
have documented my experience on getting my development environment
ready in the "OSGI Development Guide" [1]. Let's all try to keep it
up to date and use it as a reference for others that want to come and
help.
[1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Development+Guide+(OSGI)
On Wed, Oct 29, 2008 at 11:47 AM, Raymond Feng <en...@gmail.com> 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
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Update on the Equinox branch
Posted by Luciano Resende <lu...@gmail.com>.
This is still expected, if you look in the guide, here is how I was
able to make progress :
1.Build the tuscany eclipse compiler
cd tools\maven\maven-eclipse-compiler
mvn clean install
2.Full build without execution of test cases
cd ..\..\..
mvn -Dmaven.test.skip=true -fae clean install
3.Build small distribution
cd distribution
mvn -Dmaven.test.skip=true -fae clean install
I guess the next things we need are :
- Get the modules tests executing ok
- Get all the samples updated to compile and execute
On Thu, Oct 30, 2008 at 7:26 AM, ant elder <an...@gmail.com> wrote:
>
>
> On Wed, Oct 29, 2008 at 6:47 PM, Raymond Feng <en...@gmail.com> 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
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Update on the Equinox branch
Posted by Simon Laws <si...@googlemail.com>.
On Tue, Nov 4, 2008 at 9:49 PM, Luciano Resende <lu...@gmail.com>wrote:
> On Tue, Nov 4, 2008 at 1:45 PM, ant elder <an...@apache.org> wrote:
> >
> >
> > On Tue, Nov 4, 2008 at 9:32 PM, Luciano Resende <lu...@gmail.com>
> > wrote:
> >>
> >> On Tue, Nov 4, 2008 at 11:44 AM, Raymond Feng <en...@gmail.com>
> wrote:
> >> > Hi,
> >> >
> >> > I like the idea to build a new trunk from scratch for the 2.x stream
> >> > (OASIS)
> >> > and harvest things from the sca-equinox branch and 1.x branch (OSOA).
> >> >
> >> > Now we have reasonable parts covering items a, b, c, d on Sebstien's
> >> > list. I
> >> > see it as a good story for developers to develop Tuscany modules as
> OSGi
> >> > bundles with the help from Eclipse PDE. The missing feature is the
> maven
> >> > eclipse compiler doesn't report the OSGi violations yet.
> >> >
> >> > Should we start to branch off the current trunk into 1.4 branch as
> >> > proposed
> >> > at [1] as the first step?
> >>
> >> Let me handle the branching now.
> >> I'd also like to propose we change the equinox branch "artifact
> >> version" to avoid any conflicts with the 1.4 work... would
> >> 2.0-snapshot work ?
> >>
> >
> > That would be a change that needs to be voted on. Might be worth everyone
> > reviewing the Rules For Revolutions.
> >
>
> I was about to respond to my own e-mail, let me get it right :
>
> 1.Create a 1.4 branch from trunk (this is ok, and shouldn't be a big deal)
>
> 2.Empty trunk... I wasn't planning to do it now, and I guess this is
> what you are suggesting to get it voted ?
>
> 3.Change the equinox branch artifact id (this should also be ok, right ?)
>
>
> Anyway, I'd wait for more feedback on the thread.
>
>
> > ...ant
> >
> >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
I think there are advantages to starting afresh in trunk based on the assets
that we already have, primarily that it gives us all the opportunity to feel
involved in how Tuscany v2.0 will look and gives us the chance to provide
just enough code but no more.
Ant's right though we generally need to agree this is the right thing to do
I'd want to see some focus on it and achieve quickly a base that can be
built on. So we need to only do it if we are ready. There is no point in
doing this and then seeing development continue on the Equinox branch in
parallel (I do accept that developement will continue in 1.x as we have
users that depend on that)
We already have 230 odd open JIRA against the 1.x code base so I'd like to
propose also that we take the opportunity to review those and align them
with 2.x, 1.x or both and identify those issues that can be fixed as part of
the process.
I agree with Sebastien that there is a real process opportunity here. I.e.
can we do this in a way that sets out a clear strategy (OASIS compliant SCA
runtime?) and keeps everyone involved and up to speed with what I would hope
turns out to be a fast moving but understandable code base. IMO we haven't
been very good at this in the past.
Simon
Re: Update on the Equinox branch
Posted by Luciano Resende <lu...@gmail.com>.
On Wed, Nov 5, 2008 at 7:40 AM, ant elder <an...@apache.org> wrote:
>
>
> On Tue, Nov 4, 2008 at 9:49 PM, Luciano Resende <lu...@gmail.com>
> wrote:
>>
>> On Tue, Nov 4, 2008 at 1:45 PM, ant elder <an...@apache.org> wrote:
>> >
>> >
>> > On Tue, Nov 4, 2008 at 9:32 PM, Luciano Resende <lu...@gmail.com>
>> > wrote:
>> >>
>> >> On Tue, Nov 4, 2008 at 11:44 AM, Raymond Feng <en...@gmail.com>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > I like the idea to build a new trunk from scratch for the 2.x stream
>> >> > (OASIS)
>> >> > and harvest things from the sca-equinox branch and 1.x branch (OSOA).
>> >> >
>> >> > Now we have reasonable parts covering items a, b, c, d on Sebstien's
>> >> > list. I
>> >> > see it as a good story for developers to develop Tuscany modules as
>> >> > OSGi
>> >> > bundles with the help from Eclipse PDE. The missing feature is the
>> >> > maven
>> >> > eclipse compiler doesn't report the OSGi violations yet.
>> >> >
>> >> > Should we start to branch off the current trunk into 1.4 branch as
>> >> > proposed
>> >> > at [1] as the first step?
>> >>
>> >> Let me handle the branching now.
>> >> I'd also like to propose we change the equinox branch "artifact
>> >> version" to avoid any conflicts with the 1.4 work... would
>> >> 2.0-snapshot work ?
>> >>
>> >
I'll wait for a vote thread to get started before I start any
changes/branches etc
>> > That would be a change that needs to be voted on. Might be worth
>> > everyone
>> > reviewing the Rules For Revolutions.
>> >
>>
>> I was about to respond to my own e-mail, let me get it right :
>>
>> 1.Create a 1.4 branch from trunk (this is ok, and shouldn't be a big deal)
>
> that seems fine to me
>
>>
>>
>> 2.Empty trunk... I wasn't planning to do it now, and I guess this is
>> what you are suggesting to get it voted ?
>
> yes, i think "emptying trunk " would need a vote :)
>
>>
>> 3.Change the equinox branch artifact id (this should also be ok, right ?)
>
> And i think this also needs a vote if the version is going to imply its the
> "next" or future release branch. Calling it something neutral would be ok
> without a vote, eg something like 1.4-equinox-SNAPSHOT
>
>>
>> Anyway, I'd wait for more feedback on the thread.
>>
>>
>> > ...ant
>> >
>> >
>> >
>>
>>
>>
>> --
>> Luciano Resende
>> Apache Tuscany, Apache PhotArk
>> http://people.apache.org/~lresende
>> http://lresende.blogspot.com/
>
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Update on the Equinox branch
Posted by ant elder <an...@apache.org>.
On Tue, Nov 4, 2008 at 9:49 PM, Luciano Resende <lu...@gmail.com>wrote:
> On Tue, Nov 4, 2008 at 1:45 PM, ant elder <an...@apache.org> wrote:
> >
> >
> > On Tue, Nov 4, 2008 at 9:32 PM, Luciano Resende <lu...@gmail.com>
> > wrote:
> >>
> >> On Tue, Nov 4, 2008 at 11:44 AM, Raymond Feng <en...@gmail.com>
> wrote:
> >> > Hi,
> >> >
> >> > I like the idea to build a new trunk from scratch for the 2.x stream
> >> > (OASIS)
> >> > and harvest things from the sca-equinox branch and 1.x branch (OSOA).
> >> >
> >> > Now we have reasonable parts covering items a, b, c, d on Sebstien's
> >> > list. I
> >> > see it as a good story for developers to develop Tuscany modules as
> OSGi
> >> > bundles with the help from Eclipse PDE. The missing feature is the
> maven
> >> > eclipse compiler doesn't report the OSGi violations yet.
> >> >
> >> > Should we start to branch off the current trunk into 1.4 branch as
> >> > proposed
> >> > at [1] as the first step?
> >>
> >> Let me handle the branching now.
> >> I'd also like to propose we change the equinox branch "artifact
> >> version" to avoid any conflicts with the 1.4 work... would
> >> 2.0-snapshot work ?
> >>
> >
> > That would be a change that needs to be voted on. Might be worth everyone
> > reviewing the Rules For Revolutions.
> >
>
> I was about to respond to my own e-mail, let me get it right :
>
> 1.Create a 1.4 branch from trunk (this is ok, and shouldn't be a big deal)
that seems fine to me
>
>
> 2.Empty trunk... I wasn't planning to do it now, and I guess this is
> what you are suggesting to get it voted ?
>
yes, i think "emptying trunk " would need a vote :)
> 3.Change the equinox branch artifact id (this should also be ok, right ?)
>
And i think this also needs a vote if the version is going to imply its the
"next" or future release branch. Calling it something neutral would be ok
without a vote, eg something like 1.4-equinox-SNAPSHOT
>
>
> Anyway, I'd wait for more feedback on the thread.
>
>
> > ...ant
> >
> >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
Re: Update on the Equinox branch
Posted by Luciano Resende <lu...@gmail.com>.
On Tue, Nov 4, 2008 at 1:45 PM, ant elder <an...@apache.org> wrote:
>
>
> On Tue, Nov 4, 2008 at 9:32 PM, Luciano Resende <lu...@gmail.com>
> wrote:
>>
>> On Tue, Nov 4, 2008 at 11:44 AM, Raymond Feng <en...@gmail.com> wrote:
>> > Hi,
>> >
>> > I like the idea to build a new trunk from scratch for the 2.x stream
>> > (OASIS)
>> > and harvest things from the sca-equinox branch and 1.x branch (OSOA).
>> >
>> > Now we have reasonable parts covering items a, b, c, d on Sebstien's
>> > list. I
>> > see it as a good story for developers to develop Tuscany modules as OSGi
>> > bundles with the help from Eclipse PDE. The missing feature is the maven
>> > eclipse compiler doesn't report the OSGi violations yet.
>> >
>> > Should we start to branch off the current trunk into 1.4 branch as
>> > proposed
>> > at [1] as the first step?
>>
>> Let me handle the branching now.
>> I'd also like to propose we change the equinox branch "artifact
>> version" to avoid any conflicts with the 1.4 work... would
>> 2.0-snapshot work ?
>>
>
> That would be a change that needs to be voted on. Might be worth everyone
> reviewing the Rules For Revolutions.
>
I was about to respond to my own e-mail, let me get it right :
1.Create a 1.4 branch from trunk (this is ok, and shouldn't be a big deal)
2.Empty trunk... I wasn't planning to do it now, and I guess this is
what you are suggesting to get it voted ?
3.Change the equinox branch artifact id (this should also be ok, right ?)
Anyway, I'd wait for more feedback on the thread.
> ...ant
>
>
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Update on the Equinox branch
Posted by ant elder <an...@apache.org>.
On Tue, Nov 4, 2008 at 9:32 PM, Luciano Resende <lu...@gmail.com>wrote:
> On Tue, Nov 4, 2008 at 11:44 AM, Raymond Feng <en...@gmail.com> wrote:
> > Hi,
> >
> > I like the idea to build a new trunk from scratch for the 2.x stream
> (OASIS)
> > and harvest things from the sca-equinox branch and 1.x branch (OSOA).
> >
> > Now we have reasonable parts covering items a, b, c, d on Sebstien's
> list. I
> > see it as a good story for developers to develop Tuscany modules as OSGi
> > bundles with the help from Eclipse PDE. The missing feature is the maven
> > eclipse compiler doesn't report the OSGi violations yet.
> >
> > Should we start to branch off the current trunk into 1.4 branch as
> proposed
> > at [1] as the first step?
>
> Let me handle the branching now.
> I'd also like to propose we change the equinox branch "artifact
> version" to avoid any conflicts with the 1.4 work... would
> 2.0-snapshot work ?
>
>
That would be a change that needs to be voted on. Might be worth everyone
reviewing the Rules For Revolutions.
...ant
Re: Update on the Equinox branch
Posted by Luciano Resende <lu...@gmail.com>.
On Tue, Nov 4, 2008 at 11:44 AM, Raymond Feng <en...@gmail.com> wrote:
> Hi,
>
> I like the idea to build a new trunk from scratch for the 2.x stream (OASIS)
> and harvest things from the sca-equinox branch and 1.x branch (OSOA).
>
> Now we have reasonable parts covering items a, b, c, d on Sebstien's list. I
> see it as a good story for developers to develop Tuscany modules as OSGi
> bundles with the help from Eclipse PDE. The missing feature is the maven
> eclipse compiler doesn't report the OSGi violations yet.
>
> Should we start to branch off the current trunk into 1.4 branch as proposed
> at [1] as the first step?
Let me handle the branching now.
I'd also like to propose we change the equinox branch "artifact
version" to avoid any conflicts with the 1.4 work... would
2.0-snapshot work ?
>
> Thanks,
> Raymond
>
> [1]
> http://markmail.org/message/jfgf4nsvfqw5hdg7?q=Update+on+the+Equinox+branch
>
> --------------------------------------------------
> From: "Jean-Sebastien Delfino" <js...@apache.org>
> Sent: Monday, November 03, 2008 9:52 AM
> To: <de...@tuscany.apache.org>
> Subject: Re: Update on the Equinox branch
>
>> Simon Laws wrote:
>>>
>>> snip...
>>> On Fri, Oct 31, 2008 at 6:28 PM, Raymond Feng <enjoyjava@gmail.com
>>> <ma...@gmail.com>> wrote:
>>>
>>> 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
>>>
>>>
>>> Ok, thanks Raymond, your intention is clear.
>>>
>>> So, in summary, the code in branch will be proposed as the new trunk when
>>> it is ready. It is not the intention to take the lessons learned and apply
>>> them to a new trunk bit by bit.
>>>
>>> Filling in the gaps from other ML discussions (I'm not saying it will be
>>> so but I'm painting a picture here).
>>>
>>> The new (2.x) will be our OASIS SCA code base. The intention being that
>>> it will be based on the OSGi foundation from the equinox branch
>>> The existing (1.x) trunk is retained, in a branch, as our OSOA SCA code
>>> base and is further developed as appropriate.
>>>
>>> Simon
>>
>>
>> In my opinion, to get a good foundation in trunk for (a) an OSGi-enabled
>> Tuscany and (b) an implementation of the OASIS SCA, the project needs the
>> following:
>>
>> a) Tuscany modules as first class OSGi bundles with clean imports/exports.
>>
>> b) First class integration with a leading OSGi runtime like Equinox (with
>> the ability to add others later if needed).
>>
>> c) A Modular distribution structure allowing to drop reasonably sized
>> 'feature packages' on top of a core runtime distro.
>>
>> d) An OSGi-aware development environment for Tuscany contributors, mixing
>> Maven, Eclipse tools, custom tools and processes supporting the whole dev
>> lifecycle.
>>
>> e) Less code, as the project has accumulated a lot of stuff over time with
>> various levels of quality, and dead code not used or supported anymore,
>> making it difficult to find your way through the codebase.
>>
>> f) Cleaner code, a pass through all the modules to add comments, adjust
>> the visibility of classes/methods, sort between statics and instance
>> methods, remove deprecated/unused code etc.
>>
>> g) Refreshed clean SPIs, as they've been in maintenance mode for 18 months
>> and have been polluted with workarounds and non-optimal changes.
>>
>> h) A redesign of some problematic or over-complicated areas like policy
>> for example (that's a good one to redesign as it's also impacted by the
>> OASIS chang
>
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Update on the Equinox branch
Posted by Raymond Feng <en...@gmail.com>.
Hi,
I like the idea to build a new trunk from scratch for the 2.x stream (OASIS)
and harvest things from the sca-equinox branch and 1.x branch (OSOA).
Now we have reasonable parts covering items a, b, c, d on Sebstien's list. I
see it as a good story for developers to develop Tuscany modules as OSGi
bundles with the help from Eclipse PDE. The missing feature is the maven
eclipse compiler doesn't report the OSGi violations yet.
Should we start to branch off the current trunk into 1.4 branch as proposed
at [1] as the first step?
Thanks,
Raymond
[1]
http://markmail.org/message/jfgf4nsvfqw5hdg7?q=Update+on+the+Equinox+branch
--------------------------------------------------
From: "Jean-Sebastien Delfino" <js...@apache.org>
Sent: Monday, November 03, 2008 9:52 AM
To: <de...@tuscany.apache.org>
Subject: Re: Update on the Equinox branch
> Simon Laws wrote:
>>
>> snip...
>> On Fri, Oct 31, 2008 at 6:28 PM, Raymond Feng <enjoyjava@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> 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
>>
>>
>> Ok, thanks Raymond, your intention is clear.
>>
>> So, in summary, the code in branch will be proposed as the new trunk when
>> it is ready. It is not the intention to take the lessons learned and
>> apply them to a new trunk bit by bit.
>>
>> Filling in the gaps from other ML discussions (I'm not saying it will be
>> so but I'm painting a picture here).
>>
>> The new (2.x) will be our OASIS SCA code base. The intention being that
>> it will be based on the OSGi foundation from the equinox branch
>> The existing (1.x) trunk is retained, in a branch, as our OSOA SCA code
>> base and is further developed as appropriate.
>>
>> Simon
>
>
> In my opinion, to get a good foundation in trunk for (a) an OSGi-enabled
> Tuscany and (b) an implementation of the OASIS SCA, the project needs the
> following:
>
> a) Tuscany modules as first class OSGi bundles with clean imports/exports.
>
> b) First class integration with a leading OSGi runtime like Equinox (with
> the ability to add others later if needed).
>
> c) A Modular distribution structure allowing to drop reasonably sized
> 'feature packages' on top of a core runtime distro.
>
> d) An OSGi-aware development environment for Tuscany contributors, mixing
> Maven, Eclipse tools, custom tools and processes supporting the whole dev
> lifecycle.
>
> e) Less code, as the project has accumulated a lot of stuff over time with
> various levels of quality, and dead code not used or supported anymore,
> making it difficult to find your way through the codebase.
>
> f) Cleaner code, a pass through all the modules to add comments, adjust
> the visibility of classes/methods, sort between statics and instance
> methods, remove deprecated/unused code etc.
>
> g) Refreshed clean SPIs, as they've been in maintenance mode for 18 months
> and have been polluted with workarounds and non-optimal changes.
>
> h) A redesign of some problematic or over-complicated areas like policy
> for example (that's a good one to redesign as it's also impacted by the
> OASIS chang
Re: Update on the Equinox branch
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Simon Laws wrote:
>
> snip...
> On Fri, Oct 31, 2008 at 6:28 PM, Raymond Feng <enjoyjava@gmail.com
> <ma...@gmail.com>> wrote:
>
> 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
>
>
> Ok, thanks Raymond, your intention is clear.
>
> So, in summary, the code in branch will be proposed as the new trunk
> when it is ready. It is not the intention to take the lessons learned
> and apply them to a new trunk bit by bit.
>
> Filling in the gaps from other ML discussions (I'm not saying it will be
> so but I'm painting a picture here).
>
> The new (2.x) will be our OASIS SCA code base. The intention being that
> it will be based on the OSGi foundation from the equinox branch
> The existing (1.x) trunk is retained, in a branch, as our OSOA SCA code
> base and is further developed as appropriate.
>
> Simon
In my opinion, to get a good foundation in trunk for (a) an OSGi-enabled
Tuscany and (b) an implementation of the OASIS SCA, the project needs
the following:
a) Tuscany modules as first class OSGi bundles with clean imports/exports.
b) First class integration with a leading OSGi runtime like Equinox
(with the ability to add others later if needed).
c) A Modular distribution structure allowing to drop reasonably sized
'feature packages' on top of a core runtime distro.
d) An OSGi-aware development environment for Tuscany contributors,
mixing Maven, Eclipse tools, custom tools and processes supporting the
whole dev lifecycle.
e) Less code, as the project has accumulated a lot of stuff over time
with various levels of quality, and dead code not used or supported
anymore, making it difficult to find your way through the codebase.
f) Cleaner code, a pass through all the modules to add comments, adjust
the visibility of classes/methods, sort between statics and instance
methods, remove deprecated/unused code etc.
g) Refreshed clean SPIs, as they've been in maintenance mode for 18
months and have been polluted with workarounds and non-optimal changes.
h) A redesign of some problematic or over-complicated areas like policy
for example (that's a good one to redesign as it's also impacted by the
OASIS changes).
i) Processes in the project to keep the code of the foundation clean,
simple and interesting to work with.
The work in the sca-equinox branch is an attempt to cover (a) to (d) and
a little bit of (e), as a side effect of trying to work on (a) to (d) on
a more manageable code base.
Items (e) to (h) are as important, and without addressing them first,
the new foundation will be difficult to build on and grow again.
Finally Item (i) is the most important for a longer term success of that
foundation.
So, I think that the better way to build the new foundation the project
needs in trunk is:
1) Empty trunk.
2) Clean up a small selection of modules and functions, do the above (a)
to (g) thoroughly.
3) Bring these modules to trunk slowly when they are clean and usable again.
4) Do not bring up to trunk the dead weight or the problematic functions
covered by (h). They'll have to be redone for OASIS-SCA anyway.
5) Establish (i) to make sure the foundation stays clean.
Disclaimer: I'm not going to have much time to work on this in the next
few weeks so please take all of the above really just as suggestions.
Hope this helps.
--
Jean-Sebastien
Re: Update on the Equinox branch
Posted by Simon Laws <si...@googlemail.com>.
snip...
On Fri, Oct 31, 2008 at 6:28 PM, Raymond Feng <en...@gmail.com> wrote:
> 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
>
>
Ok, thanks Raymond, your intention is clear.
So, in summary, the code in branch will be proposed as the new trunk when it
is ready. It is not the intention to take the lessons learned and apply them
to a new trunk bit by bit.
Filling in the gaps from other ML discussions (I'm not saying it will be so
but I'm painting a picture here).
The new (2.x) will be our OASIS SCA code base. The intention being that it
will be based on the OSGi foundation from the equinox branch
The existing (1.x) trunk is retained, in a branch, as our OSOA SCA code base
and is further developed as appropriate.
Simon
Re: Update on the Equinox branch
Posted by Raymond Feng <en...@gmail.com>.
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 <en...@gmail.com> 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 <en...@gmail.com> 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 <en...@gmail.com> 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
Re: Update on the Equinox branch
Posted by Simon Laws <si...@googlemail.com>.
On Thu, Oct 30, 2008 at 5:32 PM, Raymond Feng <en...@gmail.com> 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 <en...@gmail.com> 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 <en...@gmail.com> 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
Re: Update on the Equinox branch
Posted by Raymond Feng <en...@gmail.com>.
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 <en...@gmail.com> 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 <en...@gmail.com> 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
Re: Update on the Equinox branch
Posted by Luciano Resende <lu...@gmail.com>.
>From [1] and [2], our 1.4 release would be based on trunk and I was
planning to branch it over the weekend. Maybe this is a good time to
also bring the equinox branch to trunk. If people are comfortable with
this, I'd volunteer to make this happen all together with the 1.4
branching.
[1] http://markmail.org/message/3hijhczkotdgddol
[2] http://markmail.org/message/w2tuvdg4lijm4vta
On Thu, Oct 30, 2008 at 9:12 AM, ant elder <an...@apache.org> wrote:
> 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 <en...@gmail.com> 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 <en...@gmail.com> 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
>
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Update on the Equinox branch
Posted by ant elder <an...@apache.org>.
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 <en...@gmail.com> 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 <en...@gmail.com> 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
>
Re: Update on the Equinox branch
Posted by Raymond Feng <en...@gmail.com>.
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 <en...@gmail.com> 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
Re: Update on the Equinox branch
Posted by ant elder <an...@gmail.com>.
On Wed, Oct 29, 2008 at 6:47 PM, Raymond Feng <en...@gmail.com> 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