Hi, Simon,
The local copy of Tuscany jars in the lib directory was for the
self-contained test purpose. We can disable that and set up TUSCANY_HOME to
point to an existing 1.6 distro.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <[email protected]>
Sent: Thursday, January 21, 2010 11:19 PM
To: <[email protected]>
Subject: Re: Separate JIRA component for travel sample
Simon Laws wrote:
No I don't think so. I'd thought of doing something separate. Not sure
it's going to be ready for 1.6 and don't want to hold that up.
I say separate mainly as I'd imagined this sample to be an example of
how someone can build an application that uses a separate Tuscany SCA
release rather than a sample which is part of a Tuscany SCA release.
Thoughts?
Simon
+1 for releasing this sample separately and using it to demonstrate how
users can build and run applications using an existing Tuscany release.
With this in mind, I think the current packaging of the sample may have a
bit of a problem. The "lib" directory produced by a maven build of the
distribution module contains 64MB of jars that are almost an exact copy of
the complete Tuscany runtime contained in the Tuscany binary distro.
If a user were building this sample based on an existing Tuscany release,
I'm not convinced they would want their build to create a new copy of the
Tuscany runtime as part of the sample application. Perhaps we could find
a way for the sample to use the Tuscany runtime that the user has already
downloaded and installed.
Simon
