Thanks Andy for your explaination.
No problem about svn, I'm pretty used to it.
But I'm quite new to maven and I have a couple of month of experience in
Magnolia.
Thanks again.
Matteo
Andy Pippin ha scritto:
Matteo,
One thing to keep in mind is that Subversion is a source code management
tool, and Maven is a build tool. However, Maven does do some management of the
resulting artifacts - which causes a little confusion.
For example, Subversion would keep individual versions of your web.xml, mytags.tld,
MyTag.java, and so forth. Maven would compile, copy, and otherwise manipulate those
files and create the end result - mywebapp.war. The result of a build is referred to as
the "artifact" in Maven-speak.
In order to differentiate between different builds of the web app, Maven also assigns a version
to it (i.e. 1.0-SNAPSHOT). It's best to interpret "snapshot" to mean "the thing
that is going to be released as". So, mywebapp-1.0-SNAPSHOT.war is the artifact that
eventually will be released as version 1.0 of mywebapp.war.
This probably won't help you build your custom webapp using Magnolia, but it
will hopefully clear some things up about Maven and Subversion.
aBp_
----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------
