Summary: | More integration between custom builders and Eclipse's environment | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | userdeleted_bug262356 |
Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | jerome_lanneluc, remy.suen, thatnitind |
Version: | 3.4 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
userdeleted_bug262356
2008-08-30 16:19:58 EDT
It looks like the use of the Java builder is just an example. The request seems to be more general. However I'm not sure to understand exactly what it is about. Could you please provide a scenario which would describe steps by steps what you expect? (In reply to comment #1) > It looks like the use of the Java builder is just an example. The request seems > to be more general. However I'm not sure to understand exactly what it is > about. Could you please provide a scenario which would describe steps by steps > what you expect? > Sure. I'd like to get my test suite running whenever I save my tested classes. There's a "continuous testing" plugin for 3.1 but not 3.4, therefor I wrote a builder to make it work. The builder is activated on autobuilds (i.e. when you save files). The builder then needs to call a test suite which shows a JFace dialog in case of test failures. Therefore, I need to pass it a classpath pointing to JFace and JUnit. Note that this classpath is _the same_ from the project, because that test suite class wouldn't compile if I hadn't JFace and JUnit in the project's calsspath. So I wrote a ruby script which dynamically discovers the JFace and JUnit jars, mount a classpath string and the calls the java command passing it that classpath string. The builder is that script: you specify ruby.exe as the program to run, the location inside bin folder of your test suite as working dir (because script passes . as classpath), the ruby script name and test suite class name as arguments to ruby.exe. Therefore, when you run a builder you're running it outside Eclipse's context, this si why you need to pass a classpath config. It would be nice however, if you were able to create an "internal builder", that is, you specify a _class_ to run, not an _external program, so you woudn't need to reconfigure your classpath since the class would run under the project's classpath. I think this would have the same effect as being able to activate a Run configuration whenever you save files/ on autobuilds, but I don't know which of them would be suitable. 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. If you have further information on the current state of the bug, please add it. 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. |