Thanks Matt. I'll be sure to bring up this approach as an option.
From: Matt Milliss
To: Maven Users List
Sent: Mon, November 23, 2009 7:45:03 PM
Subject: Re: Thoughts on build vs deploy time property filtering
To avoid having to build an artifac
nders Hammar
To: Maven Users List
Sent: Mon, November 23, 2009 4:06:11 PM
Subject: Re: Thoughts on build vs deploy time property filtering
Well, I would argue that you should keep all environment specific
configuration outside of your "artifact".
How can you do filtering on deploy? Do y
build time, producing an application inside .tar.gz that can be unpacked and
started, but that requires one build per environment.
From: Anders Hammar
To: Maven Users List
Sent: Mon, November 23, 2009 4:06:11 PM
Subject: Re: Thoughts on build vs deploy time
Well, I would argue that you should keep all environment specific
configuration outside of your "artifact".
How can you do filtering on deploy? Do you explode your jar/war/ear, filter,
and then repack?
/Anders
On Mon, Nov 23, 2009 at 16:59, John Prystash wrote:
> Hi, I was hoping for some thou
Hi, I was hoping for some thoughts from the community about the reasons behind
why one might want to filter at build time versus at deploy time.
Traditionally, our organization built one artifact from version control that
still contained property placeholders. We would filter those artifacts at
