[
http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12379113
]
Prasad Kashyap commented on GERONIMO-1974:
--
When a newer version of the module is redeployed, the configuration of the
newer module is marked as load=false, even
[
http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12379119
]
Prasad Kashyap commented on GERONIMO-1974:
--
In my C:\Apache\geronimo\configs\welcome-jetty\target\plan\plan.xml file, I
changed the version number from 1.1 to
[
http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12378253
]
Aaron Mulder commented on GERONIMO-1974:
Another bug releated to this issue -- when you redeploy to get a new version,
the config.xml keeps the original version,
[
http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12377948
]
Prasad Kashyap commented on GERONIMO-1974:
--
Aaron, this new title and description sounds good.
But I still have the problem with the error message on the
[
http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12377953
]
Prasad Kashyap commented on GERONIMO-1974:
--
This is how I think the redeploy should work.
I don't mind if, by default, it replaces the target module entirely,
