nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem using Composer with Source Control

C�dric

Dear all,

I'm encouting a problem when using Composer with Source Control.

I have read the Composer_user documentation, I have put the correct file on Source Control,

but after this, i'm not able to compile project as the default.darfile is readonly.

Do you have a solution to compile project without having several checkout on the 'default.darfile' ( one per developer ), and without putting the file as read instead of readonly?

Regards,

Cédric

Find more posts tagged with

Comments

aflowers001

Which source control ar you using?

I have used TFS, SVN & CVS happily but MS Sourcesafe has always been problematic as its default is to get locked as read-only as opposed to the others which give you read/write files that can be checked in if changed.

What we did for VSS was alter the defaults so that it checks out unlocked/read-write but we never really trusted it would work properly after that hence the moves to SVN or TFS for projects.

C�dric

We are using Harvest SCM version 12.0.2

By reading your message, you confirm that in your case, the default.darfile file can be used, even if it is in read only mode?

But I discover another problem.

I tried to modify a process, which is already into the source control.

I did the checkout, and them import the modifed process from docbase,

Then i have another version of the process instead of replacing the old one !!!

udeleng

Since the DAR file is generate from the sources (artifacts), you should exclude it from being added into the repository. I use SVN, so I added a svn:ignore property to exclude the bin-dar folder from source control.

In regards to a second version of an object being created at install time, you can control this be setting the upgrade option on the project Properties > Documentum Project dialog. The options are Overwrite, Ignore, or Version. You can set it for each object (Right-Click > Properties on artifact) or for the whole project.

C�dric

Dear all,

Thank you for your answers.

The problem is not coming from bin-dar for which I have deployed a ignore file ( .scmignore as I'm using CA SCM )

but it's for default.dardef file.

In order to compile the project after an import, this file shouldn't be in read only.

Now for the process, the option is 'Overwrite Matching Objects', but when I want to import an update version from repository, a version [1] is created instead of replacing the old version.

Temporary solution: I have deleted the old version from source control, then import the update from repository into workspace, then make a checkin

This is working....but i'm not sure this is the correct behaviour.

So for now, I will continue to use this temporary solution.

Regards,

Cédric

FredericFortin

Hi Cédric,

We are facing the same challenges regarding Process import.

What we are doing is we create a temp project to which we import the process. Then we use WinMerge between this temp project and the main one to update the modified artifacts. This way our SCM commit will only contain the delta.

Good luck