Donald, would there be any concerns with letting the plugin dependency
system automatically download and install derby 10.1.1.0 alongside
10.1.3.2 in WAS CE? If that works for you then that could be
accomplished by applying this patch to
http://geronimo.liferay.com/plugins/geronimo-plugins.xml :
49a50
<default-repository>http://www.ibiblio.org/maven2/</default-repository>
Otherwise, as Aaron said the modules should be reinstalled and
re-exported as plugins alongside the changes you requested to the
dependency metadata.
Best wishes,
Paul
On 10/17/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
Just a note -- if you change the Derby dependency, it's best to change
it in the original deployment plan for the Geronimo module, update the
plugin metadata, and build a new plugin file (CAR). Ideally, both the
serialized CAR metadata and the XML plugin metadata will include the
same dependency (e.g. without the version number). If you just change
the XML without changing the original deployment plan and regenerating
the CAR, then the serialized data will likely still have the versioned
dependency.
Thanks,
Aaron
