From: brett l. <bre...@gm...> - 2014-02-05 14:30:17
|
On Wed, Feb 5, 2014 at 7:45 AM, Stefan Frey <ste...@we...> wrote: > There was something I did not remember was still to be done before I > will release an alpha: > > I intend to update the build process and suggest for this using gradle > (http://www.gradle.org). > > I compared this to adding apache ivy (http://ant.apache.org/ivy/) and > stay with the previous ant/eclipse-build. > > My strong feeling is that I prefer to make the move to the > next-generation build tool. Using xml seemed as weird for a build as > writing Makefiles. And it seems much less restrictive than maven is/was. > > The biggest question I have is... why? What will changing build tools enable us to do that we can't with the existing tools? > I still want to hear if there are any objections, even if it will only > effect myself as I will be responsible for the rails2.0 build. > > The other issue is to use installer to create packages for the different > operating systems. > > Again... why? What benefit does this give us over the current distribution method? > Unfortunately I have not found any reasonable non-commercial tool for > this task. However there are two installer products that provide free > licenses to OS systems: > > Install4j: Requires a link to their page > > http://www.ej-technologies.com/buy/install4j/openSource/enter > > Installbuilder: No such requirement > > > http://installbuilder.bitrock.com/open-source-licenses.html?ModPagespeed=noscript > > Does anyone of you have an objection or recommendation? If I do hear > nothing negative I would apply for a free license for Rails for both > products. > > > I'm not immediately opposed to either idea, provided that there's a good reason to spend the time on that instead of implementing other desirable features. ---Brett. |