Community
Participate
Working Groups
### environment ### user@machine aa $ pwd /tmp/aa user@machine aa $ ls agent awf_exec tools ui # agent, awf_exec, tools, and ui are RCP products user@machine aa $ cd tools/ user@machine tools $ ls about.html about_files configuration features jre libcairo-swt.so plugins tools tools.ini user@machine tools $ cat ../agent/awf_agent.ini -startup plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar --launcher.library plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.0.v20100208 --launcher.suppressErrors -vmargs -Xms50m -Xmx150m -XX:+HeapDumpOnOutOfMemoryError ### starting another rcp product from a relative path ### user@machine tools $ # start agent application from this directory user@machine tools $ ../agent/awf_agent -status usage: tools [-agents <colon-separated names of agents>] [-blackbox] [-bsh <bsh file>] [-build <path>] [-cmd <command>] [-csv <filename of CSV file>] ... # expected: agent application to start # actual: tools application has started instead ### starting another rcp product from an absolute path ### user@machine tools $ /tmp/aa/agent/awf_agent -status usage: tools [-agents <colon-separated names of agents>] [-blackbox] [-bsh <bsh file>] [-build <path>] [-cmd <command>] [-csv <filename of CSV file>] ... ### actual: same problem as above ### user@machine tools $ # trying to start eclipse ide from tools directory user@machine tools $ ~/eclipse/eclipse usage: tools [-agents <colon-separated names of agents>] [-blackbox] [-bsh <bsh file>] [-build <path>] [-cmd <command>] [-csv <filename of CSV file>] ### actual: same problem as above ### This is also reproducible on a windows xp machine. It used to work with eclipse 3.4 and 3.5. We have just migrated to 3.6 Let me know if you need any other information.
eclipse version: Version: Helios Release Build id: 20100617-1415
This is really the same problem as bug 325294 *** This bug has been marked as a duplicate of bug 325294 ***
Does this bug need to be restricted to committers only?
(In reply to comment #3) > Does this bug need to be restricted to committers only? Ping?
(In reply to comment #4) > (In reply to comment #3) > > Does this bug need to be restricted to committers only? > > Ping? Hello! Echo!
Echo echo echo
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Does this bug need to be restricted to committers only? > > > > Ping? > > Hello! > > Echo! Why are you asking? the bug this bug got duplicated to is closed as fixed and not restricted. I don't think we should restrict this one.
(In reply to comment #7) > Why are you asking? the bug this bug got duplicated to is closed as fixed and > not restricted. I don't think we should restrict this one. If you look in the history, it *was* marked as committer-only earlier today. Which is why I asked.
(In reply to comment #8) > (In reply to comment #7) > > Why are you asking? the bug this bug got duplicated to is closed as fixed and > > not restricted. I don't think we should restrict this one. > > If you look in the history, it *was* marked as committer-only earlier today. > Which is why I asked. My mistake, thanks Pascal! ;-)
