Kumar.Srinivasan at Sun.COM
Wed Apr 2 11:14:09 PDT 2008
I am getting concerned with the scope of the changes that we have
been making, that it might break the legacy/non-modules behavior
of the Jdk.
So I am proposing the following builds and tests:
Currently in place:
1. periodic build and test java/modules for a push on linux only.
2. nightly build and test java/modules for any pushed during that day
on all platforms.
I want to also test for ClassLoader and other functionality, by doing this.
jprt submit -n -stree jdk -ot '.*product.*' \
-rtests '*-*-*-java/module' \
-rtests '*-*-*-tools' \
-rtests '*-*-*-java/lang/Class' \
-rtests '*-*-*-java/lang/ClassLoader' \
-rtests '*-*-*-java/lang/reflect' \
-rtests '*-*-*-sun/misc/ClassLoaderUtil' \
a> So should we run this on all platforms on a nightly or perhaps weekly
b> are there any other tests that makes sense to add ? let me know I will
add it to the above list.
Sun Microsystems, Java Software.
More information about the modules-dev