[nanocontainer-scm] [jira] Closed: (NANO-86) PicoBuilder (Groovy) needs to move to core/script package

Message:

   The following issue has been closed.

   Resolver: Paul Hammant
       Date: Mon, 3 Jan 2005 5:41 PM

Tis now called NanoContainerBuilder. Aslak fixed the failing testcase months ago.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/NANO-86

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: NANO-86
    Summary: PicoBuilder (Groovy) needs to move to core/script package
       Type: Task

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: NanoContainer
 Components: 
             core
   Fix Fors:
             1.0

   Assignee: 
   Reporter: Paul Hammant

    Created: Wed, 16 Jun 2004 12:35 AM
    Updated: Mon, 3 Jan 2005 5:41 PM

Description:
James wrote the PicoBuilder class in groovy subproject.  It was not well understood by those of us new to Groovy and its builder concept.

Now that I understand it, it's *critical* that this functionality gets consumed into the main NanoContainer project. Specifically org.nanocontainer.script.groovy

It needs a rename. Given the rename will have the word 'Groovy' and 'Builder' in it, it won't exaclty stick out as different to the current GroovyContainerBuilder. 

Perhaps it should be TrueGroovyContainerBuilder (never let me name anything).

Anyway, the BuilderSupport aspect of this is the bit that is magic.  Theat must be upgraded to 

* support different implementations of MutablePicoContainer
* leverage DefaultReflectionComponentAdapter
 - thus take string representations of key/impl that 
   are loadable classes to the groovy script env 
   executing the script.

When consumed, kill James' groovy sub-project please.


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