This content has been marked as final.
Show 5 replies
-
1. Re: Java Doc Missing
timfox Feb 26, 2010 1:20 PM (in response to jtyrrell)That's deliberate.
We only javadoc classes that are part of the public API.
-
2. Re: Java Doc Missing
jtyrrell Feb 26, 2010 2:24 PM (in response to timfox)So i'll bite, then why is it still in the shipping documents in the bundle, why do the examples reference java code that is in the "private" API and not easily documented. I admit I have not been around the discussion, so I am not sure if this makes sense or not, but I do not understand the reasons for a public vs private. -
3. Re: Java Doc Missing
timfox Feb 26, 2010 2:27 PM (in response to jtyrrell)This is discussed here: https://jira.jboss.org/jira/browse/TAG-29
We may consider moving out the embedded stuff into a public API sometime in the future.
-
4. Re: Java Doc Missing
jtyrrell Feb 26, 2010 2:29 PM (in response to timfox)I guess my comment will be then as this gets productized, we need to clearly mark what parts of the API are/are not going to be supported as part of the EAP subscription I guess. Thanks for the insight. -
5. Re: Java Doc Missing
timfox Feb 26, 2010 2:32 PM (in response to jtyrrell)jtyrrell wrote:
Right, that's the idea behind the public/private split.
Anything in the public api is supportable and we need to make compatibility guarantees for in the EAP.
Anything else we can change when we want.