Thank you for the responses
Looks like maven was overriding the default path and using only the defined
by me...
Anyway, this is about maven, not tapestry. Sorry
:)
2008/3/10, Joachim Van der Auwera <[EMAIL PROTECTED]>:
>
> Standard maven behaviour, when you change the resources, then you have
>
Standard maven behaviour, when you change the resources, then you have
to add the maven default path manually or it will not be included.
Kind regards,
Joachim
Marcelo Lotif wrote:
Hi all,
I was trying to add some files to META-INF folder putting this code into my
pom.xml:
Not sure about that, but the META-INF stuff shouldn't be in src/main/
java, but rather in src/main/resources, at which point it will
automatically be put into the .jar. Not sure why what you're doing is
messing things up, but it's certainly against recommended practice for
the maven plugins
That would be a Maven bug, if anything.
-Filip
Marcelo Lotif skrev:
Hi all,
I was trying to add some files to META-INF folder putting this code into my
pom.xml:
META-INF
src/main/java/META-INF
...
To deploy it to tomcat, I'm generating a .war file usin
Hi all,
I was trying to add some files to META-INF folder putting this code into my
pom.xml:
META-INF
src/main/java/META-INF
...
To deploy it to tomcat, I'm generating a .war file using the "mvn package"
command. Ok, this will add the files into the META-I
