Bug 93165 - When creating a product that should behave like a normal cmdline app, eclipse.exe becomes hard to use
Summary: When creating a product that should behave like a normal cmdline app, eclipse...
Status: RESOLVED DUPLICATE of bug 173962
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-28 15:41 EDT by Kenneth Ölwing CLA
Modified: 2007-04-26 09:43 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Ölwing CLA 2005-04-28 15:41:50 EDT
I want to build a plain command line app. Setting this up with 'PDE - Product
Configuration' and then building using 'Eclipse Product Export Wizard', the
normal eclipse.exe is copied (and renamed if desired - for this example to foo.exe).

The expectation is now to be able to use foo.exe as any commandline app - piping
in/out of stdout/err etc, checking the exit code etc etc.

Currently I have identified a few issues:
1) Starting the exe, it is not synchronous to my shell. This is because the exe
file is linked to the 'windows' subsystem rather than the 'console' subsystem.
This can be worked around by using a tool such as 'dumpbin'.
2) Exit code processing is not transparent. a) exit codes 23 and 24 are
specially recognized, and b) any exit code other than those and 0 will pop up a
messagebox. Whatever the exit code, the final exit code to the calling app will
be 0.

A suggestion is to make it possible to indicate in the product configuration
wizard that the intended use is as a 'normal' console app, so that the copied
launcher has correct console subsystem linking, as well as becoming completely
exit code transparent.
Comment 1 Pascal Rapicault CLA 2005-04-28 21:24:54 EDT
It seems that you might be better off writing your own executable, or simply directly start java with -jar 
startup.jar.
Comment 2 John Arthorne CLA 2007-04-26 09:28:59 EDT
Support for this is currently being investigated. Andrew, is there another bug report tracking this?
Comment 3 Andrew Niefer CLA 2007-04-26 09:43:46 EDT
1) See bug 173962
2) Propagation of the exit code has been fixed, see bug 173900

*** This bug has been marked as a duplicate of bug 173962 ***