[jira] Commented: (LOOM-1) RoadMap for Loom
jira-yCVjj/[email protected]
| Newsgroups | gmane.comp.java.jcontainer.interest |
|---|---|
| Message-ID | <[email protected]> |
The following comment has been added to this issue:
Author: peter royal
Created: Sun, 26 Oct 2003 7:23 PM
Body:
I don't have dates, but from a procession standpoint here's what I plan on working on...
LOOM-7 - Per-Block classloaders
LOOM-8 - Custom Logger factories
LOOM-28 - Deploy via XML descriptor
LOOM-23 - Deploy via "Mapped Archives"
From a feature standpoint that's
* Re-working classloaders for applications
* Allow for more fine-grained and flexible deployment scenarios to ease development and deployment.
The latter is dependent upon some other projects, and will leverage the former (since I want to do hot-reload of blocks)
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=LOOM-1
Here is an overview of the issue:
---------------------------------------------------------------------
Key: LOOM-1
Summary: RoadMap for Loom
Type: New Feature
Status: Assigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: loom
Assignee: Peter Donald
Reporter: Peter Donald
Created: Wed, 18 Jun 2003 11:42 PM
Updated: Sun, 26 Oct 2003 4:34 PM
Description:
We need to decide on and write a roadmap for Loom. This will basically tell us what features are coming and when we can do releases etc. I just got another user request for this (it is one of the most common questions along with "whens the next release?").
To help write this we could write a maven plugin that sucks down issues from jira and maybe some xslt/jelly script could do the grouping and ordering of issues.
---------------------------------------------------------------------
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