RE : [m2] packaging up applets

[Olivier Lamy <ol...@accor.com>]

Have a look here
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycl
e.html 
Section Specifying a New Packaging
You will see it's very easy ;-)

- Olivier

-----Message d'origine-----
De : Christopher Cobb [mailto:christopher.cobb@wfinet.com] 
Envoyé : jeudi 15 décembre 2005 15:17
À : 'Maven Users List'
Objet : RE: [m2] packaging up applets


As a new maven user, I must say that I am surprised that there is no
support for applet scenarios.  The closest information I could find is
here:

http://jira.codehaus.org/browse/MNG-896?vote=vote

When I first visited the page, there was only one vote for this issue
and I have now added my own for a grand total of two votes!  I guess
this will be solved Real Soon Now!  So, in lieu of having an existing
built-in solution, I suppose I will have to create my own solution.  

I would prefer never to have to deal with accidentally using the wrong
copy of the war file (one that doesn't have the applet).  Therefore,
whenever the war file is generated, it should always contain its applet
and all of its dependents.  The applet, et al, needs to be copied to the
war's project directory before the war's package goal is executed.

Perhaps I could get a few hints on how to proceed.  Since I'm a newbie
here, I would be grateful if someone could verify the following outline
of steps.

1. Since "everything is a plugin", I suppose that I will have to write
some kind of plugin to accomplish this.  maven-appletpackager-plugin?

2. Push or pull?  Should the applet push itself into the web app, or
should the web app pull the applet into itself?  Since everything else
is more or less pull-ish around here, I suppose that a pull model would
be better.

3. If it's a pull, then the applet (et al) should be copied to the web
app before the web app gets packaged.  Does that mean that the plugin
should attach to the war's package phase?  Will this ensure that it gets
done BEFORE the war file is generated?

4. If it's a pull, then it would be nice to have some kind of dependency
from the web project to the applet project to ensure that the applet (et
al) is up-to-date before being copied to the web app.  But normal
dependencies get put in the web project's WEB-INF/lib directory.  The
applet does not go here.  It goes in the "top" of the web app's context
(e.g., /applets).  How can I have a real dependency (ensuring
up-to-dateness) but not cause the dependents to get copied to the
WEB-INF/lib directory and have them copied to src/main/applets instead.

QUESTION: So the question is, how do you create a dependency between the
web app project and the applet project without causing the applet and
dependencies be copied into the WEB-INF/lib directory where it does not
belong, and have them copied to src/main/applets instead?

Thanks in advance for any guidance you can provide.

cc

-----Original Message-----
From: Christopher Cobb [mailto:christopher.cobb@wfinet.com] 
Sent: Wednesday, December 14, 2005 4:25 PM
To: 'Maven Users List'
Subject: [m2] packaging up applets

I have one project which an applet and produces, say, applet.jar.

This applet depends on other projects which produce, say,
appletsupport1.jar and appletsupport2.jar.

I have another project which is a web app which will provide the home
for the applet.  Among other things, it will have a jsp page which will
invoke/load the applet.

How do I get the applet and all its dependent jars packaged up properly
in the web app?




-----------------------------------------
Attention:
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorized
to state them to be the views of any such entity. The information
contained in this message and or attachments is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material.  If you received this in error, please
contact the sender and delete the material from any system and destroy
any copies.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org



This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited.
--------------------------------------------------------------------------------------------------------------
Ce message électronique et tous les fichiers joints ainsi que  les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la  personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci  de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites.
-------------------------------------------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org