On Fri, Oct 31, 2008 at 10:51 AM, Raymond Feng <[EMAIL PROTECTED]> wrote: > Hi, > > Now the configuration of Tuscany modules as Eclipse plugin projects seem to > be working well. I have also fixed most of the OSGi access violations. A few > modules still have error markers. There are two major issues: > > 1) Split packages from 3rd party jars. > > For example, module tuscany-binding-ejb-runtime depends on > geronimo-ejb_3.0_spec-1.0.jar and annotations-api-6.0.14.jar. Both have the > javax.ejb packages. > > 2) Access non-exported packages in some of test cases. > > For example, module tuscany-policy-security-jsr250 has test cases that use > org.apache.tuscany.sca.implementation.java.introspect.impl.ServiceProcessor. >
I'm looking into this issue. I also noticed some possible split package in binding-gdata, I'm looking into that as well. > Thanks, > Raymond > > -------------------------------------------------- > From: "Raymond Feng" <[EMAIL PROTECTED]> > Sent: Thursday, October 30, 2008 10:32 AM > To: <[email protected]> > Subject: Re: Update on the Equinox branch > >> 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: [email protected] >> 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: [email protected] >> 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 > > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
