I see. You're right we could use one for production deployment and one development.

What would be the benefit of having two build layouts like this? I guess more specifically, how would it help the deploy process to have the stuff in the build directory?

The main reason I ask is because the real question is whether or not that benefit justifies the effort that would be required to build and maintain the build scripts to do so.

-David


On Apr 6, 2007, at 3:13 AM, BJ Freeman wrote:

Not sure I am following you david.
if you startofbiz in the root like it is now then you are using ofbiz in
developement mode.
if you start ofbiz in the runtime you are using it strictly in binary mode.
so you have both.
the startofbiz we use now, would be developement.
I see the runtime as the deployment to other servers or the release
image for binaries.

am I missing something?


David E. Jones sent the following on 4/5/2007 8:58 AM:

So, in other words: destroy being able to change anything on the fly,
have duplicates of nearly everything in OFBiz, etc?

That would be very different from the run-in-place semantics, and we
would lose a lot of what is nice about OFBiz during development.

-David


On Apr 5, 2007, at 5:45 AM, BJ Freeman wrote:

how about
Leave the build in the components, like they are now for development.

copying all files needed to the runtime folder like that startofbiz.* hotdeploy folder,etc, so the runtime can be the only folder distributed.
it would require a copy section be added to each build.xml


Jacopo Cappellato sent the following on 4/4/2007 12:52 AM:
Now that we have the new "runtime folder", containing all the runtime objects, what about moving all the build/* files from each component
into a new runtime/build/ folder?

In this way the only folder in which there will be files written while
building/running the system will be in the runtime folder.

I see advantages in this approach, especially for the distribution of pre-built releases: the pre-built release could be simply the source
official release + the pre-built objects in the runtime folder.
Also everything apart from the runtime folder could be in a read- only
file system (for example a cd).

Jacopo








Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to