Yes close. With a little bit of tweaking i believe you can remove entity
definitions but that is hardly useful. The real value and hard work is in
the user interface, the services (java, groovy, minilang, auto etc...) And
the wiring between them. Most of this stuff is open.
On Oct 17, 2014 7:20 PM,
Thanks Taher for sharing your thoughts, I agree with your opinion, while
further evaluating this,
if i were limit the production release artifacts to only Bare Bones
required, seems like Java source code is
the only candidate that is eligible for exclusion, Is this a fair statement?
Regards
Sakthi
Hi Integrin,
You know I thought about this for a while when deploying to our clients. In
my opinion removing the java source files although easy does not have a lot
of significance because the whole system is open (entities, service
definitions, the controller mappings and so on). Our value propos
Please accept my apologies, mail sent quickly...
. In essence the entire project including java source
code/configuration is present in the location from which the project is run
. For Production environment i would like to ONLY include artifacts
that are required for running the project an
Hi Ofbiz Users,
- What is the recommended best practice for Ofbiz Production Build
- I have been Playing with Ofbiz for a bit now
. In my Test/Local environment i build Ofbiz using Ant and start/stop
using shell scripts, from within the project
