You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Syte Beimin (JIRA)" <ji...@codehaus.org> on 2007/07/17 17:28:13 UTC
[jira] Created: (MECLIPSE-306) Different approach to Multiple
Module Projects
Different approach to Multiple Module Projects
----------------------------------------------
Key: MECLIPSE-306
URL: http://jira.codehaus.org/browse/MECLIPSE-306
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Components: multiproject
Affects Versions: 2.4
Environment: Fedora Linux
Reporter: Syte Beimin
Priority: Minor
Attachments: maven-eclipse-plugin-2.4-multiModule-patch.txt
At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
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
[jira] Updated: (MECLIPSE-306) Different approach to Multiple
Module Projects
Posted by "Syte Beimin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Syte Beimin updated MECLIPSE-306:
---------------------------------
Attachment: maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt
I accidentally submitted the patch with s System.out.printline still in it. Bad me. Here's the fixed patch.
> Different approach to Multiple Module Projects
> ----------------------------------------------
>
> Key: MECLIPSE-306
> URL: http://jira.codehaus.org/browse/MECLIPSE-306
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Environment: Fedora Linux
> Reporter: Syte Beimin
> Priority: Minor
> Attachments: maven-eclipse-plugin-2.4-multiModule-patch.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt
>
>
> At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
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
[jira] Updated: (MECLIPSE-306) Different approach to Multiple
Module Projects
Posted by "Steve Swinsburg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Swinsburg updated MECLIPSE-306:
-------------------------------------
Attachment: multi-module-single-project.png
> Different approach to Multiple Module Projects
> ----------------------------------------------
>
> Key: MECLIPSE-306
> URL: https://jira.codehaus.org/browse/MECLIPSE-306
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Core : Multi-projects
> Affects Versions: 2.4
> Environment: Fedora Linux
> Reporter: Syte Beimin
> Priority: Minor
> Attachments: maven-eclipse-plugin-2.4-multiModule-patch_fixed_tests.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt, maven-eclipse-plugin-2.4-multiModule-patch.txt, multi-module-single-project.png
>
>
> At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-306) Different approach to Multiple
Module Projects
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113970 ]
Barrie Treloar commented on MECLIPSE-306:
-----------------------------------------
Syte,
This is our How To "Create projects within projects"
* checkout the root of your project from the version control repository
* run mvn eclipse:eclipse from the root of the project directory
* refresh the project in Eclipse
* delete the .project from the project root using the navigator view.
* File → Import... → General → Existing Projects into Workspace, Next
* browse to the project root
* check all projects needed (if this is an empty list, you forgot to delete the .project file)
* finish
There are known issues with subclipses implementation such that following these instructions will cause 100% cpu usage. However Issue 511 has been resolved (http://subclipse.tigris.org/issues/show_bug.cgi?id=511) and this should fix that problem.
We use CVS internally and I haven't played with my SVN sourceforge repositories since the patch for 511 was applied. So YMMV.
> Different approach to Multiple Module Projects
> ----------------------------------------------
>
> Key: MECLIPSE-306
> URL: http://jira.codehaus.org/browse/MECLIPSE-306
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Environment: Fedora Linux
> Reporter: Syte Beimin
> Priority: Minor
> Attachments: maven-eclipse-plugin-2.4-multiModule-patch.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed_tests.txt
>
>
> At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
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
[jira] Updated: (MECLIPSE-306) Different approach to Multiple
Module Projects
Posted by "Syte Beimin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Syte Beimin updated MECLIPSE-306:
---------------------------------
Attachment: maven-eclipse-plugin-2.4-multiModule-patch_fixed_tests.txt
Ok. Now I understand why I had to run the test multiple times for it to work. It's now fixed.
> Different approach to Multiple Module Projects
> ----------------------------------------------
>
> Key: MECLIPSE-306
> URL: http://jira.codehaus.org/browse/MECLIPSE-306
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Environment: Fedora Linux
> Reporter: Syte Beimin
> Priority: Minor
> Attachments: maven-eclipse-plugin-2.4-multiModule-patch.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed_tests.txt
>
>
> At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
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
[jira] Issue Comment Edited: (MECLIPSE-306) Different approach to
Multiple Module Projects
Posted by "Steve Swinsburg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281967#comment-281967 ]
Steve Swinsburg edited comment on MECLIPSE-306 at 10/24/11 5:37 PM:
--------------------------------------------------------------------
We would absolutely love this functionality. We have many multi module projects but don't want them to show up as multiple projects in Eclipse, just as one. I've attached a screenshot of what a typical project looks like. This has 10 modules but it is all grouped in the one project, with only one .project at the base, but including all classpath dependencies from the various modules beneath.
was (Author: steve.swinsburg):
We would absolutely love this functionality. We have many multi module projects but don't want them to show up as multiple projects in Eclipse, just as one. I've attached a screenshot of what a typical project looks like. this has 10 modules but it is all grouped in the one project, with only one .project at the base, but including for all class path dependencies in the various modules beneath.
> Different approach to Multiple Module Projects
> ----------------------------------------------
>
> Key: MECLIPSE-306
> URL: https://jira.codehaus.org/browse/MECLIPSE-306
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Core : Multi-projects
> Affects Versions: 2.4
> Environment: Fedora Linux
> Reporter: Syte Beimin
> Priority: Minor
> Attachments: maven-eclipse-plugin-2.4-multiModule-patch_fixed_tests.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt, maven-eclipse-plugin-2.4-multiModule-patch.txt, multi-module-single-project.png
>
>
> At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-306) Different approach to Multiple
Module Projects
Posted by "Max Bowsher (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102689 ]
Max Bowsher commented on MECLIPSE-306:
--------------------------------------
The big shortcoming of this approach is that Eclipse is unaware of the separation and dependencies between modules, and you can easily create a circular dependency, which will compile fine in this Eclipse configuration, but fail when compiling with Maven.
> Different approach to Multiple Module Projects
> ----------------------------------------------
>
> Key: MECLIPSE-306
> URL: http://jira.codehaus.org/browse/MECLIPSE-306
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Environment: Fedora Linux
> Reporter: Syte Beimin
> Priority: Minor
> Attachments: maven-eclipse-plugin-2.4-multiModule-patch.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed_tests.txt
>
>
> At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
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
[jira] Commented: (MECLIPSE-306) Different approach to Multiple
Module Projects
Posted by "Steve Swinsburg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281967#comment-281967 ]
Steve Swinsburg commented on MECLIPSE-306:
------------------------------------------
We would absolutely love this functionality. We have many multi module projects but don't want them to show up as multiple projects in Eclipse, just as one. I've attached a screenshot of what a typical project looks like. this has 10 modules but it is all grouped in the one project, with only one .project at the base, but including for all class path dependencies in the various modules beneath.
> Different approach to Multiple Module Projects
> ----------------------------------------------
>
> Key: MECLIPSE-306
> URL: https://jira.codehaus.org/browse/MECLIPSE-306
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Core : Multi-projects
> Affects Versions: 2.4
> Environment: Fedora Linux
> Reporter: Syte Beimin
> Priority: Minor
> Attachments: maven-eclipse-plugin-2.4-multiModule-patch_fixed_tests.txt, maven-eclipse-plugin-2.4-multiModule-patch_fixed.txt, maven-eclipse-plugin-2.4-multiModule-patch.txt, multi-module-single-project.png
>
>
> At my company we're used to check out an entire project from subversion. So we'll get all the modules of a project in one eclipse project. The eclipse plugin will create .project and .classpath files in each module directory. For easy checkout and maintainability I've made a patch for the eclipse plugin. With the config '<multiModule>true</multiModule>' the plugin now creates a .project and .classpath file in the root of the multi module project. This classpath has all the source and output directories setup so eclipse put's it's outputs in the same directories (in the modules target directories) where maven places them.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira