I believe the recommendation from the book is to use a shared Maven installation with a default conf/settings.xml file that is inherited by everyone and can be over-ridden locally. I've not actually tried this though as in my environment, installing a shared application implies running apps off network drives which we generally try to avoid doing. There is probably a better way!
Matt. -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: 16 June 2006 13:56 To: Maven Users List Subject: RE: Shared properties across multiple modules Yeah, that'd work - but what I'd like to do is have a default in each module and let the user override with a profile in their own settings.xml. What's the best way to do this? -----Original Message----- From: Read, Matt [mailto:[EMAIL PROTECTED] Sent: Friday, June 16, 2006 8:09 AM To: Maven Users List Subject: RE: Shared properties across multiple modules Have you tried profiles in your settings.xml? -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 23:35 To: Maven Users List Subject: RE: Shared properties across multiple modules Please - someone out there must be using things like port number across modules, does anyone have a working example of something like this? -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:11 AM To: Maven Users List Subject: RE: Shared properties across multiple modules Any further suggestions about this? This is kind of a pressing issue for me. -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 3:57 PM To: Maven Users List Subject: Shared properties across multiple modules Ok - so I'm filtering resources here and there and now it's come to my attention that there are places where there is some duplication. Is there a way to share properties across multiple modules? If so where do you store this? Through tons of testing, I've found this: - properties defined in the parent's pom override everything else when the build is run from the parent poms level - properties defined in the parent's pom are unavailable when run from the actual modules working directory - settings in filter.properties override anything in profiles.xml - settings in profiles.xml are available to be expanded within the pom.xml file (settings in filter.properties are not) Note that some will be building at the parent pom level for things, some will be running from the module level. For example - the automated build will be running from the top level to do the "mvn install", then from the module level for one module to do the "mvn assembly:assembly". The other argument would be I only want to build ONE module, how can this one module use these shared properties? How do you do this? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail is confidential and intended solely for the use of the individual(s) to whom it is addressed. If you are not the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, copying of , or any action taken in reliance upon, it is strictly prohibited and may be illegal. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail is confidential and intended solely for the use of the individual(s) to whom it is addressed. If you are not the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, copying of , or any action taken in reliance upon, it is strictly prohibited and may be illegal. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
