The main purpose if scm:checkout is to allow user to fetch the source base on a scmurl input ( thru -DconnectionUrl), However it also can pickup the connectionUrl in the pom.xml of the execution directory ( your pom). Because of that and to work for both cases, your source files are checked out to another directory ( target/checkout) sinse we dont want the checkout out to contaminate your existing files.
It is not recommended to pass in -DconnectionUrl=your current dir, since the checkout will removed your current dir first before attemp to fetch from SCM Why you want to automate "commit" after checkout and build? What is the flow of you script? -D On 7/17/06, HUGOT Franck <[EMAIL PROTECTED]> wrote:
Hello, I'd like to know what is the philosophy of using maven2 scm plugin. I put my pom.xml at the root dir of my project. Projet under SVN : MyProject/Pom.xml MyProject/Src/main/java/... ... So with the maven checkout command (mvn scm:checkout...), this pom is located in target/checkout dir. Target/checkout/pom.xml Target/checkout/src/main/java/... Do I have to modify the checkout directory (-D checkoutDirectory) so that the source files will be copied in a MyProject/ dir? Is there a way to checkout, compile( ....) and commit? How can I simply do this? There is a lack of documentation. I don't find a way to do this with maven. I finally decided to use a shell script that extract the source from svn and then use maven for the other goals. Do I have to use the release plugin? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Franck HUGOT SOFINCO - Groupe Credit Agricole Service Urbanisation Des Développements DSI/PAT/DAOS/SUDD Tel : (+33) 01 60 76 54 66 [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
