Distributed template/script development: support of professional versioning functionalities

In case of a distributed FirstSpirit template and script development process,

FirstSpirit does NOT SUPPORT:

- merging

- conflict handling

- external versioning

Currently, when changes are integrated provided by different parties in just one FirstSpirit project in parallel, changes are not merged and conflicts are not identified. This leads to:

- huge synchronization overhead

- errors

- missing traceability

Feature request:

- provide an interface to integrated external versioning tools like SubVersion, CVS, GIT


- implement merging and conflict handling into FirstSpirit JavaClient

1 Comment
Crownpeak employee
Crownpeak employee

Hi Holger,

Your feature request to provide an interface ti integrate external versioning is implemented since FirstSpirit 5.1.

Best regards