well i'll take a dig through jira then and see if there is anything low hanging, otherwise i'll push something tomorrow
- Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Jun 2011 22:26, "Mark Struberg" <[email protected]> wrote: > Stephen, please feel free to go on with the release. > > For fixing the sparse scenario with localCheckout, I'd need to first add the relativePathProjectDirectory info to maven-scm-provider-gitexe. > Afterwards I can parse this info and correctly use it for constructing the local file:// clone URL. > But that will need a bit (+ a fresh maven-scm release) > > LieGrue, > strub > > > --- On Sun, 6/26/11, Stephen Connolly <[email protected]> wrote: > >> From: Stephen Connolly <[email protected]> >> Subject: Re: Request to release maven-release-plugin 2.2 >> To: "Maven Developers List" <[email protected]> >> Date: Sunday, June 26, 2011, 7:30 PM >> cool >> >> - Stephen >> >> --- >> Sent from my Android phone, so random spelling mistakes, >> random nonsense >> words and other nonsense are a direct result of using swype >> to type on the >> screen >> On 26 Jun 2011 18:40, "Mark Struberg" <[email protected]> >> wrote: >> > Hi Stephen! >> > >> > I've fixed the tests now. >> > >> > I'll now go on and try to fix the localCheckout with >> GIT in submodules. >> > >> > LieGrue, >> > strub >> > >> > --- On Sat, 6/25/11, Stephen Connolly <[email protected]> >> wrote: >> > >> >> From: Stephen Connolly <[email protected]> >> >> Subject: Re: Request to release >> maven-release-plugin 2.2 >> >> To: "Maven Developers List" <[email protected]> >> >> Date: Saturday, June 25, 2011, 12:59 PM >> >> i can take a shot. but it will be >> >> Monday before i have the bandwidth. >> >> >> >> - Stephen >> >> >> >> --- >> >> Sent from my Android phone, so random spelling >> mistakes, >> >> random nonsense >> >> words and other nonsense are a direct result of >> using swype >> >> to type on the >> >> screen >> >> On 25 Jun 2011 12:40, "Mark Struberg" <[email protected]> >> >> wrote: >> >> > kk I'll do it this evening. But first someone >> needs to >> >> fix the broken unit >> >> tests (mockReleaseManager missing) ;) Someone >> working on >> >> that already? >> >> > >> >> > LieGrue, >> >> > strub >> >> > >> >> > --- On Sat, 6/25/11, Stephen Connolly < [email protected]> >> >> wrote: >> >> > >> >> >> From: Stephen Connolly <[email protected]> >> >> >> Subject: Re: Request to release >> >> maven-release-plugin 2.2 >> >> >> To: "Maven Developers List" <[email protected]> >> >> >> Date: Saturday, June 25, 2011, 11:37 AM >> >> >> i can give you until noon gmt+1 >> >> >> Tuesday... at that point i need to cut >> >> >> something >> >> >> >> >> >> - Stephen >> >> >> >> >> >> --- >> >> >> Sent from my Android phone, so random >> spelling >> >> mistakes, >> >> >> random nonsense >> >> >> words and other nonsense are a direct >> result of >> >> using swype >> >> >> to type on the >> >> >> screen >> >> >> On 25 Jun 2011 11:32, "Mark Struberg" >> <[email protected]> >> >> >> wrote: >> >> >> > Hi! >> >> >> > >> >> >> > If you'd give me a day (after fixing >> the >> >> broken >> >> >> tests), then I'd like to >> >> >> resolve the problem that a release from a >> sparse >> >> directory >> >> >> in GIT doesn't >> >> >> work if localCheckout is used. >> >> >> > >> >> >> > The reason is pretty simple: I >> currently >> >> construct the >> >> >> local checkout url >> >> >> as file:// + >> >> releaseDescriptor.getWorkingDirectory(). >> >> >> > >> >> >> > Guess we need to put the 'base >> directory' of >> >> the SCM >> >> >> repository >> >> >> ReleaseDescriptor somehow. >> >> >> > >> >> >> > Of course, that's not really a >> blocker issue >> >> because >> >> >> by not using >> >> >> localCheckout all things work fine. >> >> >> > >> >> >> > LieGrue, >> >> >> > strub >> >> >> > >> >> >> > --- On Sat, 6/25/11, Dan Tran <[email protected]> >> >> >> wrote: >> >> >> > >> >> >> >> From: Dan Tran <[email protected]> >> >> >> >> Subject: Re: Request to release >> >> >> maven-release-plugin 2.2 >> >> >> >> To: "Maven Developers List" >> <[email protected]> >> >> >> >> Date: Saturday, June 25, 2011, >> 3:32 AM >> >> >> >> Why not just cut with what we >> >> >> >> currently have? :-) I will >> do my >> >> best to >> >> >> review >> >> >> >> >> >> >> >> -D >> >> >> >> >> >> >> >> On Fri, Jun 24, 2011 at 1:51 PM, >> Stephen >> >> Connolly >> >> >> >> <[email protected]> >> >> >> >> wrote: >> >> >> >> > hervé has been making some >> tweak >> >> today (as >> >> >> have i) >> >> >> >> > >> >> >> >> > if nobody steps up, i >> should be able >> >> to kick >> >> >> off a >> >> >> >> release on Monday. won't >> >> >> >> > have the bandwidth before >> then, and >> >> there are >> >> >> a couple >> >> >> >> of critical issues in >> >> >> >> > jira... be good to do a bug >> scrub >> >> first. >> >> >> >> > >> >> >> >> > Dan, if you can review the >> open >> >> critical >> >> >> issues and >> >> >> >> feed back your feeling >> >> >> >> > on which can be downgraded >> i'll >> >> drive the >> >> >> release. >> >> >> >> Deal? >> >> >> >> > >> >> >> >> > - Stephen >> >> >> >> > >> >> >> >> > --- >> >> >> >> > Sent from my Android phone, >> so >> >> random >> >> >> spelling >> >> >> >> mistakes, random nonsense >> >> >> >> > words and other nonsense >> are a >> >> direct result >> >> >> of using >> >> >> >> swype to type on the >> >> >> >> > screen >> >> >> >> > On 24 Jun 2011 16:42, "Dan >> Tran" >> >> <[email protected]> >> >> >> >> wrote: >> >> >> >> >> Hi >> >> >> >> >> >> >> >> >> >> Can we have a new >> release for >> >> this >> >> >> plugin? I am >> >> >> >> anxious to pick up >> >> >> >> >> http://jira.codehaus.org/browse/MRELEASE-648 >> >> >> >> >> >> >> >> >> >> -D >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> >> >> 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] >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> > 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] >> >> > >> >> >> > >> > >> --------------------------------------------------------------------- >> > 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] >
