• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: wolips.properties hardcoded in build.xml
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wolips.properties hardcoded in build.xml


  • Subject: Re: wolips.properties hardcoded in build.xml
  • From: Bastian Triller <email@hidden>
  • Date: Thu, 06 Jun 2013 13:03:49 +0200

You can create ant configurations for the install target for each customer. There you can override the "wolips.properties" property, pointing to the individual file. You can find the ant configurations under Run->External Tools Configurations ... or through opening the build.xml, context clicking the install target and select Run as ant ... or Ant->Run as ... (no Eclipse open right now ...)

Am 06.06.2013 10:10 schrieb "Markus Ruggiero" <email@hidden>:
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
email@hidden
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      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >wolips.properties hardcoded in build.xml (From: Markus Ruggiero <email@hidden>)

  • Prev by Date: Re: patch for wonders NSArray implementation
  • Next by Date: Using ERRest to output JSON without quotes around a property value
  • Previous by thread: Re: wolips.properties hardcoded in build.xml
  • Next by thread: Re: patch for wonders NSArray implementation
  • Index(es):
    • Date
    • Thread