Community
Participate
Working Groups
I have a launch configuration which is required to be run which generates some code. If that launch configuration isn't run then the project will not compile. (The autogenerated files are not in version control). It would be nice to be able to say in the external tool builders section that you want a particular launch configuration to run at a certain point in the build cycle.
In the external tool builders property page you can specify to copy an existing configuration to run as an external tool.
yes but you can only copy other EXTERNAL configurations. I want a java launch configuration to be run!
Deferred
Is this going to be considered for 3.1?
This is not on the 3.1 plan.
I'd like to see that too. I'd like to run my junit tests on build.
any chance this could be considered for 3.2?
There appear to be 2 workarounds for this: 1. The "export ant build" files will create a an ant task with each of your launch configurations which you can then use in your build system. 2. There is also ant4eclipse which will allow you to launch configurations (http://ant4eclipse.sourceforge.net/). Both of the above solutions have problems which still means we can't use it for our situation.
No committment for 3.2, but re-opening to re-evaluate.
Deferred for post 3.2.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
