Different approach to Multiple Module Projects

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 2.4
  • Fix Version/s: None
  • Component/s: Core : Multi-projects
  • Labels:
    None
  • Environment:
    Fedora Linux
  • Testcase included:
    yes
  • Patch Submitted:
    Yes

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Syte Beimin added a comment -

I accidentally submitted the patch with s System.out.printline still in it. Bad me. Here's the fixed patch.

Show
Syte Beimin added a comment - I accidentally submitted the patch with s System.out.printline still in it. Bad me. Here's the fixed patch.
Hide
Permalink
Syte Beimin added a comment -

Ok. Now I understand why I had to run the test multiple times for it to work. It's now fixed.

Show
Syte Beimin added a comment - Ok. Now I understand why I had to run the test multiple times for it to work. It's now fixed.
Hide
Permalink
Max Bowsher added a comment -

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.

Show
Max Bowsher added a comment - 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.
Hide
Permalink
Barrie Treloar added a comment -

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.

Show
Barrie Treloar added a comment - 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.
Hide
Permalink
Steve Swinsburg added a comment - - edited

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.

Show
Steve Swinsburg added a comment - - edited 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.

People

  • Assignee:
    Unassigned
    Reporter:
    Syte Beimin
Vote (1)
Watch (4)

Dates

  • Created:
    Updated: