Hi Pierre, Okay I'll try to answer and provide as much relevant information as I can.
- So first, the system currently does create a jar file in /build/libs. The name of the jar is the name of the project (currently defaulting to the folder name). You can run the system by typing java -cp build/libs/jarname.jar org.apache.ofbiz.base.start.Start or running the jar directly. - However, it is better to avoid using the jar file directly. Because Gradle is a full programming language + DSL and is therefore a fundamental part of the framework solution. Your best bet is to talk to OFBiz always through Gradle and avoid using it directly. - Hmmmm, the point about not downloading the libraries is a little challenging. Maybe one solution is to copy your $HOME/.gradle directory to the production environment which contains all the dependencies. But anytime you make a dependency change then you need to copy it again. - the rc scripts are really nothing but bash scripts that call your java -jar under the hood right? So the solution very simply is to change the rc scripts to call gradle instead. This is one of the tasks for a WIP of fixing everything in /tools. Does that help? any other logistical problems? BTW this is very good feedback we need that kind of stuff for deployment fine-tuning. I heard others ask similar questions. Regards, Taher Alkhateeb On Sat, Jul 16, 2016 at 6:57 PM, Pierre Smits <pierre.sm...@gmail.com> wrote: > I thought that Gradle was not unlike the other java based build tools like > Ant and Maven, and that it could generate a jar too. > > Ohh. I forgot to mention some other requirements: > > - The 3rd party libraries must reside within the application > - Auditors must be able to track the origin of 3rd party libraries > residing in applications > > Best regards, > > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ > > On Sat, Jul 16, 2016 at 5:51 PM, Pierre Smits <pierre.sm...@gmail.com> > wrote: > > > Hi Taher, > > > > Thanks for your quick response. > > > > The reason why this is needed is because I am limited in my options in > > hardened servers in production environments, as a result of GRC policies > > and procedures. > > This entails (amongst others): > > > > - no ports open than those that are required to access the server > > environment (ssh) or the application (in the case of OFBiz: the > designated > > ajp port. > > - no manual starting of stopping of services other than through > > services (rc scripts) and chron jobs > > - no downloading of software etc from within the server > > - no build processes allowed on application servers when the reside in > > the production environment. > > > > I trust that answers your question. > > > > Best regards, > > > > Pierre Smits > > > > ORRTIZ.COM <http://www.orrtiz.com> > > OFBiz based solutions & services > > > > OFBiz Extensions Marketplace > > http://oem.ofbizci.net/oci-2/ > > > > On Sat, Jul 16, 2016 at 5:33 PM, Taher Alkhateeb < > > slidingfilame...@gmail.com> wrote: > > > >> Hi Pierre, > >> > >> Can I ask what do you want the jar for maybe I can provide an > alternative > >> answer? > >> > >> Taher Alkhateeb > >> > >> On Jul 16, 2016 6:31 PM, "Pierre Smits" <pierre.sm...@gmail.com> wrote: > >> > >> > Hi all, > >> > > >> > I am still working my way through how our gradle implementation works > >> and > >> > how I can apply it in a CI/CD environment. And I still have some > >> questions. > >> > So I hope someone will help me a bit. > >> > > >> > How do I use the Gradle build process to generate the ofbiz executable > >> (the > >> > jar file)? > >> > > >> > > >> > Best regards, > >> > > >> > Pierre Smits > >> > > >> > ORRTIZ.COM <http://www.orrtiz.com> > >> > OFBiz based solutions & services > >> > > >> > OFBiz Extensions Marketplace > >> > http://oem.ofbizci.net/oci-2/ > >> > > >> > > > > >
