when you create an .xml resource?
Peter
- Original Message -
From: "Christian Gruber"
To: "Tapestry users"
Sent: Tuesday, 14 July, 2009 14:53:27 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Tapestry, Maven and Log4j using an XML properties file
Not off-han
vrinides"
To: "Tapestry users"
Sent: Monday, 13 July, 2009 18:28:09 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: Re: Tapestry, Maven and Log4j using an XML properties file
Hi Christian,
This is my effective pom:
http://maven.apache.org/POM/4.0.0"; xm
Monday, 13 July, 2009 18:28:09 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Tapestry, Maven and Log4j using an XML properties file
Hi Christian,
This is my effective pom:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
13 July, 2009 16:35:45 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Tapestry, Maven and Log4j using an XML properties file
The xml provided looks a lot like the default metadata that occurs if
you don't configure anything. Resources are copied from /src/main/
resources into t
hens, Beirut,
Bucharest, Istanbul
Subject: Tapestry, Maven and Log4j using an XML properties file
Hi,
I am not sure if this is if fact a Maven issue more than it is a
Tapestry one... apologies if it is, but basically I have some new
logging requirements that will use the range and match filters
*.xml
...
Thanks,
Peter
- Original Message -
From: "P Stavrinides"
To: "Tapestry Mailing List"
Sent: Monday, 13 July, 2009 12:07:23 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Tapestry, Maven and Log4j using an XML properties fi
Hi,
I am not sure if this is if fact a Maven issue more than it is a Tapestry
one... apologies if it is, but basically I have some new logging requirements
that will use the range and match filters that are only available using an XML
configuration file for log4j, so I tried to switch over from
