[news.eclipse.technology.m2e] Re: Eclipse errors after SCM update

[Yves Schumann <starwarsfan@xxxxxxxxxx>]

Hi there

Igor Fedorenko schrieb:
> I don't have much experience with Eclipse ClearCase plugin (and the
> little experience I had was not a good one), so I can only give you some
> hints how you can start troubleshooting this problem but to solution. I
> assume you're talking about Maven dependency resolution problems. If you
> are talking about Java compilation errors, then most likely these
> suggestions do not apply.

So I've installed Eclipse 3.5RC3 (Galileo) and m2e 0.9.8 and till now
nothing changes in the behaviour. :-(

At first I can tell that the maven importer sometimes shut down Eclipse
like before. No change here.


> First, make sure that Eclipse workspace is in sync with underlying
> filesystem (select all projects, right click, Refresh).

Done with no change on behaviour.


> If Refresh does not help, try forcing Maven dependency re-resolution
> (Project->Update All Maven Dependencies). Internally, m2e uses
> filesystem timestamps to detect pom.xml file changes and it may get
> confused if ClearCase does anything funny.

Done too, no change.


> You can also try full/clean workspace build (Project->Clean...->Clean
> all projects).

So, what should I say... No change too...


> If any of these steps makes the errors go away, we can dig deeper to see
> how to actually fix the problem.

Currently I'm very frustrated because it is very time consuming and I
have no idea where to search the problem. What should I try?

Here's just an example:

One of the projects (say A) has a dependency to another project (say B),
defined on pom.xml. Project B is listet on the Maven Dependencies of A
as an open folder. But on A I got the error "The import ... cannot be
resolved" and a part of the imported package is underlayed with a red
line. Note, _not_ the whole package of the imported class! But it
confuses me, that the import is reachable with Ctrl+click on the
importet class.

Aditionally: Why is the file <project>/.settings/org.maven.ide.eclipse
modified during project import? This file is under version control but
the importer replaces them with a new version. On ClearCase all
versioned files are write protected and the ClearCase plugin checks them
out (make them writable) if neccessary. So if I'm disconnected from
ClearCase and import a maven project, this will produce a question like
".settings/org.maven.ide.eclipse is write protected. Make it writable?".
If answering this with "Yes", I got hijacked files on ClearCase.

If I create two Maven projects with some lines of code and the
dependencies as written on the last paragraph, everything is nice. So I
have absolutely no idea what's wrong on the "real" projects. The build
including the deploy is working nice and without any problems from the
commandline and out of Eclipse too. But Eclipse itself "knows" the right
files out of the referenced projects (Ctrl+click works) but underlays
them with a red line as mentioned above.


> This is likely https://bugs.eclipse.org/bugs/show_bug.cgi?id=249930.
> It is not m2e specific. You can either build patched JDT core or move
> to Eclipse 3.5.

As written above, same behaviour with Eclipse 3.5RC3 and m2e 0.9.8.

So what should I do now?


-- 
MfG
Yves
[eisfair-team]

Arbeiten am Computer ist wie U-Boot fahren. Fängt man an die Fenster zu
öffnen, dann gehen die Probleme los.