Hi.
But setting.xml dont allows a <properties/> tag in root.
So, where should I put this element?
For example :
pom.xml <properties> <host>slolen</host></properties>
<url>file:\\${host}\odessa.m2repo</url>
and I want move <properties> <host>slolen</host></properties> to
setting.xml
Thanks
Edwin Punzalan wrote:
Hi,
A direct answer is no. There are no properties file in m2.
And the right way to do it is to put properties that are
project-related in pom -> properties element and properties that are
user-related in settings -> properties element.
Oscar Picasso wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
