It seems to me, the feature you ask belonging to maven-scm-plugin which does not have that capability yet.
For now, the second developer can manually use the info, in the POM, to contruct scm:checkout command -D On 7/13/05, Christian Schlaefcke <[EMAIL PROTECTED]> wrote: > Yann LE DU schrieb: > > >Hi Christian, > > > >I don't know if that answers to your question, but if > >you want to take a pom out of the repository, just > >delete the whole project directory from the > >repository... I always did this way when I needed to. > > > > > > > Not really ;-) But let me explain: > > Imagine the following: > A developer creates a brand new project and configures it for use with > scm. He checks it in and adds the POM to the central maven-repo. > Another developer know wants to work on this project as well on a > different machine. So I wonder how the second developer can use maven to > start working. > > What I have in mind is something like: > Developer 2 retrieves (however) the POM of the project from the central > maven-repo and can now use maven for his/her tasks e.g.: scm:checkout, > java:compile, jar:deploy, whatever ... So maven now checks out the > project from cvs/svn and solves the whatever wanted task. > > My question refers to the first step of the second developer. How will > this developer be able to work with the same project from a central > mave-repo while the project essentials sit in cvs/svn? > > Thanks & Regards, > > Chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
