On Thu, 24 Jan 2008 03:42:13 Mark Hobson wrote: > Hi Michael, > There is another caveat in that it's all or nothing. Using a profile > mechanism will switch all range dependencies into snapshot mode, when > typically a developer only wishes to upgrade a couple. How could this > be achieved using profiles? i can think of two ways off the top of my head * install on the specific project * selective repositories and profiles for different project groups
The real question is what do you hope to achieve by enabling snapshots for a particular project or set of projects. Perhaps a change of direction in the discussion do you use multiple lines and merging to manage what your releases? > > > I'm concerned that MNG-3092 is a one way street where better more > > flexible solutions could exist. But having said that if you did fix 3092 > > it would not adversely affect me right now. And if it does... well I'll > > figure something out. > > I can see the theoretical opposition to fixing MNG-3092, but since > it's impractical and unworkable it seems merely academic. I'm open to At the moment I can do continuous integration in two ways * head to head (configure continuum deployment #1 to do clean install) * latest relevant release to latest relevant release - using version ranges (configure continuum deployment #2 do just do clean test) With mgn-3092 it will be impossible to take one artifact commit a change to the head and see if that breaks any of my other artifacts without changing poms. As the #1 won't pickup any changes because snapshot is not explicitly selected. > suggestions if they still give the efficiency gains that working with > version ranges will provide. I think people just overrate what snapshots provide... a non reproducible... non rollbackable... changes get pushed on me as a developer so i get broken when its incovenient to me... I work on the basic premise that the system should be in a state or releasability not development. Snapshots just bugger that up. And worse it makes people lazy. "Its only a snapshot". Not using snapshots as a norm gives me more power to "smack someone in the head" - if you will excuse the metaphor - if they are not working responsibly. IMO if its not in source control it does not count, there is no trail, no guarantees, no possibility of generating diffs -Perhaps mercurial or svk could mitigate that to some extent - and chances are no recent backups. > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
