Hi Alex, is there a chance to get the BUILDR-486 in the one or the other way into the next release? I'm fine with making the changes private to not expose a public API to live with it. But having the build dependencies listed in the pom is a nice addendum IMO.
Also I had an issue with the svn release function, I hope that I can find some time to dig into that. Tammo On Mon, Jan 31, 2011 at 07:07, Alex Boisvert <[email protected]> wrote: > Sure. > > Just to be clear, I'm aiming for a release candidate on Sunday (Feb. 6th) so > we have another 7 days to get changes/fixes into the codebase. > > alex > > > On Sun, Jan 30, 2011 at 4:40 PM, Peter Donald <[email protected]>wrote: > >> Hi, >> >> I tested it out on all our builds and only found one issue. JIRA is >> down for system maintenance right nowso I have attached a patch to >> address this but am away from the computer with the key to access svn >> atm. So if you could make sure this change gets in before release I am >> +1 for a release. The message for the commit should be something like >> >> ------------------------------------ >> Ensure that the IDEA module is generated correctly when the module >> contains no java files. >> >> Without this change the output directory would be the project root >> which would end up being excluded as a result. This problem was caused >> by the refactor of the plugin prior to migrating it into buildr core. >> ------------------------------------ >> >> On Fri, Jan 28, 2011 at 4:54 PM, Alex Boisvert <[email protected]> >> wrote: >> > I'm thinking about releasing Buildr 1.4.5 towards end of next week. I >> want >> > to keep pushing regular releases out and I think we have a fair number of >> > issues/changes that would benefit our users. >> > >> > If you want to get anything else in this release or feel the timing isn't >> > right, please shout. >> >> -- >> Cheers, >> >> Peter Donald >> > -- Tammo van Lessen - [email protected] - http://www.taval.de
