Hi.
You can actually create any kind of assembly you want: you can instruct Maven
to put the Applet in a directory of your choosing.
However, you're right about the problem of Jetty serving pages from the source
tree, and I don't know how to overcome that particular thing. I'm new to
developin
Steven Coco a écrit :
Hi.
You should create a Parent project, with 2 modules: one for the WebApp, and
another for the Applet. They will build into their own artifacts -- a War for
the WebApp, and a Jar for the Applet -- in your repositories, but they share
the parent project's attributes; and
Hi.
You should create a Parent project, with 2 modules: one for the WebApp, and
another for the Applet. They will build into their own artifacts -- a War for
the WebApp, and a Jar for the Applet -- in your repositories, but they share
the parent project's attributes; and they go into folders in
Hello
Sorry to be a little out of the Tapestry subject but I would like to get
some knowledge from you.
I've got a Java applet which is running in a Tapestry page. Today I'm
using Ant build to build the project, which is compiling Tapestry
application and packaging the Applet in a Jar file. T
