We ran into scalability issues in the past trying to build everything
together all the time and have migrated away to a more modular
structure. Rather than put it all back together like this, would it
be possible to have separate modules in Parabuild for the different
areas? For example, modules for:
* spec
* sdo
* das
* sca kernel
* sca standalone runtime
* and individual sca services (e.g. axis2 based ones)
Each of these modules should build on their own but for that to work
we need to be more diligent about publishing SNAPSHOTs - e.g. we
should consider republishing the SNAPSHOT of spec.
--
Jeremy
On Jan 5, 2007, at 4:04 PM, Slava Imeshev wrote:
--- Toni Menzel <[EMAIL PROTECTED]> wrote:
I did this:
svn co http://svn.apache.org/repos/asf/incubator/tuscany/java/ .
cd sdo;mvn clean install
cd ../sca;mvn clean install
the second mvn call breaks with missing dependency.
@Slava, can you rebuild your question, don't know what you are
talking
about exactly..?
We have these builds configured for Tuscany but apparently after
recent changes they are not doing much.
If I had a command line sequence I could set it up so that it
runs the build after every checkin and sends notifications
if they break the build. That'd give an opportunity to fix
the build quickly rather than after someone discovers it
does not build.
The closes that we could get based on the docs is
export JAVA_HOME=/opt/jrockit-R26.4.0-jdk1.5.0_06
export ANT_HOME=/opt/apache-ant-1.6.5
export MAVEN_HOME=/opt/maven-2.0.4
export PATH=$PATH:$JAVA_HOME/bin:$MAVEN_HOME/bin:$ANT_HOME/bin
echo ==== Building SDO =============
mvn -N
cd $PARABUILD_BUILD_DIR/spec
mvn -N
cd $PARABUILD_BUILD_DIR/sdo
mvn -N
echo ==== Building sdo.spec project =============
cd $PARABUILD_BUILD_DIR/spec/sdo-api
mvn
echo ==== Building sdo.tools project =============
cd $PARABUILD_BUILD_DIR/sdo/impl
mvn
echo ==== Building sdo.tools project =============
cd $PARABUILD_BUILD_DIR/sdo/tools
mvn
echo ==== Building sdo.samples project =============
cd $PARABUILD_BUILD_DIR/sdo/sample
mvn
echo ==== Building SCA =============
cd $PARABUILD_BUILD_DIR/spec/sca
mvn -e
cd $PARABUILD_BUILD_DIR/spec/commonj
mvn -e
cd $PARABUILD_BUILD_DIR/sca
mvn -e
But with this some tests are failing so I am not sure if this
sequence is
correct.
That's why I was wondering what is the official build sequence to
build
tuscany-java from scrates.
Slava
Toni
Slava Imeshev schrieb:
Guys,
If you tell me how to build tuscany from a command line at one
shot. I can make sure that such
errors are caught immeditely.
Slava
--- Toni Menzel <[EMAIL PROTECTED]> wrote:
Hi!
I just tried to build tuscany from source for the first time.
Building sdo works out-of-the-box but the sca breaks with the
following
message:
Downloading:
http://ws.zones.apache.org/repository/org.osoa/jars/sca-api-
r0.95-1.0-incubator-SNAPSHOT.jar
[WARNING] Unable to get resource from repository
apache.ws.m1.snapshots
(http://ws.zones.apache.org/repository)
[INFO]
-------------------------------------------------------------------
-----
[ERROR] BUILD ERROR
[INFO]
-------------------------------------------------------------------
-----
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.osoa:sca-api-r0.95:jar:1.0-incubator-SNAPSHOT
I added http://people.apache.org/repo/m2-snapshot-repository/ to my
.m2/settings.xml, but this doesn't work either..
is there any known issue with this revision or am i missing
something?
thanks in advance,
Toni
PS: I tried using a fresh local mvn repository, too :-(
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Toni Menzel
http://www.tonit.com
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
