Should I make these changes for the ScalaJPA project as well? Do we need to notify all of the people who are hosting projects on scala-tools.org, or is everyone pretty much on this list?
Derek On Fri, Nov 6, 2009 at 11:23 AM, Josh Suereth <[email protected]>wrote: > Great, Thanks! > > > On Fri, Nov 6, 2009 at 11:23 AM, Indrajit Raychaudhuri < > [email protected]> wrote: > >> >> Done. Hudson build triggered, we're good if no build fail mail comes in >> next half an hour. >> >> Cheers, Indrajit >> >> On 06/11/09 8:10 PM, Josh Suereth wrote: >> > Anytime soon would be good. I"m leaving the other option open for now >> > (because there's a lot more work to fully disable) but I'm trying to >> > move all projects into a state where they won't break before that >> > change. SO once you're done, I'll send out the email scheduling when >> > hudson is going into maintenance. >> > >> > >> > Thanks! >> > -Josh >> > >> > On Fri, Nov 6, 2009 at 2:11 AM, Indrajit Raychaudhuri >> > <[email protected] <mailto:[email protected]>> wrote: >> > >> > >> > Josh, thank you for driving us do the 'right thing' :) >> > >> > Hudson build would trigger when the pom.xml changes. >> > So do you want your fork (b9588f...) to be applied right away. Or do >> you >> > want us to wait for a pre-set time for the transition? >> > >> > Committers, do you insist a ticket/reviewboard for this. If yes, >> I'll do >> > the needful? >> > >> > Cheers, Indrajit >> > >> > On 06/11/09 6:28 AM, Josh Suereth wrote: >> > > Scala-tools.org's Hudson server will no longer allow local >> > deployment to >> > > the repository. You *must* submit all snapshot/release artifacts >> > > through the nexus webapp. The hudson server will provide a >> > server id >> > > (nexus.scala-tools.org <http://nexus.scala-tools.org> >> > <http://nexus.scala-tools.org>) that will have >> > > appropriate (and appropriately hidden) credentials for nightly >> > > deployments of snapshots. >> > > >> > > As such, the following changes should be made to lift's pom.xml >> (I'm >> > > trying to update your hudson lift configuration to cause the >> least >> > > amount of disruption): >> > > >> > > I have a forked repo (jsuereth/liftweb) with the changes as well >> > (if you >> > > want to use github's "fork queue" feature): >> > > >> > > --- a/pom.xml >> > > +++ b/pom.xml >> > > @@ -806,16 +806,16 @@ >> > > <id>hudson</id> >> > > <distributionManagement> >> > > <repository> >> > > - <id>hudson.scala-tools.org <http://hudson.scala-tools.org> >> > <http://hudson.scala-tools.org></id> >> > > - <url>file:///home/scala-tools.org/www/repo-snapshots >> > <http://scala-tools.org/www/repo-snapshots> >> > > <http://scala-tools.org/www/repo-snapshots></url> >> > > + <id>nexus.scala-tools.org <http://nexus.scala-tools.org> >> > <http://nexus.scala-tools.org></id> >> > > + >> > <url>http://nexus.scala-tools.org/content/repositories/releases >> </url> >> > > </repository> >> > > <snapshotRepository> >> > > - <id>hudson.scala-tools.org <http://hudson.scala-tools.org> >> > <http://hudson.scala-tools.org></id> >> > > - <url>file:///home/scala-tools.org/www/repo-snapshots >> > <http://scala-tools.org/www/repo-snapshots> >> > > <http://scala-tools.org/www/repo-snapshots></url> >> > > + <id>nexus.scala-tools.org <http://nexus.scala-tools.org> >> > <http://nexus.scala-tools.org></id> >> > > + >> > <url>http://nexus.scala-tools.org/content/repositories/snapshots >> </url> >> > > <uniqueVersion>false</uniqueVersion> >> > > </snapshotRepository> >> > > <site> >> > > - <id>hudson.scala-tools.org <http://hudson.scala-tools.org> >> > <http://hudson.scala-tools.org></id> >> > > + <id>nexus.scala-tools.org <http://nexus.scala-tools.org> >> > <http://nexus.scala-tools.org></id> >> > > <url>file:///home/scala-tools.org/www/mvnsites-snapshots/liftweb >> > <http://scala-tools.org/www/mvnsites-snapshots/liftweb> >> > > <http://scala-tools.org/www/mvnsites-snapshots/liftweb></url> >> > > </site> >> > > </distributionManagement> >> > > >> > > >> > > > >> > >> > >> > >> > >> > > >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
