On 12/19/06, Folke Lemaitre <firstname.lastname@example.org> wrote:
> I have the latest version (1.1.9) of subclipse installed.
> In the meanwhile I've located the source of the issue:
> The problem was that the "Maven 2"/bin (latest version) directory was on
> my path, which contains an older version of JavaHL. Aparently, subclipse
> started using the dlls from the maven distribution instead of the ones
> installed together with subclipse. And with the changes to the local working
> copy format in svn 1.4, the old dlls could not understand my local workign
I do not think that alone would cause it to load the DLL's. Subclipse has
the code in place to counter this and be somewhat sure it gets the right
DLL's. The exception is that Windows has a "feature" where a DLL can only
be loaded one time within a process. So if some Maven code was running in
the same process as Eclipse and it loaded these DLL's before Subclipse got a
chance to load its DLL's, then yes that would cause a problem. But other
than that, Subclipse has code in place to get the DLL's it ships regardless
what is in your PATH.
> The only issue I still have at the moment is that the eclipse "Open Type"
> dialog no longer shows results from that particular project, while it does
> give code completions on imports for that project. It might be that this
> issue is unrelated with the maven trouble, since I installed the 3.3M4build of eclipse..
That is more likely to be a 3.3 problem.
Received on Tue Dec 19 15:35:06 2006