On Jan 5, 2006, at 6:45 PM, Napoleon Esmundo Ramirez wrote:
Maven should always be run where the pom.xml resides. When you did
a "mvn
archetype:create ...", maven created the directory of your project
that
contains the skeleton and the default pom.xml, so you'd really have
to "cd"
there.
Doing "mvn archetype:create" creates an individual project. If the
project
exists, maven reports a "BUILD ERROR" to avoid ruining whatever's
in the
existing project. I think it's safer that way. In your case,
having the
app and the site residing in a single project, I think you could
just create
the app, then manually do site in it. Or you could treat the app
and site
as separate projects that you could merge later on (manually or as a
multi-project).
Thanks!
I get why archetype:create behaves the way it does. What I guess I'm
unclear on, then, is this. a:create's purpose seems to be automating
the mundane initial project creation tasks (for which I'm grateful).
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.)
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, with schema files, sources, and generated sources. I
was thinking of these being two separate projects, but then I'd want
a single "site" that encompasses all of it. Is this the right way to
think about things?
If so, how do I accomplish this?
TIA!
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
