Another approach would be to add -1.3 and -1.4
(and -1.5) options to load-time weaving, so the tests in non-Java 5 modules
could test in backward compatibility mode instead of testing against a 1.5
level. These options might also be useful in optimizing weaving for projects
that aren’t using Java 5 features like annotations.
From:
aspectj-dev-bounces@xxxxxxxxxxx [mailto:aspectj-dev-bounces@xxxxxxxxxxx] On Behalf Of Matthew Webster
Sent: Friday, June 09, 2006 6:26
AM
To: AspectJ
developer discussions
Subject: [aspectj-dev] JUnit
Classpath in Batch Testing
One topic of discussion on the last AspectJ call
concerned executing tests with a Java 5 project dependency e.g. weaver5. The
harness dynamically adds these tests when running under Java 5. Unfortunately
with the introduction of LTWWorld (https://bugs.eclipse.org/bugs/show_bug.cgi?id=140695)
all the LTW tests in the "tests" project have an implicit dependency
on the Java 5 projects when run under Java 5. This is OK when running RunTheseBeforeYouCommitTests
because the "run-all-junit-tests" project has the right dependencies.
This is not the case when running individual testcases/suites in the
"tests" project. On workaround is to manually add the relevant
projects to the Eclipse launch configuration but I am concerned how this will
work on the build machine.
I
have looked at the <junit> task in build.xml and assume that "<pathelement location="${aj.jar.dir}/${module.name}-test-all.jar"/>"
is the classpath used for testing a particular project. However I cannot find
where the JAR is built and hence what it comprises. I would like to ensure that
the Java 5 projects e.g. weaver5 are on the classpath when testing _every_
project.
Cheers
Matthew
Webster
AOSD Project
Java Technology Centre, MP146
IBM Hursley
Park, Winchester, SO21 2JN,
England
Telephone: +44 196 2816139 (external) 246139 (internal)
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
http://w3.hursley.ibm.com/~websterm/
