Just note that if you have property substitutions in your servicemix.xml or xbean.xml files that you will need to declare a system property in the POM:
<properties> <useServiceUnitAnalyzer>false</useServiceUnitAnalyzer> </properties> As otherwise the jbi-maven-plugin for the jbi-service-unit packaging will load the bean contexts and try to substitute values which will cause all sorts of problems at build time. -----Original Message----- From: Ramon Buckland [mailto:[EMAIL PROTECTED] Sent: Wednesday, 21 February 2007 11:01 AM To: [email protected] Subject: Re: Using properties in xbean.config We use a spring PropertyPlaceHolderConfigurer to provide properties into servicemix.xml and xbean.xml files. so your answer is yes, you would just need to get maven to produce your properties file for you. Howevere, on the same topic, are you aware that from starting from 3.1 the service-unit will include anything in lib/* to the classpath. See http://incubator.apache.org/servicemix/classloaders.html for more information This works best when you use the jbi-maven tooling to create the service-unit because it will put the correct jars in the SU as determined by Maven. On Tue, 2007-02-20 at 05:48 -0800, dgoodine wrote: > I'm coming across a case where I need to put versioned libraries in the > classpath explicitly in the xbean.config for service units. The question > is, can easily I avoid adding the literal library name (i.e. MyLib-1.3.jar) > and use property substitution to keep the version up to date? > > I manage the global version of all my components and libraries as properties > in a master pom.xml file. Is there a way I can use that value to substitute > into the classpath declaration in the xbean.config files? It would be a > pain, and very error-prone, to have to change those files manually every > time the version of a dependency changed. > > If this would require maintaining the versions in a .properties file, can I > then get maven to use that for the properties used in the build process?
