Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334506

Summary:	Commandline archive tool should use return codes != 0 for errors during batch execution
Product:	[Technology] Jubula	Reporter:	Markus Tiede <markus.tiede>
Component:	Core	Assignee:	Markus Tiede <markus.tiede>
Status:	CLOSED FIXED	QA Contact:	Tim Winselmann <tim.winselmann>
Severity:	critical
Priority:	P3	CC:	Achim.Loerke, tim.winselmann
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Markus Tiede

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 1 Markus Tiede

2011-01-21 06:02:31 EST

fixed with
http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=445190eea26a27735de5bb3d709ac614c1993e5d

Comment 2 Tim Winselmann

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