Still not sure why you need deployment or test configurations in your
applications
You are not the first person to build an N-tiered web application with
many servers.
Why can you not put debugging levels and BaseURLs in JNDI?
Those seem pretty simple things to deal with.
You are not the first person to try to use/misuse profiles for this.
I am not trying to be mean or disrespectful of your intentions, I am
just trying point out some reasons why there is no answer to what you
want to do.
It is not a good way to do things and Maven is not designed to solve
this problem.
You are looking at Maven for the right reasons but Maven is not Ant.
Maven is designed to make it easy to do the right thing and it make make
it hard or impossible to do other things.
I didn't write Maven but I had to deal with the same thing. We didn't
get started out right either and had to change.
I have also read dozens of long conversations here with people more
determined than you to try to find a way to make Maven do what you want.
You also have had advice from others here who are the best Maven experts
in the world (committers to the project ) and you might have observed
that they have not given you a solution. It is not because they are
trying to annoy you or tease you.
Ron
On 20/01/2011 5:18 PM, Jeff wrote:
I don't want to debate our architecture or processes since I have little to
do with defining them, but its an N-tiered web application comprising from
one to dozens of servers. Many of the tests are Selenium Integration tests
on Windows clients hitting remote servers that are mostly Linux. We have
dev and test instances that we hit during development. One of the key
properties that changes is the baseURL used by selenium, as well as
debugging levels.
The integration test code is not currently part of the source for the
application.
The tests never run on the app servers directly (I've never seen anyone do
that anyway...our build servers don't run the web app.), particularly the
integration tests as they are client-based.
We are running the tests from dev workstations for now but will eventually
expand to running a subset of integration tests via Hudson.
We are leveraging as much of Maven through the entire process as possible in
order to maximize reuse, portability and integration moving forward.
Anything else I can clarify?
On Jan 20, 2011 2:24 PM, "Ron Wheeler"<[email protected]>
wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
