| 33 | | # IF YOU UPDATE THIS CLASSPATH, |
| 34 | | # BE SURE TO UPDATE THE CLASSPATH EVERYWHERE (MORE THAN JUST ONCE) |
| 35 | | # IT OCCURS IN build.xml. FAILURE TO OBSERVE THIS SIMPLE RULE BREAKS |
| 36 | | # ANT-IDE INTEGRATION. |
| 37 | | if [ "$EXPLICIT_ANT_ARGS" == "" ] ; then |
| 38 | | EXPLICIT_ANT_ARGS="-noclasspath -lib \"third_party/ant:third_party/xtc:third_party/junit:third_party/fj:third_party/dstm2:third_party/bcel:build\"" |
| 39 | | fi |
| 40 | | |
| 41 | | export ANT_ARGS=$EXPLICIT_ANT_ARGS |
| 42 | | export ANT_OPTS="-Xmx384M -Xms256M -XX:+UseParallelGC" # -verbosegc" # -XX:+PrintGCDetails" |
| 43 | | export ANT_CALLED_FROM_SCRIPT="yes" |
| 44 | | |
| 45 | | echo Using Ant args $ANT_ARGS |
| 46 | | |
| 47 | | $ANT_HOME/bin/ant $ANT_ARGS $* |
| | 33 | # |
| | 34 | # For NetBeans, you should not need to adjust anything to |
| | 35 | # build and test Fortress. |
| | 36 | # |
| | 37 | # For Eclipse, workspace and ant builds should not require any |
| | 38 | # adjustments, but to run tests using ant within Eclipse, you |
| | 39 | # will need to add junit.jar to |
| | 40 | # build.xml -> Run As -> Ant Build... -> Classpath -> User Entries -> Add JARs... |
| | 41 | # |
| | 42 | $ANT_HOME/bin/ant -noclasspath -lib third_party/junit "$@" |
