Hi Oscar, I faced the same problem. I "solved" it by using a profile wich has properties with valus to be configured by the developer in settings.xml.
See http://maven.apache.org/guides/introduction/introduction-to-profiles.html The profile is enabled using <activeProfiles> <activeProfile>aProfileName</activeProfile> </activeProfiles> because <activation><activeByDefault/></activation> is not working yet. Martin -----Oorspronkelijk bericht----- Van: Oscar Picasso [mailto:[EMAIL PROTECTED] Verzonden: donderdag 24 november 2005 17:44 Aan: [email protected] Onderwerp: [m2] Properties files Hi, In m1 we could use user specific properties in the pom and these properties could be read from some properties files. What is the similar functionality in m2? Here is what I have found that is somewhat related - you can user -Dsome.property=some.value => It doesn't use a file. - setting.xml for user specification configuration => you cannot use it to set arbitrary properties for a specific pom. - filtering => it allows to set properties to resources but not to poms. - using the pom's properties element => the properties are set in the pom itself, which is what I want to avoid. - same as above, but move all the user specific properties in a parent pom that could be customized by each user The later approach seems to me the closest to the m1 user specific properties files. I would however prefer a simpler properties file instead of an xml (pom) file. I am under the impression that I miss something. What is the right to do it? Thanks Oscar --------------------------------- Yahoo! Music Unlimited - Access over 1 million songs. Try it free. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
