You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/16 07:07:34 UTC
[jira] Closed: (MAVEN-1314) Introduce Workspace as standard top-level project (like multiproject)
[ http://jira.codehaus.org/browse/MAVEN-1314?page=all ]
Brett Porter closed MAVEN-1314:
-------------------------------
Resolution: Fixed
available in Maven 2.0.
> Introduce Workspace as standard top-level project (like multiproject)
> ---------------------------------------------------------------------
>
> Key: MAVEN-1314
> URL: http://jira.codehaus.org/browse/MAVEN-1314
> Project: maven
> Type: Improvement
> Components: core
> Versions: 1.0-rc3
> Reporter: Eirik Maus
>
> Original Estimate: 10 weeks
> Remaining: 10 weeks
>
> 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)
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org