Perhaps this should be a Feature Request ....
I use a hybrid woproject/custom build process, which basically adds
an extra <frameworkset> to the build.xml file ... like so ... in
order to use frameworks outside the "normal" locations:
<frameworks root="." embed="true">
<patternset>
<include name="Library/Frameworks/*.framework" />
</patternset>
</frameworks>
... which works fine with the ant build and ant install commands ...
but I also include the originating Project in my "Build Path >>
Configure Build Path..."
... which allows for the wolips incremental builder to work ...
IT WOULD BE GREAT if the WOProject team decided to deviate from the
standard file locations and add a Project level location for
frameworks (which would need be 'embed="true"' ....)
This way, when adding a reference to a woframework the levels would be:
1) Project level
2) User level
3) Local level
4) System
The current methodology works great if you use frameworks; it breaks
down when you want to use multiple non-conflicting versions or are
actively developing frameworks, which are also needed to run
production applications.
- PJ
On a note related to the Properties discussions going on:
I add 2 new targets to the build.xml files ... for ant stage and ant
deploy ... which just sets the deploy mode ... (dev/stage/deploy) ...
and then ....
I then set up app install vars for app installation ... like
'com.zenn.${deploy.mode}.${app.name}.installPath' & 'com.zenn.
$appname.hostName'
... so that I can have the (3) basic deployment characteristics
covered ... in the Properties file
ant install uses the "dev" <woapplication> configs
ant stage uses the "stage" <woapplication> configs
ant deploy uses the 'deploy" <woapplication> configs
I use a custom framework (with a frameworkPrincipal) that listens for
EOModel notifications, which get handled somewhat similarly ...
com.zenn.${deply.mode}.${EOModel.name}.username ... so that I don't
have to add my own modelAddedNotification for db connection
dictionary mangling ... it just knows ... because it can compare its
host name with those listed in the Properties file .. to figure out
if its being tested locally, being staged for QA, or running on a
production server ... if it doesn't match deploy or staging, then it
assumes dev ...
It sure would be great if ERXExtensions could handle the optional
EOModel overrides without my special framework ... seems like all WO
apps have the same needs for this ...
On Nov 16, 2007, at 11:41 AM, Chuck Hill wrote:
>
> On Nov 16, 2007, at 8:19 AM, Cornelius Jaeger wrote:
>
>> Hi All
>>
>> I didn't find this info anywhere.
>> I need to add frameworks for which i don't have the source to a
>> project.
>> when i want to add them to the classpath i can only choose User,
>> Library, or System level frameworks.
>> is there a location i can put them in, inside the project
>> structure, like jars into Libraries?
>> something like Frameworks?
>
> If the frameworks are just jars (nothing else under Resources/)
> then you can just take the jars out of the framework and use them
> directly. Otherwise, I think you will have to install them in /
> Library/Frameworks or ~/Library/Frameworks.
>
> Chuck
>
> --
>
> 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
>
>
>
>
>
This archive was generated by hypermail 2.0.0 : Fri Nov 16 2007 - 12:40:11 EST