project auto-update when changes in the repository occur, updating only the changes

[Ryan Zoerner <ry...@gmail.com>]

Hello,

I am new to using Maven and I have just downloaded a snapshot, installed the
snapshot (mvn install) and I have set it up for eclipse using the command
(mvn -Psetup.eclipse).

Doing this took a long time. I am wondering if there is a mechanism already
working in Maven which will look for and download any changes and build only
those updates, into the snapshot that I've set up, or if I must run the
whole script on all the code, any time that I want an update.

Also, in the POM file, am I supposed to make changes there? Does maven make
regular calls to the repository automatically to see what has changed and
already do what I am describing? Is that what scm is, for instance? Do I
need to write a script to do the eclipse setup automatically?

Thank you.

Ryan Zoerner

Re: project auto-update when changes in the repository occur, updating only the changes

[Ryan Zoerner <ry...@gmail.com>]

The reason that I ask if that's what scm is, is that the address from which
I downloaded the snapshot is not the same as the address under the scm tag.

Thank you.



On Mon, Apr 11, 2011 at 9:24 PM, Ryan Zoerner <ry...@gmail.com> wrote:

> Hello,
>
> I am new to using Maven and I have just downloaded a snapshot, installed
> the snapshot (mvn install) and I have set it up for eclipse using the
> command (mvn -Psetup.eclipse).
>
> Doing this took a long time. I am wondering if there is a mechanism already
> working in Maven which will look for and download any changes and build only
> those updates, into the snapshot that I've set up, or if I must run the
> whole script on all the code, any time that I want an update.
>
> Also, in the POM file, am I supposed to make changes there? Does maven make
> regular calls to the repository automatically to see what has changed and
> already do what I am describing? Is that what scm is, for instance? Do I
> need to write a script to do the eclipse setup automatically?
>
> Thank you.
>
> Ryan Zoerner
>
>