Summary: | JDT core test suites should be on dev.eclipse.org | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jim des Rivieres <jeem> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.1 M2 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Jim des Rivieres
2002-08-19 14:22:22 EDT
This is already planned for 2.1. Now this isn't as simple, we have to check them all before we do. For instance, many of our suites are tuned for running against licensed class libraries. We are currently reworking them all, and plan to expose them gradually onto dev.eclipse.org. You claim that many suites are not dependent on licensed code ? What are you referring to ? I was thinking of the test suites OTI has written, as opposed to Sun JCK or Plum Hall compiler test suites. For instance, the Java model and AST test suites should be available. Unfortunately some of the Java Model tests use proprietary code as their data. These need to be rewritten. We will also need to add the copyright header to all tests that we intend to make public. PMC request was made to create 3 projects on dev.eclipse.org, and a module: projects: - org.eclipse.jdt.core.tests.compiler - org.eclipse.jdt.core.tests.builder - org.eclipse.jdt.core.tests.model module: - org.eclipse.jdt.core.tests with same commit rights as org.eclipse.jdt.core The 3 test projects are now on dev.eclipse.org. JDT/Core tests are running during the nightly builds and they should also run in the next integration build. Verified. |