VLT checkouts with version control and lastReplicated data | Community
Skip to main content
willtonkin
willtonkin
Level 2
October 16, 2015
Solved

VLT checkouts with version control and lastReplicated data

  • October 16, 2015
  • 3 replies
  • 1228 views
 

Hi,

I just wanted to check if anyone had an elegant solution to this problem - I use Git heavily in my workflow and I very often checkout my project and have a lot of touched files due to the cq:lastReplicat* properties changing. I have no interest in tracking these sorts of changes so was wondering if their's either a method of ignoring these changes in Git or avoiding checking these properties at all out of the JCR with Vlt?

Thanks

<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" jcr:primaryType="nt:file"> <jcr:content -        cq:lastReplicated="{Date}2014-06-13T15:49:04.596+01:00" +        cq:lastReplicated="{Date}2014-06-20T13:21:46.958+01:00" cq:lastReplicatedBy="admin" cq:lastReplicationAction="Activate" jcr:lastModifiedBy="admin"
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JustinEd3

Hi Will,

If you have lastReplicated propertyes in your version controlled content, I'd suggest revising your workflow to avoid this. In general, a given file (or, really, node), should either be managed through version control or replication (not both).

Justin

3 replies

J
Adobe Employee
JustinEd3Adobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi Will,

If you have lastReplicated propertyes in your version controlled content, I'd suggest revising your workflow to avoid this. In general, a given file (or, really, node), should either be managed through version control or replication (not both).

Justin

willtonkin
willtonkinAuthor
Level 2
October 16, 2015

Hi Justin,

I appreciate your help.

That makes total sense, however, I can't think of a way of working that would separate the two? Would you be able to provide an example of how an individual developer could build whilst testing in both WCM author and publish, maintaining a VC system and avoid this kind of issue?

Thanks,

Will

J
Adobe Employee
JustinEd3Adobe Employee
Adobe Employee
October 16, 2015

Hi Will,

If I understand you correctly, the reason you are replicating git-managed files is because developers are running author and publish both locally? If so, they should be using Maven to deploy to publish.

If this isn't correct, can you explain the workflow you are currently using?

Regards,

Justin

Terms & ConditionsAccessibility statement

Loading footer...