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 they go into folders in the parent
projet directory (by convention...).
Then you create an Assembly, which instructs Maven to package the Jar with the
WebApp, and you can deploy this as a single unit.
This should explain most of it:
http://maven.apache.org/guides/getting-started/index.html#how_do_i_build_more_than_one_project_at_once
Thanks Steven. I done like explained. It works for a library but not for
an Applet.
Maven put the Jar Applet in the folder WEB-INF/lib/theApplet.jar but it
is an Applet, so it should be accessible from web pages. It should be
deployed in web content folder.
Another need is the jetty:run.
jetty serves files from the folder src/main/webapp, not from the
target/my-app ...
I'm lose in maven's space. I'd posted here because I think tapestry's
users should resolved that need. I think I'll go to post my questions at
[EMAIL PROTECTED]
Thank you for your help
Cyrille
Ciao.
On Sun June 24 2007 8:58:12 am #Cyrille37# wrote:
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. Tapestry application
and Java applet are in the same Eclipse project.
Now I'm starting to use Maven, which seems to be very used now days.
Do you have a idea on how to make Maven compiling Tapestry's pages and
classes and packaging the Applet in its own jar file ?
Thanks a lot for your feedbacks
cyrille.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
