maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Closed] (MECLIPSE-306) Different approach to Multiple Module Projects
Date Fri, 25 Dec 2015 11:49:51 GMT


Robert Scholte closed MECLIPSE-306.
    Resolution: Won't Fix
      Assignee: Robert Scholte

The Apache Maven team has decided to retire the maven-eclipse-plugin, so this issue won't
be fixed. 

> Different approach to Multiple Module Projects
> ----------------------------------------------
>                 Key: MECLIPSE-306
>                 URL:
>             Project: Maven Eclipse Plugin (RETIRED)
>          Issue Type: New Feature
>          Components: Core : Multi-projects
>    Affects Versions: 2.4
>         Environment: Fedora Linux
>            Reporter: Syte Beimin
>            Assignee: Robert Scholte
>            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, 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 was sent by Atlassian JIRA

View raw message