[jboss-dev] Public vs. Private API's

[Adrian Brock]

Previous discussion (one of many):
http://lists.jboss.org/pipermail/jboss-development/2007-July/010327.html

or this rant :-)
https://jira.jboss.org/jira/browse/JBAS-1796

On Fri, 2008-12-05 at 10:33 -0500, Andrig Miller wrote:
> I was going to start a thread on one of the design forums but there
> isn't an overall AS design forum, so I'm posting to the dev list
> instead.
> 
> We have been having a discussion within the TDM's about documenting
> the public vs. "private" API's.  The problem we continue to have is
> customers start using API's that are usually, but not always,
> third-party libraries that are used as implementation details for an
> API we do mean for them to use.  Of course, then they start asking for
> support of that usage.
> 
> As this discussion took place internally, we starting batting around
> the idea of separately all the things we would like to be private into
> its own lib directory.  So having one lib directory where have all the
> API's that we intend to have customers/users use, and one where we
> have everything else, so we can clearly communicate what should be
> used and what shouldn't be used directly.
> 
> What do you guys think?  Is this even possible?
> 
> Andy
> 
> -- 
> Andrig (Andy) Miller
> VP of Engineering
> JBoss, a division of Red Hat, Inc.
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx