Another option would be to add a new attribute to deployment
plans called something like isCompatibleWith or upgrades.
This attribute would tell Geronimo that it can use this version of the
component in place of the component that it upgrades.
So for v1.0.1 we could use
configuration
Aaron,
Thanks for raising this issue - this is important. It's tacky to
force people to change their plans for a minor version upgrade.
1) Ship 1.0.1 with all the configIds saying 1.0 so there is no issue
for at least that release
I like this option for this branch. It looks as if the plan
It seems like if we move ahead as planned for 1.0.1 and 1.1, we're
going to ship a product with configIds like
geronimo/j2ee-server/1.0.1/car, which means that many deployment plans
written for 1.0 will not be able to be deployed unmodified on 1.0 --
and it will instantly turn a huge number of
