CVS log for carol/carol/build.xml
	Help

Request diff between arbitrary revisions / Display revisions graphically

Add maven2 support:
* Version updated to 2.2.10-SNAPSHOT
* Introduced POM for all carol artifacts
* add 'maven:install' and 'maven:deploy' target in the main build.xml

Carol 2.2.9

CAROL_2_2_8

CAROL_2_2_7

CAROL_2_2_6

New version

Test to see if CVSPAM works well

CAROL_2_2_4

CMI_1_1_4
CAROL_2_2_3

CAROL_2_2_2

CAROL_2_2_1

CAROL_2_2_0

CAROL_2_1_0

 CAROL/CMI separation

version 2.0.10

New version

If some Sun classes are not available at compile time, or if some signature mismatch, remove the compilation of these classes.
This should remove cmi, iiop and jrmp protocols

version 2.0.8

CAROL_2_0_7

New CMI  :
- replace velocity template by ASM 1.5.3
- improving check style
- handle the serializable entries in the registry

increase version

enhance building of Carol packages (to publish)

Updated irmi.jar to the IRMI_1_0_0 tagged version. Updated externals/README. Updated version number in build.xml

Update version

2.0.2

carol 1.8.9.4

increase counter

fix invalid property

2.0.0

Generate stubs when using jrmp/jeremie

Code has been removed (update build file)

increment version number. I think this is the time to increment first digit :)

keep the name 1.0 in the jar file for the dist

Remove jar ow_util_ant_tasks.jar as discussed here :
http://www.objectweb.org/wws/arc/carol/2005-02/msg00043.html

Use subant task of Ant instead of multipleAnt

Format xml (eclipse editor) + Header

Backport for running on Bea 1.4/5.0 and Sun 5.0 JDK.
Also for IBM but it fails at startup

Removed the target "build.test" from both build.xml and
test/build.xml.

This target didn't really belong in build.xml.  It should be
sufficient for build.xml to call the target "run.tests" in
test/build.xml without also having to explicitly call "build.test".
It is then up to test/build.xml to decide whether or not to build the
tests.

In test/build.xml, the target "build.test" had a trivial
implementation.  By inlining it, we reduce the visual structural
complexity of the build process.

Compare
http://cvs.forge.objectweb.org/cgi-bin/viewcvs.cgi/carol/carol/doc/usermanual/img/test-build.png?rev=1.2&content-type=text/vnd.viewcvs-markup
and
http://cvs.forge.objectweb.org/cgi-bin/viewcvs.cgi/carol/carol/doc/usermanual/img/test-build.png?rev=1.3&content-type=text/vnd.viewcvs-markup


Also compare

http://cvs.forge.objectweb.org/cgi-bin/viewcvs.cgi/carol/carol/doc/usermanual/img/build.png?rev=1.1&content-type=text/vnd.viewcvs-markup
and
http://cvs.forge.objectweb.org/cgi-bin/viewcvs.cgi/carol/carol/doc/usermanual/img/build.png?rev=1.2&content-type=text/vnd.viewcvs-markup

Minor cleanup.

Removed the following property definitions from build.xml:

    carol.cmi.name
    carol.cmi.package
    carol.cmi.compiler

These were only used in archive/ow_carol_cmic.xml.  So, I just inlined
their values directly in ow_carol_cmic.xml.

Minor cleanup.

Prior to these change, build.xml used two different properties for the
same purpose: "version" and "carol.version".  The former was defined
in config/configure.properties and hasn't been updated in ages.  (It
was still set to 1.5.1.)  The latter is defined in build.xml.

I removed "version" and updated affected targets to use
"carol.version" instead.

Removed the definition of "externals.classpath".  It was identical to
that of "carol.classpath".  Replaced all remaining references
to "externals.classpath" with references to "carol.classpath".

Removed the jonathan.jvmarg property.  It appears to have been copied
and pasted from test/genstub/rmic_jonathan.xml into build.xml.  In
order to get expanded correctly, this property depended on the
following values having been set:

    test.externals
    test.build
    test.ext

These are not set in build.xml.  So, the property ended up being to
set to a garbage string with unexpanded $ signs in it:

  -Xbootclasspath/p:${test.externals}/jonathan.jar:...

Removing the jonathan.jvmarg altogether did not cause any problems in
build.xml.  Encouraged by this, I tried removing it from
test/genstub/rmic_jonathan.xml as well.  No problems there either.

This is a merge of change "2005-01-13 15:00" from the carol_1_8_5_br
branch back onto the trunk.  The merge includes the following changes
from the branch:

 build.xml (1.27.2.3)
 test/build.xml (1.11.2.1)
 test/conform/carol_all_tests.xml (1.12.2.2)
 test/conform/generic/carol_double.xml (1.11.2.2)
 test/ext/java.policy (1.3.2.1)
 test/src/org/objectweb/carol/jtests/conform/basic/clients/MultiProtocolTests.java (1.5.2.1)
 test/src/org/objectweb/carol/jtests/conform/basic/server/BasicServer.java (1.6.2.1)
 test/src/org/objectweb/carol/jtests/conform/util/ProcessRunner.java (1.1.2.1)
 test/src/org/objectweb/carol/jtests/conform/util/ProcessStopper.java (1.1.2.1)

This change is described in
  http://mail-archive.objectweb.org/carol/2005-01/msg00000.html

The original log message can be viewed here:
http://cvs.forge.objectweb.org/cgi-bin/viewcvs.cgi/carol/carol/test/conform/generic/carol_double.xml?rev=1.11.2.2&only_with_tag=carol_1_8_5_br&content-type=text/vnd.viewcvs-markup

The original log message is also reproduced below for convenience

..............................................................................

The purpose of this commit is to change the way we set up and tear
down multiple concurrent processes when running unit tests.

For background information, see these threads:

 - http://mail-archive.objectweb.org/carol/2004-12/msg00005.html
 - http://mail-archive.objectweb.org/carol/2004-12/msg00022.html

The unit tests verify correctness of various RMI implementations
provided by CAROL.  To test remote method calls, we normally need
three different processes running concurrently:

  (a) registry;
  (b) remote server;
  (c) remote client.

(In actuality, this ranges from 2 to 5 concurrent processes under
different scenarios that CAROL currently tests for.)

These processes should be started in the above order and shut down in
the reverse order.  Prior to this commit, CAROL had no _precise_ way
of starting these processes in the right order and tearing them down
correctly.  The desired effect was achieved by using Ant's <parallel>
task in concert with <sleep> to start the processes in the right
order.  For teardown, we were relying on the 'timeout' attribute of
the <java> task.  One of the side effects of this approach was that
the tests took 9 minutes to run regardless of how fast your computer
was.

This commit eliminates the use of sleeps and timeouts.  Instead, we
now rely on the Ant's <waitfor> task to ensure that the required
processes are started in the right order.  Two new helper classes are
introduced to allow us to programmatically shut down the processes by
sending a command over TCP.  These two new classes are
  org.objectweb.carol.jtests.conform.util.ProcessRunner
  org.objectweb.carol.jtests.conform.util.ProcessStopper

The above accounts for the bulk of the changes committed in this
checkin.

Another small change was to _not_ generate javadocs as part of running
tests.

The end result is that tests now take anywhere from 1 to 3 minutes to
finish depending on how fast your machine is.  This is down from 9
minutes.

This commit introduces a seeming regression.  Tests involving either
jrmp1.1 or jrmp1.2 now fail intermittently.  For tests that do not
involve either of these two protocols, there are no regressions.  I
will investigate intermittent failures and commit a fix as soon as I
have it.

The following files are part of this commit:

  build.xml
  test/build.xml
  test/conform/carol_all_tests.xml
  test/conform/generic/carol_double.xml
  test/ext/java.policy
  test/src/org/objectweb/carol/jtests/conform/basic/clients/MultiProtocolTests.java
  test/src/org/objectweb/carol/jtests/conform/basic/server/BasicServer.java
  test/src/org/objectweb/carol/jtests/conform/util/ProcessRunner.java
  test/src/org/objectweb/carol/jtests/conform/util/ProcessStopper.java

The purpose of this commit is to change the way we set up and tear
down multiple concurrent processes when running unit tests.

For background information, see these threads:

 - http://mail-archive.objectweb.org/carol/2004-12/msg00005.html
 - http://mail-archive.objectweb.org/carol/2004-12/msg00022.html


The unit tests verify correctness of various RMI implementations
provided by CAROL.  To test remote method calls, we normally need
three different processes running concurrently:

  (a) registry;
  (b) remote server;
  (c) remote client.

(In actuality, this ranges from 2 to 5 concurrent processes under
different scenarios that CAROL currently tests for.)

These processes should be started in the above order and shut down in
the reverse order.  Prior to this commit, CAROL had no _precise_ way
of starting these processes in the right order and tearing them down
correctly.  The desired effect was achieved by using Ant's <parallel>
task in concert with <sleep> to start the processes in the right
order.  For teardown, we were relying on the 'timeout' attribute of
the <java> task.  One of the side effects of this approach was that
the tests took 9 minutes to run regardless of how fast your computer
was.

This commit eliminates the use of sleeps and timeouts.  Instead, we
now rely on the Ant's <waitfor> task to ensure that the required
processes are started in the right order.  Two new helper classes are
introduced to allow us to programmatically shut down the processes by
sending a command over TCP.  These two new classes are
  org.objectweb.carol.jtests.conform.util.ProcessRunner
  org.objectweb.carol.jtests.conform.util.ProcessStopper

The above accounts for the bulk of the changes committed in this
checkin.

Another small change was to _not_ generate javadocs as part of running
tests.

The end result is that tests now take anywhere from 1 to 3 minutes to
finish depending on how fast your machine is.  This is down from 9
minutes.

This commit introduces a seeming regression.  Tests involving either
jrmp1.1 or jrmp1.2 now fail intermittently.  For tests that do not
involve either of these two protocols, there are no regressions.  I
will investigate intermittent failures and commit a fix as soon as I
have it.

The following files are part of this commit:

  build.xml
  test/build.xml
  test/conform/carol_all_tests.xml
  test/conform/generic/carol_double.xml
  test/ext/java.policy
  test/src/org/objectweb/carol/jtests/conform/basic/clients/MultiProtocolTests.java
  test/src/org/objectweb/carol/jtests/conform/basic/server/BasicServer.java
  test/src/org/objectweb/carol/jtests/conform/util/ProcessRunner.java
  test/src/org/objectweb/carol/jtests/conform/util/ProcessStopper.java

Reverting the change made in 1.27.2.1.

Don't run javadoc as part of running the tests.

Integrate Jacorb into carol

Change message

New carol packaging

*** empty log message ***

jonathan.jar replaced by jeremie.jar

suppress blank

*** empty log message ***

*** empty log message ***

*** empty log message ***

no rebuild with Jeremie

Remote Manageable Registry

Local registry context optimization and serializable bindings for jeremie

local call optimization for jrmp 1.2

remove open orb modifications

add support for openorb

Carol 1.5.1 pre-realase
Correction of Bug 309

Added cmi.

CAROL 1.3.0 commit, this carol release came with

- A new simplify configuration mechanism
- A new LMI (Local Method Invocation) RMI SPI
- Bug Correction (#150 and #154)

tests modifications (simplification)

Changes for Carol defaults values loading from jndi properties

process bootstrap modification

Java remote bootstarper and shell added for test

carol 1.0.2 version

bug 113 correction and xalan junit report jdk1.3 problem correction

Bug 131 correction and javadoc compilation correction

There is two major change in this commit:
- Jeremie management and test is added, but there is probleme with referenceable binding
- IIOP now manage the binding in a CosNaming of Referenceable and of Serialisable Object

build.xml target name re-desing

CVS registering

Initial revision

Back to OW2 Forge