>>
>
> Until now I thought we were just duplicating the list of jar deps and source
folders,
> but I did not realize we were using fully specified filesystem specific paths. That
is
> really really bad.
>
There are no filesystem specific paths, they are all related to current
project in eclipse workspace.
So why is users reporting there being filesystem specific references ?
e.g. what if a jar is from outside the workspace?
-max
> That is why i'm interested in hearing how exadel studio users
were recommended to workaround
> this issue (since I assume it was also an issue in exadel studio)
>
> -max
>
>
>> Thanks,
>> Denis
>>
>> Max Rydahl Andersen wrote:
>>
>>> I just noticed
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137029#... which
>>> asks how users should commit their projects to svn/cvs when our .settings
files contains
>>> hardcoded file references.
>>>
>>> I did not think we still had this so it becomes a very good question.
>>>
>>> How did Exadel do this with Exadel studio ?
>>>
>>> /max
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>
>
>
>
>