forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] New comment: (FOR-233) sub-project seperation
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Dave Brondsema
    Created: Thu, 29 Jul 2004 2:44 PM
       Body:
We currently have these subprojects:

forrestbot
forrestbot webapp
forrestdoc
forrestlogos
forrestbar
forrestplugin (eclipse)
---------------------------------------------------------------------
View the issue:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-233


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-233
    Summary: sub-project seperation
       Type: Task

     Status: Unassigned
   Priority: Major

    Project: Forrest
  Component: None
    Fix For: 0.7

   Assignee: 
   Reporter: Dave Brondsema

    Created: Thu, 29 Jul 2004 2:40 PM
    Updated: Thu, 29 Jul 2004 2:40 PM

Description:
Subprojects that are not directly dependant on Forrest should be seperate modules (directories
in SVN).  This will allow SoC (seperation of concerns), separate releases, and per-subproject
access control in SVN.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org/jira//Administrators.jspa

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


Mime
View raw message