Re: wolips.properties

On 2011-03-15, at 12:06 PM, Mike Schrag wrote:

> Oh ... Your ANT builds don't work, not your ECLIPSE builds. Yeah, ant needs to have the path to wolips properties passed into it. Normally that would be done in Hudson as a configuration property to the build server.  

I'll be moving that way as soon as I can get a moment.

> build.properties isn't really the ideal place to do it since that is going to be shared by other people on your team.

I see. Team of one, so I didn't run into that issue. :-)

> If it works for you, no sense in rocking the boat. I don't know if we can inject a value into ant properties from inside eclipse. That would probably be the proper fix for that ...

No need, I just wanted to see if there was something wrong with my setup.

Thanks Mike,

David

> 
> On Mar 15, 2011, at 2:22 PM, David Holt wrote:
> 
>> Hi all,
>> 
>> I have just found out that I shouldn't have to include wolips.properties in my individual application's build.properties files. However, if I rely on just the workspace properties settings, I get build errors such as the following when I try to install:
>> 
>> Buildfile: /Users/me/Documents/Workspaces/workspace/Test/build.xml
>> init.properties:
>> init.install:
>> compile:
>> 
>> BUILD FAILED
>> /Users/me/Documents/Workspaces/workspace/Test/build.xml:206: The framework name 'ERExtensions' does not exist.
>> 
>> Total time: 3 seconds
>> 
>> If I do include the wolips.properties setting in build.properties the project will install fine. 
>> 
>> Is there something else that I should be setting?
>> 
>> Thanks,
>> David
>