[EMAIL PROTECTED] wrote:
Hi,
there is a problem when working with projects and dependencies inside
eclipse.
following dependency: module A uses module B (A->B), which is configured
in A.pom.xml
1) checkout A into workspace
2) when looking at Project->Properties->Libraries->Maven2Dependencies i
can see included B as a jar-dependency
3) checkout B into workspace, when looking at
Project->Properties->Libraries->Maven2Dependencies i can see included B
as a project and not as jar anymore (makes sense, for B exists now in
workspace).
4) when deleting B from workspace project A gives me an error that it
cannot find B as a project. when looking at
Project->Properties->Libraries->Maven2Dependencies there is B still
included as a project, though it does not exists anymore.
in my perception when deleting a project from workspace m2eclipse should
switch to do a reference to repository and not to the project inside
workspace anylonger. or am i doing something wrong? i would think it as
a bug.
there are two long taking workarounds to get the project to build:
1) opening a new workspace with the project
2) deleting around contents of
$workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/A/
and making clean build. maybe this could be an issue with eclipse and
not the fault of m2eclipse because deletion of projects don't
synchronize with respective outputfiles?
i am using m2eclipse 0.0.10 inside eclipse 3.2.2 Build id: M20070212-1330.
I think there is a Jira issue for this already, although concerning
closing project B which has the same effect. Do a quick search of the
Jira and I'm sure you'll find it.
Adam
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
