Maybe I missed it, but is this documented today how to do this? What
modules to build for the kernel? For extensions? I recall I started to
help on a wiki page but can't seem to locate it now. I think I stopped
since even I got a bit confused on it. Can I ask where this is? And
is it
This one:
https://svn.apache.org/repos/asf/incubator/tuscany/java/pom.xml
This is no longer used as the parent for any of the modules and the
profiles it contains are no longer valid so it does not really serve
any purpose. I'd propose we remove it ...
--
Jeremy
Hi Jeremy
Wouldn't we still have scenarios where we would like to build multiple
projects from the Tuscany project root ? (e.g sca and samples/sca or
sca/sca-api-r1.0 and kernel). If so, the profiles inside java/pom.xml
should be way to go, no ?
--
Luciano Resende
On Feb 21, 2007, at 11:31 AM, Luciano Resende wrote:
Hi Jeremy
Wouldn't we still have scenarios where we would like to build
multiple
projects from the Tuscany project root ? (e.g sca and samples/sca or
sca/sca-api-r1.0 and kernel). If so, the profiles inside java/pom.xml
should be way
If we follow the pattern we have been using for SDO, DAS, once we build the
project, the samples are built together to make sure changes on the core
didn't break functionality used by the samples. In the case of SCA, don't
we want to do the same, and when building sca, we would build the samples
,
Raymond
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, February 21, 2007 12:05 PM
Subject: Re: Remove pom in tuscany/java
On Feb 21, 2007, at 11:31 AM, Luciano Resende wrote:
Hi Jeremy
Wouldn't we still have scenarios
On Feb 21, 2007, at 12:50 PM, Luciano Resende wrote:
If we follow the pattern we have been using for SDO, DAS, once we
build the
project, the samples are built together to make sure changes on the
core
didn't break functionality used by the samples. In the case of
SCA, don't
we want to do
On Feb 21, 2007, at 1:25 PM, Raymond Feng wrote:
So are you going to publish SNAPSHOT versions of the different
modules to maven repo all the time? I assume the published
artifacts are the dependencies used by modules. Otherwise, those
who want to play with the source code won't have a
Jeremy Boynes wrote:
On Feb 21, 2007, at 1:25 PM, Raymond Feng wrote:
So are you going to publish SNAPSHOT versions of the different
modules to maven repo all the time? I assume the published artifacts
are the dependencies used by modules. Otherwise, those who want to
play with the source
