On Mon, 08 Nov 2010 14:36:33 -0200, Christian Riedel
<cr.ml...@googlemail.com> wrote:
Hi Nicolas & Thiago!
Hi!
- I use Maven to generate my Manifest.mf (Tapestry-Module-Classes).
Auto-resolving artifacts means there is no maven-generated manifest.mf
available. You have to create one that is similar to the generated one
and store it in src/main/resources/META-INF for example.
I do that too.
- New files are not copied over automatically.
m2eclipse-generated .project file excludes the contents of
src/main/resources from being copied to target/classes. Change this
manually in the project properties.
After being angry at maven for those pitfalls I decided to give that
RunJettyRun plugin a try.
I still have to provide a manually created manifest.mf but new resources
are at least read in automatically.
While developing, I temporally use @SubModule in the WAR project's
AppModule to load the modules in other projects.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
