[jira] Commented: (MECLIPSE-306) Different approach to Multiple Module Projects

["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