On Aug 6, 2007, at 12:48 AM, Stephane Nicoll wrote:
Well I guess you should change the update policy instead. SNAPSHOTs is
a crucial concept for us: it allows to continuously integrate our
components, test them, etc.
Yup, it is for me too... I just need to have more control over when
it integrates new bits. I was just working on a POC to test using
GShell as the bootstrapping jvm which forks the Apache Geronimo
process, and I was just trying to make a clean build to test a new
feature and due to the SNAPSHOT resolution after midnight it pulled
some new deps that broke part of the build early, before it could
even get to my stuff... which leaves me now having to figure out what
broke in my POC branch, or making sure that trunk builds, rebranching
and reapplying my POC changes... blah, lots of time wasted. And this
isn't the first time either. Seems to hit me a lot because I'm
actually working late, and often am running builds at 11:59pm and
12:01am.
If your build break way,way,way,... to much it might be worse if you
disable snapshots resolution. Anyway, update policy is the way to go,
IMO.
Ya, I'd like to not make that the default, but for me, I'd really
like to have more control. So I can svn up to pull the latest
sources, then do some mvn -up or something to pull the latest snaps
and build, and if its happy, then go to work... and not have to worry
that if I run an online build again that it might cause something
else to break.
I'd really like to see some more integrated control over how snaps
get updated, so that I can selectively choose which updates I want
and hopefully avoid the hours and hours (and even days sometimes)
when I have to go hound folks or dig into mystery code and mvn -X
logs to figure out what is broke and how to fix it.
--jason
Regards,
Stéphane
On 8/6/07, Jason Dillon <[EMAIL PROTECTED]> 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.
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Large Systems Suck: This rule is 100% transitive. If you build one,
you suck" -- S.Yegge
---------------------------------------------------------------------
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]
