It's being added to the EAP docs.
There is an internal wiki here that we need to make public, which describes the info:
On Dec 18, 2012, at 4:10 PM, Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
Google didn't show anything for it. I didn't look at the EAP
docs.
On 12/18/12 4:03 PM, Jim Tyrrell wrote:
> Is this in the docs?
>
> Jim
>
> Sent from my iPad
>
> On Dec 18, 2012, at 11:06 AM, Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
>
>> On 12/18/12 10:53 AM, David M. Lloyd wrote:
>>> 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.
>>
>> Beginning at Line 73 at ModuleLoadService[1] you can see the
>> significance of the jboss.api stuff. It just triggers WARN logging.
>>
>> The logging is in a category used for nothing else, so once people feel
>> properly warned they can restrict the category to ERROR.
>>
>> [1]
>>
https://github.com/jbossas/jboss-as/blob/master/server/src/main/java/org/...
>>
>>
>> --
>> Brian Stansberry
>> Principal Software Engineer
>> JBoss by Red Hat
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev