I checked out the M2 branch, cleaned out my local Maven .m2 repo,
built the runtime using -Prelease, built the samples, and ran all
the samples. The main purpose of doing this was to ensure that
the -Prelease flag had not removed any artifacts that were needed
to successfully build and run the
On further investigation, this is caused by a mismatch betweeen the
sample instructions in readme.html and the artifacts built by the sample.
The instructions give the following command to run:
java -jar target/distribution/bin/launcher.jar
I have now run all the samples successfully, using only the jars that
are deployed to maven when using the -Prelease flag.
The only other issue I had with the previous release candidate was the
packaging and formal release voting for the spec APIs that we need from
org.osoa and commonj. These
Hi,
Considering the axiom SNAPSHOT dependency puzzle has been figured out,
should we go ahead to push M2 release out?
Thanks,
Raymond
- Original Message -
From: Raymond Feng [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, December 04, 2006 12:10 PM
Subject: Re: Much
Yes! Jeremy, as release manager what do you say, would you make us another
release candidate to review and vote on?
...ant
On 12/5/06, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
Considering the axiom SNAPSHOT dependency puzzle has been figured out,
should we go ahead to push M2 release
I think resolves the last issue - does anyone have anything else to
bring up? If not, I will start to package another release candidate.
--
Jeremy
On Dec 5, 2006, at 8:50 AM, ant elder wrote:
Yes! Jeremy, as release manager what do you say, would you make us
another
release candidate to
