Hi Andrus,
there are some issues when we resolve the nextroot and co trough the
envinronment:
- memory leaking
- a open/close of a terminal on windows
- performance
I'll think it's a good solution to resolve the required properties at
runtime if somebody won't use the wobuild.properites at runtime.
As a side note: The message of the exception is wrong. It should be
woproperties.xml.
Ulrich
On 01.10.2003, at 02:50, Andrus Adamchik wrote:
> Hi everyone,
>
> just wanted to discuss a little change I really need to make to
> WOProject.
> The patch is attached. I am not committing it yet, since doing only
> occasional work with WOProject these days, I may not know all the
> implications.
>
> I have a customer request to create a self-contained build environment
> for
> the set of projects we are developing. For some internal reasons, using
> wobuild.properties is not desirable. When looking for ways around, I
> figured that a limitation that wo.* properties should come from a file
> and
> in no other form is really arbitrary. It is really a shame to get an
> exception like:
>
> org.objectstyle.woenvironment.env.WOBuildPropertiesNotFoundException:
> Could not find wobuild.properties. Run the buildfile:
> build-user-home-wobuild-properties.xml first.
> at
> org.objectstyle.woproject.ant.WOApplication.getWOEnvironment(Unknown
> Source)
>
> when all the needed properties already exist in the Ant environment
> (whatever way they got in there)... Hence, the patch below... Any
> objections to this? If not, I'll commit it in a day or so.
>
> Thanks,
>
> Andrus
> ....coming back to WO roots ... every once in a while :-)
>
>
> <patch.txt>
This archive was generated by hypermail 2.0.0 : Wed Oct 01 2003 - 13:10:27 EDT