Hi,
The host-http, host-jetty, policy-security-ws modules are in the
modules/pom.xml but they are not declared as dependencies in the
distribution/core/pom.xml. As a result, the pdetarget doesn't have the
3rd-party dependencies for these modules generated as OSGi bundles.
Thanks,
Raymond
From: ant elder
Sent: Thursday, November 20, 2008 7:30 AM
To: dev@tuscany.apache.org
Subject: Re: 2.0 trunk modules status update
On Thu, Nov 20, 2008 at 2:30 PM, Simon Laws <[EMAIL PROTECTED]>
wrote:
On Thu, Nov 20, 2008 at 7:22 AM, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
I spent a few hours trying to get the Eclipse PDE integration working. But I
ran into a strange issue that doesn't exist in the sca-equinox branch: The
org.eclipse.osgi plugin cannot be selected for the target platform,
otherwise javax.xml.stream Import-Package cannot be resolved. I will have to
continue tomorrow.
I suggest that we try to get more modules built and loaded into Eclipse PDE
following the steps below.
1) Build maven-eclipse-compiler first
cd tools/maven/maven-eclipse-compiler
mvn clean install
2) Build the modules
cd modules
mvn clean install -Dmaven.test.skip=true
mvn -Peclipse
3) Build the PDE target
cd distribution
mvn clean install
cd pdetarget
mvn -Peclipse
4) Import distribution/pdetarget
Launch your Eclipse IDE, select File->Import->Existing projects into
Workplace, and then import the "PDE Target" project (from
distribution/pdetarget) into your Eclipse Workspace.
Inside eclipse, open tuscany-distribution-pdetarget project
open target/tuscany-distribution-pdetarget.target
click "Set as target platform" on the upper-right side of the overview
window that opened
You can then go to Windows --> Preferences --> Plugin Development Env -->
Target Platform to verify
5) Import modules
Now, launch your Eclipse IDE, select File->Import->Existing projects into
Workplace, and then import the project from SCA Modules into your Eclipse
Workspace.
Thanks,
Raymond
--------------------------------------------------
From: "Luciano Resende" <[EMAIL PROTECTED]>
Sent: Wednesday, November 19, 2008 11:19 AM
To: <dev@tuscany.apache.org>
Subject: Re: 2.0 trunk modules status update
We have made good progress, this is all good news. As for what's next,
I believe there are still lots of work to do to get a stable base for
our OASIS work, and this thread [1] give us some hints of what can be
our next steps. I think we still need to bring up most if not all the
modules as OSGi bundles, get some of the OSGi tools integrated, start
working on getting the tests passing, etc
[1] http://markmail.org/message/otyegk65ebku642o
On Wed, Nov 19, 2008 at 11:06 AM, Simon Laws <[EMAIL PROTECTED]>
wrote:
On Wed, Nov 19, 2008 at 5:15 PM, Simon Laws <[EMAIL PROTECTED]>
wrote:
On Wed, Nov 19, 2008 at 4:37 PM, ant elder <[EMAIL PROTECTED]> wrote:
FYI, the 2.0 trunk modules build ok for me now, thats with the
modules/pom.xml only including the reduced set for the calculator sample,
and samples/calculator-equinox is workingish, gets a lot of warning messages
but the calculator component does run, but only when the maven repository is
not within a folder containg spaces in the name.
...ant
Nice one ant. Let me do an update and get your changes.
Simon
Ok, so those changes work for me and I'm up and running with this basic set
of modules. So what next? I guess it's back over to the themes thread to
hear what people want to work on, in what order, and look at how we get it
done.
Simon
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Hi
So I upgraded to Ganymede, followed the steps in the previous post to
install the new PDE target (needed a bit of pom editing about to get it to
work with our minimum set of modules).
I installed the PDE eclipse projects (mvn -Peclipse) and got a lot of
errors.
I reverted back to standard eclipse projects (mvn elipse:eclipse) and of
course I'm good again.
I suggest we concentrate on getting the minimum set of modules just as we
want them before pulling the kitchen sink back into the build. That doesn't
mean of course that if you want to maintain other modules in you IDE if you
feel the need
On that note can we now move all of the modules that don't don't contribute
to the minimum set out of the modules dir?
Simon
I'm doing the same, and it is working ok though i get the errors below on
some of the manifests relating to a few dependencies. Whats the way to fix
these?
...ant
Description Resource Path Location Type
No available bundle exports package 'commonj.work' MANIFEST.MF
tuscany-core/META-INF line 50 Plug-in Problem
No available bundle exports package 'net.sf.cglib.proxy' MANIFEST.MF
tuscany-core/META-INF line 56 Plug-in Problem
No available bundle exports package 'org.apache.ws.commons.schema'
MANIFEST.MF tuscany-xsd/META-INF line 15 Plug-in Problem
No available bundle exports package 'org.mortbay.component' MANIFEST.MF
tuscany-host-jetty/META-INF line 19 Plug-in Problem
No available bundle exports package 'org.mortbay.jetty.handler'
MANIFEST.MF tuscany-host-jetty/META-INF line 21 Plug-in Problem
No available bundle exports package 'org.mortbay.jetty.nio' MANIFEST.MF
tuscany-host-jetty/META-INF line 22 Plug-in Problem
No available bundle exports package 'org.mortbay.jetty.security'
MANIFEST.MF tuscany-host-jetty/META-INF line 23 Plug-in Problem
No available bundle exports package 'org.mortbay.resource' MANIFEST.MF
tuscany-host-jetty/META-INF line 26 Plug-in Problem
No available bundle exports package 'org.mortbay.thread' MANIFEST.MF
tuscany-host-jetty/META-INF line 27 Plug-in Problem
Unsatisfied constraint: 'Import-Package: org.mortbay.jetty; version="6.1.7"'
MANIFEST.MF tuscany-host-jetty/META-INF line 20 Plug-in Problem
Unsatisfied constraint: 'Import-Package: org.mortbay.jetty.servlet;
version="6.1.7"' MANIFEST.MF tuscany-host-jetty/META-INF line 24
Plug-in Problem
Unsatisfied constraint: 'Import-Package: org.mortbay.log; version="6.1.7"'
MANIFEST.MF tuscany-host-jetty/META-INF line 25 Plug-in Problem
