On Tue, 29 Jul 2008, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> Hey guys - I'm struggling to build the nightly snapshot and I'm sure
> this is a /palmface type problem.
As you've noted yourself, our nightly snapshots aren't really
supported right now - I'll fix the page.
If you check out Ant from
On Tue, 29 Jul 2008, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> I also tried to verify that bug 42277 was closed/fixed in the
> nightly builds, but I see it's not.
>
> String resources only have properties single expanded. If you relied
> on resources being expanded more than once, it no longer
>
I think I misunderstood this particular bug. It appears to be a problem
with $${someprop} versus loading two property files and the first one
containing a ${property} that is set in the second one loaded.
To be explicit, if you have two property files, a.properties and
b.properties, in the first
EJ Ciramella wrote:
I think I misunderstood this particular bug. It appears to be a problem
with $${someprop} versus loading two property files and the first one
containing a ${property} that is set in the second one loaded.
To be explicit, if you have two property files, a.properties and
b.pro
Right - in an ideal world, sure.
We're using ant for deployments and the first file is the MOST specific
file, the secondary one is the more generic file.
So, in a nutshell, we can't alter the order of the property files.
What is interesting though is if all the properties are in the SAME
file,
--- EJ Ciramella <[EMAIL PROTECTED]> wrote:
> Right - in an ideal world, sure.
>
> We're using ant for deployments and the first file
> is the MOST specific
> file, the secondary one is the more generic file.
>
> So, in a nutshell, we can't alter the order of the
> property files.
>
> What is
How does ant choose which properties take precedence?
So say db.port is defined in three properties files (default.properties,
stack.properties and machine.properties).
Generally, we'd load them in this order:
Machine.properties
Stack.properties
Default.properties
Developers re-use default.prop
On Tue, 29 Jul 2008, Kevin Jackson <[EMAIL PROTECTED]> wrote:
> Anyone have an opinion on this patch before I commit changes
I haven't even looked into it, sorry.
It does come with tests, I suppose 8-)
Stefan
-
To unsubscribe
--- EJ Ciramella <[EMAIL PROTECTED]> wrote:
> How does ant choose which properties take
> precedence?
>
> So say db.port is defined in three properties files
> (default.properties,
> stack.properties and machine.properties).
>
> Generally, we'd load them in this order:
>
> Machine.properties
>
Right - I meant to ask, is that possible to do? I'm digging around the
documentation and it's unclear if I can do:
.
Kinda thing...
-Original Message-
From: Matt Benson [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 11:42 AM
To: Ant Developers Li
Actually, there's a much more elegant solution. The core of the issue
is the property value NOT existing at the time property file load.
So here's what we're going to do:
1 - Load the property files in the order we'd like using the kinda thing.
2 - use
3 - Load final.properties.
This gives us
Hi,
While answering a question from a user on the user ml, I've checked the code
to see if we have a version matcher able to work with regular expression, as
I remembered sg like this have been developed before. I've found
PatternVersionMatcher. But it seems this is not documented, not tested and
Xavier,
I've looked at the code, and I can't remember writing such a thing and I can't
remember using it.
The svn history logs indicates I've added the code, so I can only think of 3
options:
- there must be something wrong with my memory
- there went something wrong importing the svn history f
On Mon, Aug 4, 2008 at 9:41 PM, Maarten Coene <[EMAIL PROTECTED]>wrote:
> Xavier,
>
> I've looked at the code, and I can't remember writing such a thing and I
> can't remember using it.
>
> The svn history logs indicates I've added the code, so I can only think of
> 3 options:
> - there must be so
Actually, after thinking about this again with a full stomach, why not
after properties are loaded fully expand them (if there is a value)?
I know the following is very simplistic but just humor me, what if this
were directly in loadFile():
Properties props = new Properties();
try
{
prop
Ignore the "pom.xml" in there - that should have been
something.properties.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 4:32 PM
To: Ant Developers List
Subject: RE: Loading interdependent properties files WAS RE: Trying (and
failing) to bu
16 matches
Mail list logo
