[nanocontainer-scm] [jira] Work Logged: (NANO-99) Invent nanocontainer-gems
jira-yCVjj/[email protected] Thu, 28 Oct 2004 20:05:08 -0400 (EDT)
| Newsgroups | gmane.comp.java.nanocontainer.cvs |
|---|---|
| Message-ID | <[email protected]> |
The following work log has been added to this issue:
Logged By: Joerg Schaible
Created: Thu, 28 Oct 2004 8:04 PM
Time Logged: 8 hours
Description:
Added Nick Sieger's Constraint classes (PICO-206)
---------------------------------------------------------------------
View this work log:
http://jira.codehaus.org/browse/NANO-99?page=worklog#action_25873
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/NANO-99
Here is an overview of the issue:
---------------------------------------------------------------------
Key: NANO-99
Summary: Invent nanocontainer-gems
Type: Improvement
Status: In Progress
Priority: Major
Original Estimate: Unknown
Time Spent: 8 hours, 10 minutes
Remaining: 0 minutes
Project: NanoContainer
Components:
core
Fix Fors:
1.0-beta-1
Versions:
1.0
Assignee: Joerg Schaible
Reporter: Joerg Schaible
Created: Thu, 23 Sep 2004 4:33 AM
Updated: Thu, 28 Oct 2004 8:04 PM
Description:
We had several useful extensions for PicoContainer on the list, that I would like to collect in a nanocontainer-gems "component". Such an extension should enhance the core pico functionality, that should not bloat the core itself. I would like to use this project also as new home for some other code already in the CVS. As outline the extensions should not use nanocontainer nor use GUI classes.
Proposed contents of nanocontainer-gems:
- LCListener from Graham Lea from the list
- CollectionParameters and Contraints from Nick Sieger (PICO-206)
- StaticFactoryCA from Pico
- ThreadLocalCA from Nano
- merge proxytoys into gems
- merge consolidated pool into gems
---------------------------------------------------------------------
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