Weird. What exactly then is the purpose of:
<frameworks root="ProjectLocal" embed="${embed.ProjectLocal}"
eclipse="true" />
in the standard WO app ant?
But, OK, assuming this is not something that WOLips does at the
moment... I vaguely recall Mike mentioning *somewhere* that this is
difficult to do. Uhm, I think, not exactly sure. Anyway, perhaps it is
my lack of knowledge on the subject (or on the way people organize
their builds), but I can't exactly understand why... Here are some
ways I think this could be handled:
1. Making a subant call to the "build" target on the framework the
project is dependent on, and bundling the dist result...
2. Defining a new standard target in the framework that installs to a
temp location, subanting that target, then bundling the result from
that location, then deleting the temp location. If one wants to
encapsulate this process...
3. Making a subant call to the "install" target of the framework, and
bundling from Lib/Frameworks
4. Building the framework directly into the end result of the app,
would require somehow overriding the destination for the framework
build, not sure if that is possible...
I have successfully done number 3. The problem is that my additions to
build.xml required another file that declared which frameworks this
should be done on. However, since WOLips is internally dealing with
this nowadays, I think that one of the above options could be included
into the standard build process...
Any thoughts, anyone? Mike? Any chance of this happening? It's a
fairly common requirement, no?
F
On Feb 06, 2009, at 14:14, David Avendasora wrote:
> I don't think so. I'm pretty sure you still have to build your
> frameworks first before you can do an "Install" of you Application.
>
> Dave
>
> On Feb 6, 2009, at 12:17 PM, Stamenkovic Florijan wrote:
>
>> Hi all,
>>
>> So, new hotness (latest stable) *can* bundle framework projects
>> directly from the workspace, right? Without those project's first
>> being installed into xxx/Frameworks/, right? I started getting an
>> error (after deleting some frameworks I had in /Lib/Frameworks/ ),
>> which made me go back to some documentation, which made me doubt
>> this concept...
>>
>> So, assuming that WOLips can bundle directly from workspace, any
>> thoughts on why the following would be happening?
>>
>> Thanks,
>> F
>>
>>
>> BUILD FAILED
>> /Volumes/ib3-data/Users/flor385/Projects/Eclipse/DvisAppServer/
>> build.xml:207: Failed to process eclipse frameworks.
>> at
>> org
>> .objectstyle
>> .woproject.ant.FrameworkSet.getEclipseFrameworks(Unknown Source)
>> at org.objectstyle.woproject.ant.FrameworkSet.getJarsPath(Unknown
>> Source)
>> at
>> org
>> .objectstyle
>> .woproject.ant.FrameworkSet.jarsPathForFrameworkSets(Unknown Source)
>> at org.objectstyle.woproject.ant.WOCompile.execute(Unknown Source)
>> ...
>> Caused by: The framework name 'DvisWOModel' does not exist.
>> ... 20 more
>> --- Nested Exception ---
>> The framework name 'DvisWOModel' does not exist.
>> at
>> org
>> .objectstyle
>> .woproject.ant.FrameworkSet.getEclipseFrameworks(Unknown Source)
>> at org.objectstyle.woproject.ant.FrameworkSet.getJarsPath(Unknown
>> Source)
>> at
>> org
>> .objectstyle
>> .woproject.ant.FrameworkSet.jarsPathForFrameworkSets(Unknown Source)
>> at org.objectstyle.woproject.ant.WOCompile.execute(Unknown Source)
>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:
>> 288)
>> ...
>>
>>
>>
>> There is a WO framework called DvisWOModel in my workspace...
>>
>>
>
This archive was generated by hypermail 2.0.0 : Fri Feb 06 2009 - 14:29:49 EST