Maven 1.x Eclipse Plugin

Ability to add projects of local group to build path

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.9
  • Fix Version/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

We are using eclipse and maven for our internal project.

Our project is splitted up into multiple semi-independent projects (modules).

So, using repository and maven eclipse plugin we were able to work. However, there is still one important feature of Eclipse that is not available anymore after we swtiched to maven: sources of different projects got decoupled and you can not search, for instance, for references to some class or method.

This could be only fixed by adding referencing projects' source code from other projects.

So, I decided to write a patch for this.

The point is: during generation of .classpath plugin behaves as usually, with an exception of cases, where groupId is the same as maven.eclipse.localgroupid. For this case there will be an additional classpathentry with reference to project.

Hope, my patch explains more then this text (it is a little bit mixed .

  1. File
    PATCH
    21/Oct/05 1:25 PM
    0.5 kB
    Rodion Zhitomirsky

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Rodion Zhitomirsky added a comment -

Here patch in plain text:

— plugin.jelly-1.9 2005-10-21 20:13:02.000000000 +0200
+++ plugin.jelly-with-eclipse-project-feature 2005-10-21 20:06:59.000000000 +0200
@@ -48,6 +48,10 @@
<classpathentry kind="var" path="MAVEN_REPO/$

{relativePath}

" />
</j:otherwise>
</j:choose>
+ <j:set var="localGroupId" value="$

{maven.eclipse.localgroupid}

"/>
+ <j:if test='$

{groupId == localGroupId}

'>
+ <classpathentry combineaccessrules="false" kind="src" path="/$

{artifactId}

"/>
+ </j:if>
</define:tag>
</define:taglib>

Show
Rodion Zhitomirsky added a comment - Here patch in plain text: — plugin.jelly-1.9 2005-10-21 20:13:02.000000000 +0200 +++ plugin.jelly-with-eclipse-project-feature 2005-10-21 20:06:59.000000000 +0200 @@ -48,6 +48,10 @@ <classpathentry kind="var" path="MAVEN_REPO/$ {relativePath} " /> </j:otherwise> </j:choose> + <j:set var="localGroupId" value="$ {maven.eclipse.localgroupid} "/> + <j:if test='$ {groupId == localGroupId} '> + <classpathentry combineaccessrules="false" kind="src" path="/$ {artifactId} "/> + </j:if> </define:tag> </define:taglib>
Hide
Permalink
fabrizio giustina added a comment -

why the eclipse.dependency in project.xml can't be used in this situation?
Just add:
<properties>
<eclipse.dependency>true</eclipse.dependency>
</properties>
to the dependencies you want to link as project references in eclipse and you should achieve the same result.
Is this correct (and so we can close the issue) or I'm missing something?

Show
fabrizio giustina added a comment - why the eclipse.dependency in project.xml can't be used in this situation? Just add: <properties> <eclipse.dependency>true</eclipse.dependency> </properties> to the dependencies you want to link as project references in eclipse and you should achieve the same result. Is this correct (and so we can close the issue) or I'm missing something?

People

  • Assignee:
    Unassigned
    Reporter:
    Rodion Zhitomirsky
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: