[resteasy-dev] RESTEASY-1512 and jboss-modules

[Tomaž Cerar]

Marking module as private won't fail any tests.

All this does is logs a warning when deployment directly uses it.
that is about the extend of this "private" module to runtime.

On Sat, Oct 1, 2016 at 4:33 PM, Ron Sigal <rsigal at redhat.com> wrote:

> I've been working on bringing the content of jboss-modules into line
> with wildfly 10.1.0.Final, and I've run into a problem. The yaml
> integration tests are failing, and it's because yaml's module.xml has
>
> >     <properties>
> >         <property name="jboss.api" value="private"/>
> >     </properties>
>
> I've found some discussion
> (http://wildfly-development.1055759.n5.nabble.com/what-is-
> jboss-api-private-exactly-td5711072.html)
> where David Lloyd says
>
> > On 12/18/2012 10:37 AM, Bill Burke wrote:
> > > I've been doing multiple searches trying to figure out exactly what
> > > jboss.api=private in modules.xml means.
> > >
> > > Does it exclude/filter all classes under org.jboss.* from being
> > imported
> > > to your deployment?
> >
> > No, it's purely for EAP, so customers know that they're on their own if
> > they import private or unsupported modules into their deployments.
>
>   1, I'm not sure how to handle this. Maybe the right thing to do is
> change the yaml integration tests to import resteasy-yaml-provider.
>
>   2. Oddly, there are several other modules, e.g., resteasy-cdi,
> resteasy-jsapi, ..., that are also marked private and they aren't
> causing any failures.
>
> Thoughts?
>
> -Ron
>
>
> --
> My company's smarter than your company (unless you work for Red Hat)
>
> _______________________________________________
> resteasy-dev mailing list
> resteasy-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/resteasy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/resteasy-dev/attachments/20161003/b7103672/attachment.html