[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [Dltk-dev] DLTK Environments API
|
Hi Shelby,
Assertion:
This is happen because external Buildpath entries require to contain
paths with environment.
Please use EnvironmentPathUtils.getFullPath() then you create buildpath
entries.
About documentation:
We will provide migration guide in beginning of next week.
Best regards,
Andrei Sobolev.
> Andrei,
>
> The new assertion in the constructor for BuildpathEntry is failing for
> me on Mac OS X. It looks like EnvironmentPathUtils.isFull() returns
> false, because my path doesn't have a device.
>
> Is this to be expected? Do I need to refactor my client code somehow?
>
>
> Also, in general, do you have any documentation for the changes which
> are going to be required for client code once the Environment support
> is complete and stable? I tried a quick sync up, but there were stack
> traces happening all over the place.
>
> Thank You,
> Shelby Sanders
>
>
> On Apr 10, 2008, at 06:44AM, Andrei Sobolev wrote:
>> Hi all,
>>
>> We contributed new infrastructure to access files, execute interpreters
>> and debuggers.
>> This new API allow DLTK to support multiple environments such as local
>> file system, remote file system, embedded systems.
>>
>> We modified DLTK internal API to use this infrastructure.
>> We provide Local Environment and RSE environment implementations.
>> RSE will be accessible as optional feature and not included in DLTK
>> bundles by default.
>>
>> Not all things are done yet, but all tests are passes.
>> So please stay in sync.
>>
>> Best regards,
>> Andrei Sobolev.
>>
>> _______________________________________________
>> dltk-dev mailing list
>> dltk-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
