Dependecies between Software Component Versions

[Former Member]

We just upgraded to XI 3.0 SP22 and our SLD is upgraded to 7.0 SP14. Before the upgrade we defined a versioning strategy. We start our developments in SWCV 1.0. When this version goes to production we lock this version. When development start again on this interface we make the changes in a new SWCV, version 1.1. In this version 1.1 we would make a dependency to version 1.0 so that we don't need to copy all the objects of version 1.0 to 1.1.

In the old SLD we could define this dependecy between SWCV 1.1 to SWCV 1.0, where the SWC names are the same. In the new upgrade SLD we cannot select the same SWC in the dependency. So it is now impossible to define a SWCV dependency inside the same SWC.

Is this a bug or a new feature. If so, do we want SAP to reverse this feature?

Cheers,

Christiaan Schaake.

[Former Member]

hi christiana,

check the blog

DEPENDENCIES

XI: Are you Independent...from your dependencies?

regards

kummari

[Former Member]

Hi kummari,

The blog explains how to use dependecies, but i already know that. The problem is that defining dependecies to same SWC with different version does not work anymore.

Cheers,

Christiaan

[Former Member]

Problem is not going to be solved in PI 7.0. PI 7.1 behaves different, SWCV can have dependencies to different versions that are only defined in the repository.