Seeing as this might take some time, I committed an (untested!) fix
in 3793. Lemme know how it works.
Cheers, Anjo
Am 25.01.2007 um 09:00 schrieb Anjo Krank:
> The problem is that the two build systems - WOLips and woproject -
> are working in different ways with different parameters. In WOLips,
> you start with a fixed "root" and then use a patterset from there.
> In woproject, you can define the root where you want it, which is
> in fact what makes sense, as you may not always include from /
> Library but from your versioned releases or build directory etc.
>
> The bug you are seeing was introduced as a side effect of fixing
> the classpath-order bug (WOL-214) which introduced some very hard-
> to-find bugs when you are using a lot of properties. The reason I
> wasn't seeing it is that I don't use the WOLips properties for my
> ant builds anymore because of what I outlined above.
>
> Now, we could fix this by yet more obscure code in the WOApp task,
> but a real solution would be to allow for some way in WOLips to set
> the "dir" or "root" parameter on the frameworks, resources and
> wsresources tasks... but I have to say, if I had a good idea on how
> to do that (UI wise, I mean), I'd have done it a long time ago :)
>
> So it'd be a Good Thing (tm) to revive the .WOLips file, add the
> needed config information there, make the ant tasks read it and
> create some UI to configure it. (And take care that a simple
> opening a project on another developers machine doesn't re-create a
> totally different file) A nice side effect would be that there are
> a ton of files less to worry about in version control.
>
> For the time being, I'd advise you to use the "bundles" property so
> the two systems don't step on each others toes or adapt the ant
> path manually.
>
> Cheers, Anjo
>
> Am 25.01.2007 um 07:58 schrieb Alan Zebchuk:
>
>> Yes it seems to be a bug that has popped up in some of the recent
>> builds.
>>
>> It was working correctly previously.
>> I believe it's related to WOL-283
>>
>>
>> On 25-Jan-07, at 1:37 AM, Lachlan Deck wrote:
>>
>>> Hi there,
>>>
>>> a slight problem...
>>>
>>> On 12/01/2007, at 4:59 AM, Anjo Krank wrote:
>>>
>>>> <frameworks root="${wo.wolocalroot}/Library/Frameworks"
>>>> embed="true"
>>>> bundles="ERJars/ERExtensions/PostgresqlPlugIn/Ajax/
>>>> ERDirectToWeb/ERJavaMail/ERWebServices/JavaWOExtensions/
>>>> LUNeutralLook">
>>>> </frameworks>
>>>
>>> I've got the following:
>>>
>>> <woapplication name="${project.name}" ...>
>>> ...
>>> <frameworks root="${wo.wolocalroot}" embed="true">
>>> <patternset>
>>> <includesfile name="woproject/ant.frameworks.wo.wolocalroot"/>
>>> </patternset>
>>> </frameworks>
>>> <frameworks root="${user.home}" embed="true">
>>> <patternset>
>>> <includesfile name="woproject/ant.frameworks.user.home"/>
>>> </patternset>
>>> </frameworks>
>>> ...
>>> </woapplication>
>>>
>>> When I build the app, the classpaths created have the form:
>>> APPROOT/Frameworks/MyFramework.framework/Resources/Java/
>>> MyFramework.jar
>>>
>>> But the frameworks are found:
>>> APPROOT/Frameworks/Library/Frameworks/*
>>>
>>> Is this a bug in wolips? i.e., not setting the classpath correctly?
>>>
>>> Mac OS X 10.4.8, Ecipse 3.2.1, WOLips 2.0.0.3784
>>>
>>> with regards,
>>> --
>>>
>>> Lachlan Deck
>>>
>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Thu Jan 25 2007 - 04:32:52 EST