The idea is that some settings are not specific to a project
(settings.xml is just a file on your computer, not part of the build).
For example, one thing I have in settings.xml is settings for my local
web proxy. That doesn't make any sense to attach to your project, since
it's probably not applicable to everyone who wants to build said
project. And conversely, I don't have to add that to every single
project I ever try to build.

There is some flexibility in putting certain things in either the POM or
settings.xml. You can create profiles in settings.xml, for example. This
is so that, again, you can deal with build aspects peculiar to your
particular machine. It's a fine line, but there's a pretty good page[1]
that details the concerns with putting profiles into settings.xml
without breaking portability. Or you can just see for yourself what can
go in the POM [2] and what can go in the settings [3]. 

~Dan Allen


[1]
http://maven.apache.org/guides/introduction/introduction-to-profiles.htm
l
[2] http://maven.apache.org/ref/2.0.8/maven-model/maven.html - pom.xml
structre
[3] http://maven.apache.org/ref/2.0.8/maven-settings/settings.html -
settings.xml structure
-----Original Message-----
From: youhaodeyi [mailto:[EMAIL PROTECTED] 
Sent: Sunday, February 24, 2008 2:54 AM
To: [email protected]
Subject: Why is there two configuration files for Maven, settings.xml
and pom.xml


Can I put the configurations in settings.xml to pom.xml? Why does maven
use
two configuration files?

-- 
This message may contain confidential, proprietary, or legally privileged 
information. No confidentiality or privilege is waived by any transmission to 
an unintended recipient. If you are not an intended recipient, please notify 
the sender and delete this message immediately. Any views expressed in this 
message are those of the sender, not those of any entity within the KBC 
Financial Products group of companies (together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise, on the 
part of KBC FP. It is not an offer (or solicitation of an offer) of, or a 
recommendation to buy or sell, any financial product. Any prices or other 
values included in this message are indicative only, and do not necessarily 
represent current market prices, prices at which KBC FP would enter into a 
transaction, or prices at which similar transactions may be carried on KBC FP's 
own books. The information contained in this message is provided "as is", 
without representations or warranties, express or implied, of any kind. Past 
performance is not indicative of future returns.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to