You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by is...@cocoondev.org on 2004/07/29 14:40:40 UTC

[issues] Updated: (FOR-233) sub-project seperation

The following issue has been updated:

    Updater: Dave Brondsema (mailto:brondsem@apache.org)
       Date: Thu, 29 Jul 2004 2:40 PM
    Changes:
[Fix For] set to [0.7]

---------------------------------------------------------------------
For a full history of the issue, see:

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

---------------------------------------------------------------------
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