Re: [picocontainer-dev] Introducing JType

Hi Paul,

I would have though that a branch would suffice as long as it's synced
regularly with the trunk.

To support generic types fully, the main point of integration would be
in the parameter implementations to test assignability of Types rather
than Classes.  For TypeLiteral support we'd just need a few extra
parameterized add/get component/adapter methods on the container API.

I'm available for discussion if anyone's interested in implementing
this, but unfortunately I doubt I'll have time to do it myself.

Cheers,

Mark

2009/2/27 Paul Hammant <[email protected]>:
> Mark,
>
> This is where we need Mercurial/Git as the work to introduce your code would
> most likely happen in parallel with regular releases.
>
> I can only start to think, but you must have an idea already - how this
> would affect our codebase / API
>
> Regards,
>
> - Paul
>
> On Feb 27, 2009, at 2:52 PM, Mark Hobson wrote:
>
>> Hi Paul,
>>
>> Cool :)  No probs with shading it into PicoContainer, I can understand
>> the dependency conundrum.
>>
>> Yes, there's a few TODOs in there which I'd like to properly consider
>> and resolve before releasing an initial version.  There's also a bunch
>> of features I'd like to add in future which I'll start adding issues
>> for.  I use this project internally at work too so I'd like to get an
>> early release out the door and then subsequent ones to fill in any
>> gaps.  I'd prefer to use a <1.0.0 version scheme to indicate that the
>> API is not yet stable with a 1.0.0 final to cast it in stone.
>>
>> I've also got interest in the project from the Hibernate Bean
>> Validator team so I'd have to coordinate releases and features with
>> them too.  But more the merrier, it'd be good to centralise the effort
>> require to work with Types in a common library like this.  And to have
>> PicoContainer on board too :)
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email