[jira] Commented: (MAVEN-1314) Introduce Workspace as standard top-level project (like multiproject)

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: Jason van Zyl
    Created: Mon, 7 Jun 2004 2:40 PM
       Body:
All these issues are dealt with in m2 which indeed incorporates reactor behaviour inside the core as dealing with multiple projects effectively will be one of m2's strong points.
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1314?page=comments#action_20452

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1314

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1314
    Summary: Introduce Workspace as standard top-level project (like multiproject)
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: 10 weeks
 Time Spent: Unknown
  Remaining: 10 weeks

    Project: maven
 Components: 
             core
   Versions:
             1.0-rc3

   Assignee: 
   Reporter: Eirik Maus

    Created: Mon, 7 Jun 2004 2:05 PM
    Updated: Mon, 7 Jun 2004 2:40 PM

Description:
Maven should incorporate the concept of "workspace", effectively making multiproject mode the default mode. 

Virtually all real-life projects consist of several sub-projects, or will do after a while. 

Mature IDEs (IntelliJ 4.0, MS Visual studio, JBuilder ...) all require projects to be part of a workspace that contain the shared properties of those projects. Effectively, this turns single-module-projects into a special case of "multiprojects". This eases the reorganizing of the project as you (after a few months of work) discover that you need to split the project into several items, add a separate modules etc. All projects are "multiproject"-projects, so just add a sub-project to you workspace and move the files.  

Maven, being the definitive tool for large and complicated project organization and handling, should definitely follow this path. I suggest

a)
Make "multiproject" default mode

b) 
Introduce a "workspace.xml" file describing the common properties of the subprojects, and make all "project-xml" files inherit from it (even if not stated explicitly). 

c)
As a decent project/artifact type and template system is realized (see MAVEN-1016 and others), make them require that a workspace.xml is present in a parent directory. (or do this during building)

d)
Similarly, introduce something similar to maven.xml for workspaces, 

e)
.. and make maven.xml for each of the projects inherit preGoal and prostGoals (unless explicitly cancelled using some goal-trigger-cancelling mechanism yet to be invented)




---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org