Umm, no.
This question has nothing to do with repositories. It has to do with the
directory structure on the development machines.
John Coleman wrote:
Seems like you have a fundamental misunderstanding of what Maven is
for. Maven is a build tool, similar to Ant. The structure that Maven
"wants" is a conventional way to setup your project so that Maven can
build it with minimal fuss.
A Maven repo and a Subversion repo are two different things. You will
store your Maven project in the Subversion repo, but the compiled
jar/war/artifacts are stored in the Maven repository. This can be as
simple as a file system exposed by an HTTP server - but you will not
generally deploy source code there.
Have a look at the book "Better Builds with Maven" found here
http://maven.apache.org/articles.html
along with some other useful resources.
Coleman
On Feb 19, 2008, at 1:18 PM, Chris wrote:
I'm migrating a number of projects and modules to Maven. I'm confused
on how the directories should be set up.
Maven wants this:
/projectname
/module0
/src
/module1
/src
Subversion wants this:
/root
/projectname
/branches
/tags
/trunk
/module0
/branches
/tags
/trunk
/src
etc.
The way I read the documentation, Maven finds modules based on
directory name, and the svn naming convention is going to mess things up.
Where should /branches, /tags, and /trunk go in a Maven directory
structure?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
John Coleman
TRAX Tech Services
434.509.0063 x116 (w)
434.426.8357 (m)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
