This is good to know. I was under the impression you had to recompile the plugins that use the dependency. Clearly it's much easier :>
My confusion of this came in with the config.ser found in the plugin directories. I noticed that they had the artifacts listed inside of it. Beyond reading the raw binary I haven't done much research of this file. What exactly is it, and what are the dependencies listed inside of it? I never saw a version in there, so I figure it's just the serialized configuration without the versions? Some plugins for example list the version of all the artifacts in their plan.xml and geronimo-plan.xml, but I see no such version in config.ser. I understand it's not exactly related to this question, but I once had the same question, which is where these questions of mine originated. Quintin Beukes On Mon, Oct 26, 2009 at 4:10 PM, Ivan <[email protected]> wrote: > Edit the var/config/artifact_alases.properties should help you, refer to > http://cwiki.apache.org/GMOxDOC22/substituting-one-module-with-another.html > > 2009/10/26 Russell Collins <[email protected]> >> >> I have a couple of questions about keeping a Geronimo server up to date >> with current versions of binaries that are included with the server. >> Example. I would like to replace the commons-collections library to the >> most current version. How would I go about doing this without breaking the >> server? Are there any dependency/config files that would need to be updated >> so that the server would use a different version of the binary? Please let >> me know how I would go about doing this. >> >> >> >> >> >> Russell Collins >> >> > > > -- > Ivan >
