Hi,
Build failure seems to be a show-stopper to me :-). Thank you for catching
it.
The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes for
the unit tests. So if we fix it, the scope of testing shouldn't be a big
deal. All we have to do is to run the maven build on the environments we
have tested so far.
Thanks,
Raymond
----- Original Message -----
From: "Simon Laws" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Tuesday, May 22, 2007 3:37 AM
Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I've given the src and binary distros a spin on linux. My configuration is
Fedora Core5
IBM JDK 1.5.0
Maven 2.0.6
Binary:
I concur with Luciano that the READMEs for
calculator-rmi-reference
calculator-rmi-service
implementation-crud
now don't match the way that the samples are currently organized. I'm
reluctant to agree to go with this release when our shop window isn't
fully
functional. I have checked fixes in for the calculator sample to the
0.9branch and head. Luciano's fix for implementation-crud looks good
to me.
Source:
This fails to build under maven in my environment. The culprit is the
maven-jaxb-plugin. The pom provided with the version that we refer in our
poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author
names which causes the maven build to fail with the IBM JDK 1.5.0 on
Linux.
I can confirm that this does not cause a problem with the same JDK (same
version and build at least) on Windows XP. I tried using different
maven-jaxb-plugins from a variety of repositories. All failed for other
reasons. There is a manual work around to the problem, i.e. remove the
non-UTF8 characters, so I don't think that this, on its own is a blocker.
I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
