On 5-Nov-08, at 3:05 PM, Mike Schrag wrote:
> WOBootstrap bases that path off of the WOLocalRootDirectory
> property ... I bet you can point that to somewhere bogus and it
> won't pickup your <that>/Lib/Java/Extensions. This also will break /
> Library/Frameworks, I think, so you have you be embedding (which you
> should be anyway) for this to have a chance of working.
Oh, hey, that would be nice. I'll have to play with that.
I have a couple of apps I support on a server that I don't. The lack
of control over the contents of /Lib/Java/Extensions drives me nuts.
> On Nov 5, 2008, at 2:49 PM, Kieran Kelleher wrote:
>
>> It would be really nice to have a deployment bundle property or
>> launch argument to disable adding that that directory to the
>> classpath in deployment.... wishful thinking ;-)
>>
>> On Nov 5, 2008, at 2:17 PM, Chuck Hill wrote:
>>
>>> On Nov 5, 2008, at 11:15 AM, Kieran Kelleher wrote:
>>>
>>>> Is there a way to prevent the contents of /Library/WebObjects/
>>>> Extensions being added to the classpath in deployment?
>>>>
>>> I don't know of any other than removing the contents or re-writing
>>> wobootstrap.jar.
;david
-- David LeBer Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber twitter: http://twitter.com/rebeld -- Toronto Area Cocoa / WebObjects developers group: http://tacow.org
This archive was generated by hypermail 2.0.0 : Wed Nov 05 2008 - 15:08:56 EST