Well we'll always have the cutoff problem once we start leaking classes we
don't really have any control over. Given a fairly marginal use case with
probably just 1 user, I think my point is valid.
These classes are in the javax.enterprise package space. That's "ee" to me.
Even the modern ee stuff
I don't think there is anything 'ee' about @Typed annotation. I would
keep it and would make it the only cdi.jar class exported by the core.
--
Regards,
Igor
On 2/13/2014, 12:08, Kristian Rosenvold wrote:
Wouldn't it make more sense to roll our own version of "typed" then?
Leaking "ee" stuff fr
On 13 Feb 2014, at 17:08, Kristian Rosenvold
wrote:
> Wouldn't it make more sense to roll our own version of "typed" then?
Why roll our own when there’s a standard annotation available? I can always
add our own version of @Typed under a different package, but that doesn’t seem
to encourage re
Wouldn't it make more sense to roll our own version of "typed" then?
Leaking "ee" stuff from core does not seem like nice thing.
Kristian (Who will only touch "ee" stuff with a pitchfork)
2014-02-13 18:01 GMT+01:00 Igor Fedorenko :
> Please keep @Typed annotation available outside of core.
>
>
Please keep @Typed annotation available outside of core.
I use @Typed annotation in one of my (private) core extensions where I
need a class to implement an interface but not make that interface
visible for injection in other components.
--
Regards,
Igor
On 2/13/2014, 9:43, Jason van Zyl wrote:
On 13 Feb 2014, at 14:43, Jason van Zyl wrote:
> On Feb 13, 2014, at 8:44 AM, Stuart McCulloch wrote:
>
>> On 13 Feb 2014, at 13:30, Jason van Zyl wrote:
>>
>>> I would consider something like SFL4J as something which is now part of our
>>> API think it's fine to expose something like that. I
On Feb 13, 2014, at 8:44 AM, Stuart McCulloch wrote:
> On 13 Feb 2014, at 13:30, Jason van Zyl wrote:
>
>> I would consider something like SFL4J as something which is now part of our
>> API think it's fine to expose something like that. I'm not sure the same
>> holds true for CDI. Wouldn't i
On 13 Feb 2014, at 13:30, Jason van Zyl wrote:
> I would consider something like SFL4J as something which is now part of our
> API think it's fine to expose something like that. I'm not sure the same
> holds true for CDI. Wouldn't it be better just to completely hide it?
As mentioned in http:/
I would consider something like SFL4J as something which is now part of our API
think it's fine to expose something like that. I'm not sure the same holds true
for CDI. Wouldn't it be better just to completely hide it?
On Feb 13, 2014, at 5:56 AM, Stuart McCulloch wrote:
> On 13 Feb 2014, at 0
Much as I hate leaking stuff like this, it would appear to me that
extending the import (alternative 2) is the correct thing to do.
Of course, ifimports.put( "javax.enterprise.inject.Typed", coreRealm
); doesn't break any tests we could always start with that. I'll give it a
shot tonight.
Kri
On 13 Feb 2014, at 07:28, Kristian Rosenvold
wrote:
> Stuart,
>
> We're seeing java.lang.LinkageError: loader constraint violation: loader
> (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) previously
> initiated loading for a different type with name
> "javax/enterprise/util/Type
It still breaks with 3.1.1; bugger :)
2014-02-13 10:23 GMT+01:00 Tamás Cservenák :
> Maybe related to https://jira.codehaus.org/browse/MNG-5513 ?
>
> As cdi-api is now also in core?
>
>
> Thanks,
> ~t~
>
>
> On Thu, Feb 13, 2014 at 8:28 AM, Kristian Rosenvold <
> kristian.rosenv...@gmail.com> wr
Maybe related to https://jira.codehaus.org/browse/MNG-5513 ?
As cdi-api is now also in core?
Thanks,
~t~
On Thu, Feb 13, 2014 at 8:28 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:
> Stuart,
>
> We're seeing java.lang.LinkageError: loader constraint violation: loader
> (instanc
Stuart,
We're seeing java.lang.LinkageError: loader constraint violation: loader
(instance of org/codehaus/plexus/classworlds/realm/ClassRealm) previously
initiated loading for a different type with name
"javax/enterprise/util/TypeLiteral" using the maven-jetty-plugin on 3.1. I
can't really see th
14 matches
Mail list logo
