[cdi-dev] Merging JSR-330 into CDI

[arjan tijms]

On Sun, Mar 20, 2016 at 11:58 AM, Mark Struberg <struberg at yahoo.de> wrote:

> It's fine to have one spec own multiple packages. But one package shall
> not get maintained by multiple specs.
>
> Think about how sealed jars or OSGi should handle this -> technically
> broken and also not allowed by the JCP rules.
>

Okay, and then it just concerns the package itself, right? Not any parent
packages. As javax.security as parent package is shared by both JASPIC and
JACC, while the parent itself is proposed for JSR 375.

Kind regards,
Arjan Tijms



>
>
> Thus before we seriously think about that we need to know what features we
> like to get from JSR-330.
>
> I mean I'm really happy to have all this enthusiasm, but in the end it
> needs to turn into real progress.
>
>
> There are sooo many pull requests waiting to get reviewed first!
>
> * CDI-SE needs a total rework for example
> * the Builders need a review
>
> etc
>
>
> LieGrue,
> strub
>
>
> On Sunday, 20 March 2016, 11:12, arjan tijms <arjan.tijms at gmail.com>
> wrote:
> >
> >
> >On Sun, Mar 20, 2016 at 8:34 AM, Mark Struberg <struberg at yahoo.de> wrote:
> >
> >3.) We cannot simply take the javax.inject package and maintain it in
> CDI. It is forbidden to split a java package into multiple specs.
> >>
> >
> >
> >Do you mean it's forbidden for a spec to own multiple packages, e.g. CDI
> owning both javax.enterprise and javax.inject, or a single package being
> owned by multiple specs, e.g. javax.inject being owned by both AtInject 1.0
> and CDI 2/3.x?
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160320/b7343440/attachment.html