I pop woproject.jar in a specific directory relative to the build root,
and check the appropriate version into source control. This is then
passed to the actual ant invocation that does my build using the -lib
parameter.
-- Bill Michell Development Team Leader, Broadcast Platforms, BBC Future Media & Technology-----Original Message----- From: Chuck Hill [mailto:chil..lobal-village.net] Sent: 22 January 2008 17:05 To: woproject-de..bjectstyle.org Subject: Re: Upcoming Classpath Changes
On Jan 21, 2008, at 9:34 PM, Lachlan Deck wrote:
> On 22/01/2008, at 3:09 PM, Chuck Hill wrote: > >> 2. I am not so sure this is a good idea. Add this to >> wobuild.properties: >> woproject.path=/fully/qualified/path/to/woproject.jar >> It should be easy enough to determine this when WOLips is >> installed / updated, though keeping it up to date might not be so >> easy. > > Yeah, it'd need to be auto-updatable otherwise it's an extra hassle.
Maybe not so much. It does not change very often.
A more interesting problem is how to set this when WOLips is not installed (e.g. if just building from Ant). In that case you have a chicken and egg situation: Ant needs to know where this jar is before it can use it to create this file.
What do people usually do with this jar? Wonder has a copy in build/ lib. I have it in a couple of different (projects) jar frameworks and I have a path to another version in our gvc.properties file: woproject.path=${eclipse.plugins.path}/ org.objectstyle.wolips.woproject.ant_2.0.0.4058/lib/woproject.jar
gvc.properties is read in by out build.xml along with wobuild.properties and friends.
Spotlight says that I have many woproject.jar files of various sizes and dates.
So with all that, maybe we _do_ need some consistency here.
Chuck
>> The motivation for both of these is to be able to add these lines >> to a build.xml file to gain full access to WOProject: >> >> <!-- WOProject tasks and types --> >> <typedef resource="typedef.properties" classpath="$ >> {woproject.path}"/> >> <taskdef resource="taskdef.properties" classpath="$ >> {woproject.path}"/> >> >> Instead of doing them one by one: >> >> <taskdef name="woapplication" >> classname="org.objectstyle.woproject.ant.WOApplication" />
--
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
This archive was generated by hypermail 2.0.0 : Tue Jan 22 2008 - 12:22:17 EST