Hi Taher,
I'd not be against (still in the lean way), but should we not keep at least "java
-jar build/libs/ofbiz.jar ?" (with disclaimer words of precaution)?
What are other opinions?
Jacques
Le 19/08/2016 à 17:50, Taher Alkhateeb a écrit :
Hi Jacques,
On a quick skim through, I highly recommend removing completely any traces
of "java -jar". The reason for my recommendation is that gradle automates
the build process. Exposing end-users to how things happen means exposing
them to implementation details. This has the following negative outcomes:
- Users need to be aware of JVM arguments to properly execute commands
- Changes we might decide to do in the future would break existing systems
because users are exposed to the details of how the system is constructed.
- The ofbiz.jar which is constructed from gradle has hardcoded library
paths that depend on each user's computer setup. Any changes to the setup
would not be reflected correctly using raw java commands. This would
probably confuse people a lot and debugging would be a pain. If you let
Gradle take over the whole thing then you minimize the confusion.
- The syntax for java -jar is more complex
So my recommendation is to replace every occurence of java -jar with
./gradlew "ofbiz --whatever-commands-here".
Taher Alkhateeb
On Fri, Aug 19, 2016 at 6:40 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
Hi,
I have done some wiki documentation update with respect to Gradle
recently. Today I got issues with Confluence which broke my working flow on
the Apache OFBiz Technical Production Setup Guide <
https://cwiki.apache.org/confluence/display/OFBIZ/Apache+
OFBiz+Technical+Production+Setup+Guide> page more than once. So I'd
appreciate reviews, not only on this page but on all recently changed
pages. If you follow Confluence changes, you should be aware of them.
Thanks
Jacques
