I have a plugin that needs to execute a seperately installed program. I
don't want the plugin to rely on the user's environment. I would prefer
to specify the executables location via a property. I'd like to have
default properties for different OS's: windows and solaris. I'd like the
goal to fail if the installed program can not be found. I'd also like to
have an OS-independent property that a user could over-ride. So I'm
thinking og a plugin.property file that looks something like this:

  maven.foo.unix.executable=/usr/local/bin/foo
  maven.foo.windows.executable=c:\Program Files\foo

Is a user has the program foo installed somewhere else he can run

  maven -Dmaven.foo.executable=blah/blah/foo ...


So, first is this a good approach? Is it the Maven approach? Finally can
someone point me to an existing plugin that does something similar? I'm
having a hard time getting traction on this problem.

Thanks,
C. Helck



The information contained in this e-mail is confidential. This e-mail is 
intended only for the stated addressee.  If you are not an addressee, you must 
not disclose, copy, circulate or in any other way use or rely on the 
information contained in this e-mail. if you have received this e-mail in 
error, please inform us immediately and delete it and all copies from your 
system.

EBS Dealing Resources International Limited. Registered address: 10 Paternoster 
Square, London EC4M 7DY, United Kingdom. Registered number 2669861.

EBS Dealing Resources, Inc, registered in Delaware. Address: 535 Madison 
Avenue, 24th Floor, New York, NY 10022, USA, and One upper Pond road, Building 
F - Floor 3, Parsippany, NJ 07054, USA.

EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer 
Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku,  Tokyo 104-0033, Japan.

Reply via email to