override workflow.task.DependencyTask

Bowker

Please stop me from doing this. I'm hoping there is a better way.

PLC = Publish LiveSite Content workflow

Setup: Page file that has a component that uses a DCR.

Before PLC pushes to production the relationship from the page to the DCR is to the /workarea/.../DCR file.

After PLC pushes to production the relationship changes to /STAGING/...DCR file.

We have enabled the "attach only changed files" to the Add-Dependencies step in the PLC so the next time you push out the .page file the DCR is not attached, even if it's been modified (and/or submitted.) No matter what we do, the PLC does not attach the newly changed DCR.

One solution is to turn off the "only modified files" bean. What I would rather do is override the "add dependencies" task class/bean (workflow.task.DependencyTask) with a home grown version that will add what we want. That includes dependencies of dependencies....

Any guess what how to override that task's object in a "supported" way?

Rick Poulin

Overriding it is a bad (and unsupported) idea here. You'd be at the mercy of whatever they do with the parent code, and it has changed a few times in the 7.x lineage. Attaching files isn't a very complex thing, and your dependency lookups are likely to be entirely custom business logic, so you get very little value out of subclassing the ootb one. Instead, add (or replace with) a new task of your own. Just be sure that it executes before the ootb task that builds the deployment map and you'll be fine. We've done something similar to find and attach the localized equivalents of the submitted pages.