Hi,

I am currently working on a Clojure / OSGi integration: www.ogeesource.org

The goal is to extend Clojure with a module-like runtime, not to fully
convert Clojure and Clojure-based applications to OSGi (which would be
quite hard anyway).

So far you can add new modules at runtime and therefore dynamically
extend the classpath (removing/updates are not working yet).

The project is currently in proof-of-concept state and I can not
recommend to start using it! But at least you might want to watch the
github repo to stay informed.

Cheers,

Roman

2009/9/27 Volkan YAZICI <volkan.yaz...@gmail.com>:
>
> For the record, I'm forwarding below reply from Stuart Sierra.
>
> On Fri, 25 Sep 2009, Stuart Sierra <the.stuart.sie...@gmail.com> writes:
>> On Sep 25, 3:02 am, Volkan YAZICI <volkan.yaz...@gmail.com> wrote:
>>> - (System/setProperty
>>>    "java.class.path"
>>>    (str (System/getProperty "java.class.path")
>>>         ":/tmp/code"))
>>
>> The "java.class.path" system property is read-only.  And in the
>> context of dynamic ClassLoaders (like Clojure's) it's largely
>> meaningless.
>>
>>> - (add-classpath "file:///tmp/code")
>>
>> add-classpath does not work in some environments and may be removed in
>> future versions of Clojure.
>>
>> Bottom line: you can't dynamically change the Java classpath.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to