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




On Fri, Oct 17, 2014 at 11:50 AM, Taher Alkhateeb <
[email protected]> wrote:

> 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 proposition is
> in delivering requirements rather than in providing propriety solutions.
> This only makes a difference if you have a massive java API built on top of
> the framework. This of course is my personal opinion.
>
> Taher Alkhateeb
> On Oct 17, 2014 5:49 PM, "Integrin" <[email protected]> wrote:
>
> > 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 and exclude (Java Source Code
> > etc)
> >     . How are other Ofbiz users doing Production Build, do we know a list
> > of artifacts that are required to run the project.
> >     . Appreciate any pointers or any documentation in this regard,
> >
> > Regards
> >
> >
> >
> > On Fri, Oct 17, 2014 at 10:43 AM, Integrin <[email protected]>
> > wrote:
> >
> > > 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
> > >
> > >
> >
>

Reply via email to