Summary: | compilerAdapter jar should not be include in the repo | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jeff McAffer <jeffmcaffer> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.1 | ||
Target Milestone: | 2.1 M5 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | |||
Bug Depends on: | 30440 | ||
Bug Blocks: |
Description
Jeff McAffer
2003-01-25 15:57:15 EST
Well for testing purpose we use it too. The original story was that it was overriden anyway. Using it for testing is fine and removing it from the repo should not be a barrier. The jar should be built by an externalToolsBuilder on your project when you load the project into your workspace. For an example of how the other teams do this, see org.eclipse.core.resources. Not deriving it in this way can lead to inconsistencies when you change code that the jar uses but the jar is not recompiled/rebuilt. Olivier - please do the necessary so as to get it recreated on a build action. I assume it only gets created if missing (during the build process). I am waiting to get an ant task from platform core that would allow me to set the derived bit. Right now the script is ready, but the generated file is not set as derived. adapter removed from our contribution. Marking as fixed. derived bit is a separate issue which can be resolved independently. Verified. |