Joe,
You are completely correct
Quentin,
There is a way to add or remove dependencies using a groovy script,
but I'm not sure how it works. I know you can map an existing
dependency to something else by including a line in var/config/
artifact-aliases.properties. On the left side put the artifactId of
what you want to replace, on the right the artifactId of what you want
instead. Dependencies may or may not include the dependency version,
and the left side has to match, so I usually add two lines for each
substitution, one with and one without the version in the left side.
You can effectively add dependencies by constructing a plugin that
depends on some original plugin dependency plus whatever plugins you
want to add, and substituting it for the original plugin.
thanks
david jencks
On Sep 10, 2009, at 7:36 AM, Joe Dente wrote:
Quintin,
Are you simply editing the Geronimo-plugin.xml/plan.xml in place in
your
repository? I believe if you make any changes to your plugin's
deployment plan you will need to perform a complete re-deploy in order
for those changes to be picked up. I'm not certain about this, but
it is
my understanding that your plugins run off of the java serialized
object
files in your repository, which are created when you deploy a plugin.
Thus editing the deployment plans in place will have no effect.
Joe
-----------------------
Hey
How can I change the dependencies of plugins? I have a feeling that my
login problem is because the OpenEJB module that handles client
connections doesn't have the j2ee-security in it's depedencies, and
thus can't resolve the realm.
So I want to change this, but it seems everytime I edit the plan.xml
and geronimo-plugin.xml, adding new dependencies, they don't get
recognized when I restart.
--
Quintin Beukes
