Like this:

        <target name="init.properties">
                <property file="build.properties" />
                <property name="mysignaturedir" 
value="/Users/thors/I_AM_LEGEND" />
                <condition property="wolips.properties" 
value="/some/really/creepy/location/for/a/secret/wolips/file">
                        <resourceexists>
                                <file file="${mysignaturedir}" />
                        </resourceexists>
                </condition>
                <property name="wolips.properties" 
value="${user.home}${file.separator}Library${file.separator}Application 
Support${file.separator}WOLips${file.separator}wolips.properties" />

Properties are immutable, so once set it can't be overwritten.

So...

If /Users/thors/I_AM_LEGEND exists (created with touch 
/Users/thors/I_AM_LEGEND):

devc:WOSandkassi thors$ ant
Buildfile: /Users/thors/US/Sandkassi/WOSandkassi/build.xml

init.properties:

BUILD FAILED
/Users/thors/US/Sandkassi/WOSandkassi/build.xml:41: The properties 
'wo.system.frameworks' and 'wo.local.frameworks' must be set. Check that your 
/some/really/creepy/location/for/a/secret/wolips/file is correct.

Total time: 0 seconds
devc:WOSandkassi thors$


Fails because my "/some/really/creepy/location/for/a/secret/wolips/file" 
doesn't exist ;)

If I remove the file, the build succeeds. If I copy the current props file to 
this new name, it works also.


On 6.6.2013, at 08:09, Markus Ruggiero wrote:

The name wolips.properties is hardcoded in each build.xml

<property name="wolips.properties" 
value="${user.home}${file.separator}Library${file.separator}Application 
Support${file.separator}WOLips${file.separator}wolips.properties" />

Is there a way to make this dynamic? From Eclipse/WOLips preferences the name 
of the file is available.  Can ant access this value?

Reason:

I have several customers with several Wonder projects. For each customer I have 
a separate workspace. Having a dedicated wolips.properties per customer (which 
is perfectly doable and works) I can have the customers completely independent 
of each other. Each customer can have its individual WebObjects and Wonder 
version. Also I can prevent customer frameworks (that must be installed for a 
build) to pollute my /Library/Frameworks folder. I would only have to edit the 
name for wolips.properties in all the build.xml. That is doable and is what I 
currently do.

A couple days ago I forgot that the build.xml references a custom named 
wolips.properties and sent the project to the customer. They were not able to 
build the application because at their site they use the standard named 
wolips.properties.

Therefore my question: can the reference to wolips.properties be found from the 
workspace settings and determined dynamically by ant?

Thanks a lot for any help
---markus---



Markus Ruggiero
mailingli...@kataputt.com<mailto:mailingli...@kataputt.com>
Check out the new book about Project Wonder and WebObjects on 
http://www.kataputt.com/





_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      
(Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/thors%40us.is

This email sent to th...@us.is


________________________________

Fyrirvari á tölvupósti / e-mail disclaimer
http://us.is/fyrirvari

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to