David Crossley wrote:
Stefano Mazzocchi wrote:
David Crossley wrote:
snip/
Found it - there is extra whitespace at the end of these
three lines in block.properties, i.e. after the =true
Thank the lord, i am not going mad. Sounds like we
need normalize-space() whenever properties are read.
Call
Nicola Ken Barozzi wrote:
David Crossley wrote, On 18/03/2003 3.37:
Stefano Mazzocchi wrote:
David Crossley wrote:
snip/
Found it - there is extra whitespace at the end of these
three lines in block.properties, i.e. after the =true
Thank the lord, i am not going mad. Sounds like we
need
Stefano Mazzocchi wrote:
Nicola Ken Barozzi wrote:
I had moved the properties in xml files, so that the whitespace
there is really easy to see. Why did we resort back to property
files for it?
Because flat properties are much less verbose and much more friendly
to edit.
you have a
David Crossley wrote:
David Crossley wrote:
David Crossley wrote:
Stefano Mazzocchi wrote:
snip/
try to do a clean checkout, maybe there is something wrong in
your local CVS metadata.
ah, no, wait, what settings are you using for cvs update?
cvs -q -z3 update -d -P cocoon-2.1
Okay, i will try
Stefano Mazzocchi wrote:
David Crossley wrote:
snip/
Found it - there is extra whitespace at the end of these
three lines in block.properties, i.e. after the =true
Thank the lord, i am not going mad. Sounds like we
need normalize-space() whenever properties are read.
Call in the
David Crossley wrote, On 18/03/2003 3.37:
Stefano Mazzocchi wrote:
David Crossley wrote:
snip/
Found it - there is extra whitespace at the end of these
three lines in block.properties, i.e. after the =true
Thank the lord, i am not going mad. Sounds like we
need normalize-space() whenever
David Crossley wrote:
Bernhard Huber wrote:
David Crossley wrote:
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
i made a CVS update, and had no problem running build webapp,
i even tried setting in
Stefano Mazzocchi wrote:
snip/
try to do a clean checkout, maybe there is something wrong in
your local CVS metadata.
ah, no, wait, what settings are you using for cvs update?
cvs -q -z3 update -d -P cocoon-2.1
Okay, i will try the full clean checkout.
--David
David Crossley wrote:
Stefano Mazzocchi wrote:
snip/
try to do a clean checkout, maybe there is something wrong in
your local CVS metadata.
ah, no, wait, what settings are you using for cvs update?
cvs -q -z3 update -d -P cocoon-2.1
Okay, i will try the full clean checkout.
That
David Crossley wrote:
David Crossley wrote:
Stefano Mazzocchi wrote:
snip/
try to do a clean checkout, maybe there is something wrong in
your local CVS metadata.
ah, no, wait, what settings are you using for cvs update?
cvs -q -z3 update -d -P cocoon-2.1
Okay, i will
hi,
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
i made a CVS update, and had no problem running build webapp,
i even tried setting in local.block.properties all
entries from
#exclude.block.XXX=true to
Bernhard Huber wrote:
hi,
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
i made a CVS update, and had no problem running build webapp,
i even tried setting in local.block.properties all
entries from
Bernhard Huber wrote:
David Crossley wrote:
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
i made a CVS update, and had no problem running build webapp,
i even tried setting in local.block.properties
About 4 days ago the build was changed to differently
handle the way blocks are excluded. Now it looks like
those properties are ignored.
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
Would people please
14 matches
Mail list logo
