forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-233) sub-project seperation
Date Mon, 18 Oct 2004 15:50:38 GMT
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Mon, 18 Oct 2004 10:50 AM
       Body:
We now also have

eclipsePlugin

and are likely to have plugins too soon
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-233?page=comments#action_11656

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-233

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

     Status: Unassigned
   Priority: Major

    Project: Forrest
   Fix Fors:
             0.7

   Assignee: 
   Reporter: Dave Brondsema

    Created: Thu, 29 Jul 2004 2:40 PM
    Updated: Mon, 18 Oct 2004 10:50 AM

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