John, that's not the problem. Actually the individual Wonder projects
do not have individual build.xml files. There is high-level ant files
for the whole Wonder framework tree and the Wonder projects
themselves have build.properties files. I think it is fair to assume
that that's because some of the Wonder projects were created way back
in project builder days. Some of the recent new frameworks such as
Ajax do have build.xml files. Guessing again, I would say that WOLips
just "knows" how to build the old project wonder frameworks without
them having a build.xml file. I have the Wonder projects I use
checked out from CVS head into my workspace.
No big deal, I'll just continue with "install latest Wonder into /
Library/Frameworks before deploying" and then build with the regular
embed="true" attributes in the project build.xml file.
Thanks, Kieran
On Mar 30, 2007, at 3:23 PM, John Huss wrote:
> The build.xml files are filtered out by default - click the arrow in
> the top right corner of the package explorer and select Filters. Then
> uncheck build.xml.
>
> John
>
> On 3/30/07, Kieran Kelleher <kieran_list..ac.com> wrote:
>> During a moment of "continuous improvement" I decided to implement
>> Uli's
>> "package and go example" as outlined in the tutorials so that I
>> could embed
>> the Wonder frameworks directly from my workspace into a new project:
>> http://wiki.objectstyle.org/confluence/display/WOL/Embedding
>> +WOFrameworks
>>
>> However, I found that many of the Wonder frameworks do not have *any*
>> build.xml file! So, how are these projects getting built in my
>> workspace
>> without any ant file?!
>>
>> -Kieran
This archive was generated by hypermail 2.0.0 : Fri Mar 30 2007 - 16:08:46 EDT