You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Rodion Zhitomirsky (JIRA)" <ji...@codehaus.org> on 2005/10/21 20:27:11 UTC
[jira] Created: (MPECLIPSE-105) Ability to add projects of local group to build path
Ability to add projects of local group to build path
----------------------------------------------------
Key: MPECLIPSE-105
URL: http://jira.codehaus.org/browse/MPECLIPSE-105
Project: maven-eclipse-plugin
Type: Improvement
Versions: 1.9
Reporter: Rodion Zhitomirsky
Fix For: 1.9
Attachments: PATCH
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 :).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-105) Ability to add projects of local group to build path
Posted by "Rodion Zhitomirsky (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPECLIPSE-105?page=comments#action_49009 ]
Rodion Zhitomirsky commented on MPECLIPSE-105:
----------------------------------------------
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>
> Ability to add projects of local group to build path
> ----------------------------------------------------
>
> Key: MPECLIPSE-105
> URL: http://jira.codehaus.org/browse/MPECLIPSE-105
> Project: maven-eclipse-plugin
> Type: Improvement
> Versions: 1.9
> Reporter: Rodion Zhitomirsky
> Fix For: 1.9
> Attachments: PATCH
>
>
> 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 :).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-105) Ability to add projects of local group to build path
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPECLIPSE-105?page=comments#action_52067 ]
fabrizio giustina commented on MPECLIPSE-105:
---------------------------------------------
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?
> Ability to add projects of local group to build path
> ----------------------------------------------------
>
> Key: MPECLIPSE-105
> URL: http://jira.codehaus.org/browse/MPECLIPSE-105
> Project: maven-eclipse-plugin
> Type: Improvement
> Versions: 1.9
> Reporter: Rodion Zhitomirsky
> Fix For: 1.9
> Attachments: PATCH
>
>
> 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 :).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPECLIPSE-105) Ability to add projects of local group to build path
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPECLIPSE-105?page=all ]
fabrizio giustina updated MPECLIPSE-105:
----------------------------------------
Fix Version: (was: 1.9)
> Ability to add projects of local group to build path
> ----------------------------------------------------
>
> Key: MPECLIPSE-105
> URL: http://jira.codehaus.org/browse/MPECLIPSE-105
> Project: maven-eclipse-plugin
> Type: Improvement
> Versions: 1.9
> Reporter: Rodion Zhitomirsky
> Attachments: PATCH
>
>
> 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 :).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org