On 6 Aug 07, at 9:36 AM 6 Aug 07, Jason Dillon wrote:
Any thoughts on how things might work if the snapshot update bits
where a manual process? So that you have to run mvn with some flag
to pull in new snapshot artifacts, and perhaps another interactive
flag to allow only specific snapshots to be updated (with some
relatively smart warning/suggestion on other snaps to update when
one is selected)?
I really hate when my build was working fine, I'm testing out new
features I've added to my project then run a build and it pulls
down some new snaps and then hoses my build. This happens *way,
way, way* to much.
Anyways, was just something I was pondering. I'd really like to
`mvn -up` just like `svn up` to pull in new bits when I'm ready to
handle them.
If there are locally produced snapshots then the default behavior
should be to always use what's present on the machine and ignore
anything from remote servers.
If you are working on a feature, then other devs may be working on
other features and deploying snapshots but you don't want to consume
what they are producing. Even if you have walked away for 3 days and
come back to your workstation Maven should still only use the
snapshots you have built locally. If we take Geronimo as an example,
your feature may effect a single module or many modules. You should
be able to work on what you are working on without being interfered
with. We'll assume you know what you are doing and when you are ready
to integrate with the rest of the team you will deploy,
A CI machine would also benefit from this as everything is being
built locally and nothing should be pulled from a remote repository.
I think this would be the most sensible default behavior. Something
your -nsu switch tries to encapsulate which is how most people expect
to work. I don't think we need to try and magically guess when a
snapshot should be pulled or used locally.
When you were ready we could have a simple plugin that flushed the
snapshots out of the local repository for the group id of the project
you're currently working with.
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
