The resource version for component changed from 1.0 to 1.1. (601633)

Unable to save the component type

The resource version for component "preload.sh" changed from "1.0" to "1.1". (601633)

Getting this error message when I try to update a component type to use the latest version of its defining component.

We have a component type that we want to use to define the behaviour of many other components. These components have some common actions between them, such as preload, which use various shell scripts. The basic idea is, since all components perform the same actions, we want to be able to change the script, update the component type, and have that change propagate to all components of that type so that we don't have to modify all components every time we make a small change to a script.

However, it seems like changing the version of a referenced component in a defining component for a type gives the error message above. Is there any way to do what we are trying to do without updating the referenced version in every component every time we make a small change to one shared script?

[1066 byte] By [adrebita] at [2007-11-27 6:10:36]
# 1

If I understand correctly, you are changing a referenced component and want all referencing components to pick up the new version? If so, then, no that will not work. Nor is there a feature to automatically rev all referencing components. The best way I can recommend is have your referencing components checked in via a CLI script. You can run that script when you need to rev the versions of all the referencing components. If I have misunderstood, please let me know.

colinduplantisa at 2007-7-12 17:16:09 > top of Java-index,Administration Tools,N1 Service Provisioning System...
# 2

Sorry, I must have been a little confusing in my description. I am actually changing the version of a component that is referenced by a component type, and I want all components of that type to update to the same version. However, I get the error message when I try to update the component type.

Using a CLI script as you suggested is actually something that we already do, and would work in this case, but it is less than ideal, especially since the first thing we would need to do if we made a new component of this type would be update the reference to the correct version.

adrebita at 2007-7-12 17:16:09 > top of Java-index,Administration Tools,N1 Service Provisioning System...