Sounds like a plan. I think I have some time later this month to play around with naether
On Fri, Dec 30, 2016 at 5:58 PM, Antoine Toulme <[email protected]> wrote: > 1.5.1 is slipping into 2017. No worries, we’ll get it down. > > > > On Dec 4, 2016, at 10:04 PM, Antoine Toulme <[email protected]> wrote: > > > >> > >> On Nov 23, 2016, at 2:22 PM, Peter Donald <[email protected]> > wrote: > >> > >> Hi, > >> > >> On Sat, Nov 19, 2016 at 4:12 PM, Antoine Toulme <[email protected]> > wrote: > >> > >>> the board meeting went over well. > >>> > >> > >> great. > >> > >> > >>> We’re still due for a big discussion on how to sustain and attract more > >>> people to the project. I started something, and well now we’re a month > >>> later. > >>> > >> > >> Yep. Sorry - I am not going to be much help until after the xmas season > :( > >> Small child and large family :) > > No worries. > >> > >> 1.5.1 is still very much time bound to Christmas time. Interestingly, no > >>> bugs on 1.5.0 have surfaced but one, so far. > >>> > >> > >> Nothing popped up here in all our testing. So I think it must be fairly > >> solid. > > Cool. > >> > >> > >>> I’m going to try to knock a few things off the bug list. > >>> > >> > >> Great. The requests that I hear are often about how to make it easier to > >> integrate into the wider ecosystem. In no particular order the requests > are; > >> > >> * Easier to launch/install (which your docker work may handle) > > OK. Still much to do there. > >> * Integrate `buildr/custom_pom` into core and just make it the default > pom > >> generated. > > BUILDR-729 filed. > >> * Add a mechanism to more easily declare "provided" dependencies. It has > >> been suggested that something like "compile.provides << :mydep" may work > >> but not sure how this request interacts with `buildr/custom_pom`. Maybe > >> `custom_pom` could be based of this. > > Added as a comment of BUILDR-729. > >> * Add a way to do a "full" release to maven central. I am not sure > exactly > >> what this means but I get the impression that some tools allow you to > >> upload to the maven central staging repository, "close" the repository > and > >> "release" the repository. I currently do steps 2 and 3 manually and > don't > >> find it too onerous but others have suggested that they would like it > >> "fixed”. > > Wow, not sure about this. I’ve been doing some releases to Maven Central > with Buildr and it did look like you need to do those steps manually. > > I filed BUILDR-730 for this. > >> > >> Anyhoo - just in case you need some new ideas ;) > >> > >> > >>> > >>> I played with making a Docker image using a minified JDK9 image to run > >>> Buildr. RJB doesn’t work well with it right now. > >>> https://github.com/atoulme/docker-buildr/blob/master/Dockerfile < > >>> https://github.com/atoulme/docker-buildr/blob/master/Dockerfile> > >>> > >> > >> > >> Interesting. We use an alpine+jdk7 image locally. I may experiment with > it > >> over the weekend ;) > >> > >> > >> -- > >> Cheers, > >> > >> Peter Donald > > -- Cheers, Peter Donald
