[
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
