From: Stefan F. <ste...@we...> - 2014-02-06 06:18:40
|
No it should not be a show stopper for you, as running from/inside Eclipse will be the same as before. I will keep Eclipse myself as development tool for this project, even if it is not my preferred one to ensure that it will always build without any problems inside Eclipse to avoid breaking it for others. So usually you will only have to pull the new code and everything should build automatically in Eclipse. If it does not, please ask. Build tool here refers to build process for the package to publish, which means creating the .jar file and to add all libraries and resource files into a compressed archive (.zip or .tar.gz) for a new release. Stefan On 02/06/2014 04:19 AM, John David Galt wrote: > On 2014-02-05 04:45, Stefan Frey wrote: >> 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. >> >> 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 question is, will I still be able to build the dev tree in eclipse? > > I feel I'm only started on the hugely hard, steep learning curve to be > able to safely write code for this project at all, and it seems like > everytime I turn around, someone wants to make a change like this one > which may be trivial for them but is likely a show stopper for me and > other new devs. > > > > >> >> The other issue is to use installer to create packages for the different >> operating systems. >> >> 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. >> >> ------------------------------------------------------------------------------ >> Managing the Performance of Cloud-Based Applications >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >> Read the Whitepaper. >> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel >> > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |