I'm still very imature on maven and i have some doubts...I'm currently using in my project the subversion SCM tool and I'm having a hard time with maven.
1st: Do I need to configure something on subversion in order to my project to work correctly? My current maven strutcture looks like this:
after I import the root "project" which is responsable for the project as a whole, I tried to import the subprojects as projects in eclipse. After that somehow those component1/2 projects don't syncronize with the SCM repository anymore. Did anyone had this problem before? Is there a better implementation the maven strutcture for my project?
2nd: What is the exaclty purpose of the Maven SCM Project? I tried to read the info on their website, but I still don't understand the real purpose.Would the purpose of this project to be an unique jar respository on subversion/any other SCM or its just the configuration to get maven working in any SCM around?
I would really appreciate some help..
Thanks in advance! And sorry for my poor english.
Alberto Ngai [ April 12, 2007: Message edited by: alberto ngai ]
I'm not sure if I understood all that, and my Maven skills have gotten rusty, but I'll try and explain what I think your problem is.
Maven is designed to do 2 things:
1) automatically resolve dependencies for building complex projects
2) Simplify/standardize project structures
Normally, Maven will automatically fetch dependencies, but these dependencies are generally binary objects - jars. It wouldn't fetch source code, since the idea is that the only people who are using the source code are people who are altering the source code. And if I was to checkout source code, make changes, and then Maven was to write over the changes, it would be most vexing.
So the normal process is that I'd make source code changes on my local machine, test and debug them, and then when done push the source and binaries out to online repositories. The source code archiving would be done via subversion (or CVS, or whatever). There is a specific Maven target, if I recall correctly, that will publish the binary info to an appropriate Maven repository.
There may be a Maven subversion update target as well, I just don't remember. But the important part is that Maven won't be updating your source code archives without your express consent.
Customer surveys are for companies who didn't pay proper attention to begin with.