Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334506 - Commandline archive tool should use return codes != 0 for errors during batch execution
Summary: Commandline archive tool should use return codes != 0 for errors during batch...
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Markus Tiede CLA
QA Contact: Tim Winselmann CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-17 05:48 EST by Markus Tiede CLA
Modified: 2011-02-28 06:34 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Tiede CLA 2011-01-17 05:48:06 EST 
The commandline archive tool should use return codes != 0 for errors during batch execution, e.g. if you are trying to import an already existing project into the Jubula database. Although  the message "The import of project xyz failed" is displayed on the commandline the return code is 0.
Comment 2 Tim Winselmann CLA 2011-02-28 06:34:47 EST 
The commandline archive tool is named dbtool from now.

While importing a project in a Database, which does not jet exists, the dbtool imports the project and returns the exit code 0.

While importing a project in a Database, which already exists, the dbtool does not import the project and returns the exit code 1.


But the error messages are displayed twice --> Bug 338397