Community
Participate
Working Groups
For an external launch, possibly using ANT, it is often necessary to use Eclipse plugins. I have yet to figure out how this is possible and always end up resorting to today's plugin versions on today's installation path. Of course six months later and the launch is broken for me. It is broken for anyone else or any other machine immediately. Possibly they are available via a "Add Variable..." but ${eclipse_home} is not configurable. There is no "plugin" variable. Much more obviously would be a button similiar to "Add External Jars..." in the launch configuration to support "Add Plugins...".
I've had luck using -cp "${project_classpath:IDE}" as command line argument for launching java as an external builder. Perhaps something like -cp "${eclipse_home}plugins/*" would work. Or using ${target_home} to lock down the plugin versions.
(In reply to Timo Kinnunen from comment #1) > Perhaps something like -cp "${eclipse_home}plugins/*" would work. Thanks. Adding the Variable... ${eclipse_home}/plugins works well. It would be nice if the UI provided a short cut to five years of frustration before raising a Bugzilla query.
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.
The need for a not totally opaque UI remains.
Please reopen if the problem still persists.
(In reply to Ed Willink from comment #6) > The need for a not totally opaque UI remains. Please remove the stalebug flag if you remopen a bug.
