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

Bug 350217

Summary:	Store Projects and contents in workspace rather than in database
Product:	[Technology] Jubula	Reporter:	Zeb Ford-Reitz <zeb.ford-reitz>
Component:	Core	Assignee:	Project Inbox <jubula.core-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	enhancement
Priority:	P3	CC:	alexandra.schladebeck
Version:	unspecified
Target Milestone:	1.0
Hardware:	All
OS:	All
Whiteboard:

Description Zeb Ford-Reitz

2011-06-24 04:57:38 EDT

Jubula's storage of Projects in a database makes certain workflows and operations more difficult than they need to be. I think that changing this storage to files in the workspace would make these operations easier.

A concrete example of an operation that would be greatly simplified by this change is granularity in version control. If several testers are working on the same project, and one tester decides that they would like to commit their changes to a version control system (VCS), then all changes from all testers will be committed because the project is exported from the database as a single file. This can be problematic if the other testers' work is not currently "production-ready". If these testers were using a workspace-based Jubula, then only the changes from the individual tester would be committed, allowing the other testers to commit their own work when it is finished.

Comment 1 Alexandra Schladebeck

2011-08-05 11:15:40 EDT

After discussion with the product owner, this enhancement request is being rejected due to the time and effort it would cost to implement. Enhancement requests about features that would make working with e.g. versioning easier (see https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=55), should be entered as new reports.