Bugzilla – Full Text Bug Listing
| Summary: | Option to move build folder to a ramdisk | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Pavel Sklenak <pavel.sklenak> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
I would like to build workspace projects in ramdisk. For maven, it is quite simple: <profile> <!-- profile for running maven on a different/RAM disk for faster build time --> <id>ram</id> <properties> <target.directory>/tmp/eclipse/${project.groupId}-${project.artifactId}/target</target.directory> <build.dir>/tmp/eclipse/${project.artifactId}/target</build.dir> <build.outputDir>/tmp/eclipse/${project.artifactId}/target/classes</build.outputDir> <build.testOutputDir>/tmp/eclipse/${project.artifactId}/target/test-classes</build.testOutputDir> </properties> </profile> However, with JDT is not so easy. In preferences there is Java > Build Path > OutputFolderName > target/classes I would like to specify an absolute path using variables - e.g. /tmp/eclipse/${projectName}/target There is a possibility to create linked folders but creating it for each project manually is painful.