On 1/5/06, Rick Mann <[EMAIL PROTECTED]> wrote:
> But, it seems that a given project would want to be able to create
> all those things at once (that is, the project, and the site stuff
> for it, etc.)
It would be hard for Maven to know what things to add. Some projects
contain only a webapp, some contain only a jar, some both, sometimes
the site is a separate module. I usually run mvn archtype:create
multiple times to get started.
I did think that there was a way to overlay the 'site' archetype on an
existing project, though. (??)
> Now, as I come to think about it more, a different question arises.
> My project will have two major components. One is the webapp itself,
> with all the Struts action code and .jsp files, and the other is a
> Torque project,
Does the Torque module create a jar that gets used in the webapp? If
so, make it a separate module, and have the webapp depend on it. Then
have a parent pom that lists the two modules so you can build the
whole thing at once.
myproject
myproject/webapp
myproject/torque
Maven will figure out that it needs to build 'torque' before 'webapp'.
You should give these more descriptive names. :)
For the website, you can keep the source up in the parent, or you
could make it a separate module.
myproject/src/site/
or
myproject/website.
myproject/website/src/site
In addition, both 'torque' and 'webapp' could have their own src/site
directories, if they were complex enough to need separate
documentation.
... and if you're interested, Struts now has Maven 2 build files for
(most of) 1.3.x. (Just the jars, not the example apps yet.) There's
also a Struts Action Blank Archetype in the sandbox to help you get
started. :)
http://svn.apache.org/repos/asf/struts/sandbox/trunk/archetypes/action-blank/README.txt
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
