Here is a patch that uses the geronimo stax dependency, and reduced
the number of errors related to the stax-api dependency.
I'm still trying to figure out why assembly-xml have no reference to
the stax dependency.
On Fri, Nov 21, 2008 at 1:51 AM, Simon Laws <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, Nov 21, 2008 at 9:42 AM, Luciano Resende <[EMAIL PROTECTED]>
> wrote:
>>
>> Good point, the difference is that in the equinox branch, although we
>> are defining the stax-api:1.0-2 in the pom, the dependency being
>> picked up in plug-in dependencies is the
>> geronimo-stax-api_1.0_spec-1.0.1.jar. Maybe we could experiment with
>> these two different dependencies and see if they make any difference.
>>
>> On Fri, Nov 21, 2008 at 1:26 AM, Simon Laws <[EMAIL PROTECTED]>
>> wrote:
>> >
>> >
>> > On Fri, Nov 21, 2008 at 9:22 AM, Luciano Resende <[EMAIL PROTECTED]>
>> > wrote:
>> >>
>> >> On Thu, Nov 20, 2008 at 10:23 PM, Raymond Feng <[EMAIL PROTECTED]>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > I can now get JDK 1.6 working with the PDE projects. I'm still seeing
>> >> > the
>> >> > unresolved javax.xml.stream issues with JDK 5 even though the equinox
>> >> > console shows all the bundles can be resolved.
>> >> >
>> >>
>> >> I'm seeing the issue in JDK 1.5, and was wondering if this could be
>> >> related to the stax-api-1.0-2 which version is 1.0-2, but is being
>> >> listed as 1.0.0 in the pdetarget. I tried to fix that in the manifest,
>> >> but eclipse was complaining that "dash" wasn't a valid character.
>> >> Well, this is just a guess, I'll try to look into this a little more
>> >> in the morning.
>> >>
>> >> > I also added the option to create a launchable equinox configuration.
>> >> > You
>> >> > can now start the equinox console as follows:
>> >> >
>> >> > C:\Tuscany\java\sca\distribution\pdetarget\target\modules>
>> >> > "c:\Program
>> >> > Files\IBM\Java50\bin\java.exe" -jar osgi-3.3.0-v20070530.jar -console
>> >> > -clean
>> >> >
>> >> > Thanks,
>> >> > Raymond
>> >> >
>> >> >
>> >> > From: Simon Laws
>> >> > Sent: Thursday, November 20, 2008 7:35 AM
>> >> > To: [email protected] ; [EMAIL PROTECTED]
>> >> > Subject: Re: 2.0 trunk modules status update
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Thu, Nov 20, 2008 at 3:30 PM, ant elder <[EMAIL PROTECTED]>
>> >> > wrote:
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > 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: <[email protected]>
>> >> > 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
>> >> >
>> >> >
>> >> >
>> >> > I don't see those, I'm getting problems to do with packages that are
>> >> > in
>> >> > the
>> >> > JDK, e.g. the start of the databinding-jaxb manifest is
>> >> >
>> >> > Import-Package: javax.activation,
>> >> > javax.imageio,
>> >> > javax.xml.bind,
>> >> >
>> >> > An eclipse complains that no available bundle export javax.imageio.
>> >> > Which is
>> >> > a little odd.
>> >> >
>> >> > I wonder if it's something to do with the JDK that was used to create
>> >> > these
>> >> > manifests. They were generated using "Created-By: 1.6.0_07 (Sun
>> >> > Microsystems
>> >> > Inc.)" I'm on IBM 1.5. Just a stab in the dark at the moment.
>> >> >
>> >> > Simon
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Luciano Resende
>> >> Apache Tuscany, Apache PhotArk
>> >> http://people.apache.org/~lresende
>> >> http://lresende.blogspot.com/
>> >
>> > Hi
>> >
>> > Could well be that dash. Strange that this wasn't an issue on the
>> > branch.
>> > Were you using JDK6 there? I'll prod it a little to day to see if I can
>> > get
>> > anywhere.
>> >
>> > Simon
>> >
>>
>>
>>
>> --
>> Luciano Resende
>> Apache Tuscany, Apache PhotArk
>> http://people.apache.org/~lresende
>> http://lresende.blogspot.com/
>
> Ok, that's useful. I can certainly give that a spin.
>
> Simon
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Index: databinding-jaxb/pom.xml
===================================================================
--- databinding-jaxb/pom.xml (revision 719471)
+++ databinding-jaxb/pom.xml (working copy)
@@ -50,9 +50,21 @@
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.1</version>
+ <exclusions>
+ <exclusion>
+ <groupId>javax.xml.stream</groupId>
+ <artifactId>stax-api</artifactId>
+ </exclusion>
+ </exclusions>
</dependency>
<dependency>
+ <groupId>org.apache.geronimo.specs</groupId>
+ <artifactId>geronimo-stax-api_1.0_spec</artifactId>
+ <version>1.0.1</version>
+ </dependency>
+
+ <dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.1.7</version>
Index: pom.xml
===================================================================
--- pom.xml (revision 719545)
+++ pom.xml (working copy)
@@ -53,8 +53,6 @@
<module>endpoint</module>
<module>extensibility</module>
<module>extensibility-equinox</module>
- <module>host-http</module>
- <module>host-jetty</module>
<module>implementation-java</module>
<module>implementation-java-runtime</module>
<module>implementation-java-xml</module>
@@ -74,7 +72,6 @@
<module>policy</module>
<module>policy-security</module>
<module>policy-xml</module>
- <module>policy-xml-ws</module>
<module>sca-api</module>
<module>workspace</module>
<module>workspace-impl</module>
Index: databinding/pom.xml
===================================================================
--- databinding/pom.xml (revision 719471)
+++ databinding/pom.xml (working copy)
@@ -59,13 +59,21 @@
<version>2.0-SNAPSHOT</version>
</dependency>
+ <!--
<dependency>
<groupId>javax.xml.stream</groupId>
<artifactId>stax-api</artifactId>
<version>1.0-2</version>
</dependency>
-
+ -->
+
<dependency>
+ <groupId>org.apache.geronimo.specs</groupId>
+ <artifactId>geronimo-stax-api_1.0_spec</artifactId>
+ <version>1.0.1</version>
+ </dependency>
+
+ <dependency>
<groupId>org.codehaus.woodstox</groupId>
<artifactId>wstx-asl</artifactId>
<version>3.2.4</version>
Index: contribution/pom.xml
===================================================================
--- contribution/pom.xml (revision 719471)
+++ contribution/pom.xml (working copy)
@@ -40,12 +40,20 @@
<artifactId>tuscany-extensibility</artifactId>
<version>2.0-SNAPSHOT</version>
</dependency>
-
+
+ <!--
<dependency>
<groupId>javax.xml.stream</groupId>
<artifactId>stax-api</artifactId>
<version>1.0-2</version>
</dependency>
+ -->
+
+ <dependency>
+ <groupId>org.apache.geronimo.specs</groupId>
+ <artifactId>geronimo-stax-api_1.0_spec</artifactId>
+ <version>1.0.1</version>
+ </dependency>
</dependencies>
</project>
Index: assembly-xml/pom.xml
===================================================================
--- assembly-xml/pom.xml (revision 719471)
+++ assembly-xml/pom.xml (working copy)
@@ -65,13 +65,21 @@
<version>2.0-SNAPSHOT</version>
</dependency>
+ <!--
<dependency>
<groupId>javax.xml.stream</groupId>
<artifactId>stax-api</artifactId>
<version>1.0-2</version>
</dependency>
+ -->
<dependency>
+ <groupId>org.apache.geronimo.specs</groupId>
+ <artifactId>geronimo-stax-api_1.0_spec</artifactId>
+ <version>1.0.1</version>
+ </dependency>
+
+ <dependency>
<groupId>org.codehaus.woodstox</groupId>
<artifactId>wstx-asl</artifactId>
<version>3.2.4</version>
Index: databinding-axiom/pom.xml
===================================================================
--- databinding-axiom/pom.xml (revision 719471)
+++ databinding-axiom/pom.xml (working copy)
@@ -40,13 +40,21 @@
<version>2.0-SNAPSHOT</version>
</dependency>
+ <!--
<dependency>
<groupId>javax.xml.stream</groupId>
<artifactId>stax-api</artifactId>
<version>1.0-2</version>
</dependency>
-
+ -->
+
<dependency>
+ <groupId>org.apache.geronimo.specs</groupId>
+ <artifactId>geronimo-stax-api_1.0_spec</artifactId>
+ <version>1.0.1</version>
+ </dependency>
+
+ <dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-api</artifactId>
<version>1.2.7</version>
