Hi Kristopher, > -----Original Message----- > From: Kristopher Brown [mailto:[EMAIL PROTECTED] > Sent: 13 May 2004 17:18 > To: [EMAIL PROTECTED] > Subject: Inter-plugin dependancy best practices > > Hi, > > How should plugin developers indicate that a plugin is inter-dependant > on anther plugin? Some have suggested a registering mechanism like that > used by the site report. Another way is by modifying a shared variable. >
There is already a mechanism in place. It's called dependencies. Simply add a dependency of type "plugin". For example: <dependency> <groupId>xxx</groupId> <artifactId>yyyy</artifactId> <version>454354</version> <type>plugin</type> </dependency> It has the added advantage to automatically download the dependent plugins if you don't have them in your local repository. The only issues I know are: - you would usually like to say "use version > X.Y" instead of "use version X.Y". If you say "use version X.Y" then you'll have to remember to upgrade the version every time the dependent plugin changes... - if the user wants to use a given version of the dependent plugin then he cannot. A use case for that is for example if there is a bug in the version used then the user will want to use a previous version. I got this problem with the Cactus plugin which was depending on fixed versions of the war and ear plugins and some users complained. [snip] Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
