right
the question here is do we want to use it or not internally (cdi-query was
based on it no? and i think it avoid to repeat too much code, we could
handle the annotation indirection you speak about to be clearer in APIs)
if we dont' want to use it, it can wait CDI-110 otherwise we can push
Romain Manni-Bucau wrote:
right
the question here is do we want to use it or not internally (cdi-query was
based on it no? and i think it avoid to repeat too much code, we could
handle the annotation indirection you speak about to be clearer in APIs)
if we dont' want to use it, it can wait
Inline
On Thu, Sep 13, 2012 at 5:08 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
right
the question here is do we want to use it or not internally (cdi-query was
based on it no? and i think it avoid to repeat too much code, we could
handle the annotation indirection you speak about to
Well that s the current status but the point is do we add feature to (the
last release) of cdi or do we keep a compatibility with old version (i
prefer the 1st one but understand the 2nd)
About javassist David Blevins is working on sthg close for owb which could
go to commons IMO.
Le 14 sept.
