Not off-hand, but maybe try doing a "mvn help:effective-pom" to see what the underlying system is interpreting about your pom setup. You might then be able to see if there is some sort of exclusion going on or something. Frankly, I'm confused.

Christian.

On Jul 14, 2009, at 3:06 AM, [email protected] wrote:

Hi Christian,

I have a very simple setup, I don't do anything unusual in my POM.... If I rename the file to use another extension it magically appears and gets copied.

The maven resource filtering mechanism doesn't seem to work correctly, it just ignore xml files. I also did a test to copy the resource using the maven-resources-plugin, which actually does the copy but is causing some erratic behavior in Tapestry, can you suggest anything else I could try?

Thanks,
Peter

----- Original Message -----
From: "Peter Stavrinides" <[email protected]>
To: "Tapestry users" <[email protected]>
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:

<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance " xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd ">
 <modelVersion>4.0.0</modelVersion>
 <groupId>com.albourne.web</groupId>
 <artifactId>castle</artifactId>
 <packaging>pom</packaging>
  <build>
<sourceDirectory>/home/Tapestry5/castle/src/main/java</ sourceDirectory>
   <scriptSourceDirectory>src/main/scripts</scriptSourceDirectory>
<testSourceDirectory>/home/Tapestry5/castle/src/test/java</ testSourceDirectory> <outputDirectory>/home/Tapestry5/castle/target/classes</ outputDirectory> <testOutputDirectory>/home/Tapestry5/castle/target/test-classes</ testOutputDirectory>
   <defaultGoal>package</defaultGoal>
   <resources>
     <resource>
       <filtering>true</filtering>
<directory>/home/Tapestry5/castle/src/main/resources</ directory>
       <includes>
         <include>**/*.xml</include>
       </includes>
     </resource>
   </resources>
   <testResources>
     <testResource>
<directory>/home/Tapestry5/castle/src/test/resources</ directory>
     </testResource>
   </testResources>
   <directory>/home/Tapestry5/castle/target</directory>
   <finalName>castle</finalName>
   <plugins>
     <plugin>
       <artifactId>maven-compiler-plugin</artifactId>
       <configuration>
         <source>1.6</source>
         <target>1.6</target>
         <optimize>true</optimize>
       </configuration>
     </plugin>
     <plugin>
       <artifactId>maven-help-plugin</artifactId>
       <version>2.1</version>
     </plugin>
   </plugins>
 </build>
 <repositories>
   <repository>
     <releases>
       <updatePolicy>always</updatePolicy>
       <checksumPolicy>warn</checksumPolicy>
     </releases>
     <id>Albourne Repo</id>
     <name>Albourne Maven Repo</name>
     <url>http://maven.intern.albourne.com</url>
   </repository>
   <repository>
     <snapshots />
     <id>nexus snapshots</id>
     <name>Albourne Nexus Proxyy</name>
     <url>http://nexus:8081/content/groups/public-snapshots</url>
   </repository>
   <repository>
     <snapshots>
       <enabled>false</enabled>
     </snapshots>
     <id>nexus</id>
     <name>Albourne Nexus Proxyy</name>
     <url>http://nexus:8081/nexus/content/groups/public</url>
   </repository>
   <repository>
     <snapshots>
       <enabled>false</enabled>
     </snapshots>
     <id>download.java.net</id>
     <name>download.java.net</name>
     <url>http://download.java.net/maven/2</url>
   </repository>
   <repository>
     <snapshots>
       <enabled>false</enabled>
     </snapshots>
     <id>central</id>
     <name>Maven Repository Switchboard</name>
     <url>http://repo1.maven.org/maven2</url>
   </repository>
 </repositories>
 <pluginRepositories>
   <pluginRepository>
     <id>nexus</id>
     <name>Albourne Nexus Proxyy</name>
     <url>http://nexus:8081/nexus/content/groups/public</url>
   </pluginRepository>
   <pluginRepository>
     <releases>
       <updatePolicy>never</updatePolicy>
     </releases>
     <snapshots>
       <enabled>false</enabled>
     </snapshots>
     <id>central</id>
     <name>Maven Plugin Repository</name>
     <url>http://repo1.maven.org/maven2</url>
   </pluginRepository>
 </pluginRepositories>
 <dependencies>
   <dependency>
     <groupId>HFDB</groupId>
     <artifactId>hfdb</artifactId>
     <version>5.11-SNAPSHOT</version>
     <scope>compile</scope>
   </dependency>
   <dependency>
     <groupId>Albourne</groupId>
     <artifactId>web-API</artifactId>
     <version>5.11-SNAPSHOT</version>
     <scope>compile</scope>
   </dependency>
   <dependency>
     <groupId>easymock</groupId>
     <artifactId>easymock</artifactId>
     <version>2.4</version>
     <scope>test</scope>
   </dependency>
   <dependency>
     <groupId>easymock</groupId>
     <artifactId>easymockclassextension</artifactId>
     <version>2.4</version>
     <scope>test</scope>
   </dependency>
   <dependency>
     <groupId>easymock</groupId>
     <artifactId>cglib-nodep</artifactId>
     <version>2.1.3</version>
     <scope>test</scope>
   </dependency>
   <dependency>
     <groupId>jdom</groupId>
     <artifactId>jdom</artifactId>
     <version>1.0</version>
     <scope>compile</scope>
   </dependency>
   <dependency>
     <groupId>org.apache.tapestry</groupId>
     <artifactId>tapestry-core</artifactId>
     <version>5.1.0.5</version>
   </dependency>
   <dependency>
     <groupId>log4j</groupId>
     <artifactId>log4j</artifactId>
     <version>1.2.14</version>
     <scope>compile</scope>
   </dependency>
   <dependency>
     <groupId>junit</groupId>
     <artifactId>junit</artifactId>
     <version>4.1</version>
     <scope>test</scope>
   </dependency>
   <dependency>
     <groupId>javax.servlet</groupId>
     <artifactId>servlet-api</artifactId>
     <version>2.5</version>
   </dependency>
   <dependency>
     <groupId>org.chenillekit</groupId>
     <artifactId>chenillekit-tapestry</artifactId>
     <version>1.0.0</version>
     <exclusions>
       <exclusion>
         <artifactId>javassist</artifactId>
         <groupId>jboss</groupId>
       </exclusion>
     </exclusions>
   </dependency>
   <dependency>
     <groupId>org.directwebremoting</groupId>
     <artifactId>dwr</artifactId>
     <version>3.0rc1</version>
   </dependency>
 </dependencies>
 <reporting>
   <outputDirectory>target/site</outputDirectory>
   <plugins>
     <plugin>
       <groupId>org.apache.tapestry</groupId>
       <artifactId>tapestry-component-report</artifactId>
       <version>5.1.0.5</version>
       <configuration>
         <rootPackage>com.albourne.web</rootPackage>
       </configuration>
     </plugin>
   </plugins>
 </reporting>
 <properties>
   <tapestry-release-version>5.1.0.5</tapestry-release-version>
 </properties>
</project>


Thanks,
Peter

----- Original Message -----
From: "Christian Gruber" <[email protected]>
To: "Tapestry users" <[email protected]>
Sent: Monday, 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 the resulting jar/war/ear and are filtered.    Can you
post your pom.xml file (and any parent poms) in case you're overriding
some subtle behaviour?

Christian.

On Jul 13, 2009, at 7:57 AM, Peter Stavrinides wrote:

I potentially found something, Maven seems to be the advocated this
solution below, though I can't seem to get it working still? any
help with this would be appreciated:

<build>
...

<resources>
        <resource>
                <directory>src/main/resources</directory>
                <filtering>true</filtering>
                <includes>
                        <include>**/*.xml</include>
                </includes>
        </resource>
</resources>
...
</build>

Thanks,
Peter

----- Original Message -----
From: "P Stavrinides" <[email protected]>
To: "Tapestry Mailing List" <[email protected]>
Sent: Monday, 13 July, 2009 12:07:23 GMT +02:00 Athens, 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 that
are only available using an XML configuration file for log4j, so I
tried to switch over from the text based .properties file, placing
the XML file as before in 'src/main/resources' but unlike
the .properties file, it does not get published into the WEB_INF/
classes directory, but if I copy it in manually the it works. What
do I have to do to get .xml files published along with
the .tml, .properties and .class files by Maven / Tapestry?

Thanks,
Peter




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Christian Edward Gruber
[email protected]
http://www.geekinasuit.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Christian Edward Gruber
[email protected]
http://www.geekinasuit.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to