...
- continue to use common-messages-1.0-adm3.1.104.jar:
- It won't get the new long field in v1.1 model. When it receives a 'MyMessage' serialized by the v1.1, version myLongField will be invisible.
- It won't get the enhancement for detecting stale enums in the 3.2.121 generated code.
- switch to common-messages-1.1-adm3.1.104.jar:
- If will pick up the new long field in v1.1. It can exchange 'MyMessage' with Project A, but Project A won't see the value of myLongField until it upgrades to a 1.1 version of the model.
- It will not get the platform enhancements in the generated code.
- switch to common-messages-1.0-adm3.2.121.jar: If Project B isn't ready for v1.1 of the model, but want the platform enhancements in generated code.
- It won't get the new long field in v1.1 model. When it receives a 'MyMessage' serialized by the v1.1 version, myLongField will be invisible.
- It will get platform enhancements in the generated code.
- switch to common-messages-1.1-adm3.2.121.jar:
- If will pick up the new long field in v1.1. It can exchange 'MyMessage' with Project A, but Project A won't see the value of myLongField until it upgrades to a 1.1 version of the model.
- It will get platform enhancements in the generated code.
- If will pick up the new long field in v1.1. It can exchange 'MyMessage' with Project A, but Project A won't see the value of myLongField until it upgrades to a 1.1 version of the model.