[jboss-as7-dev] Javadoc - private modules vs. non-private deps - what to include (again)?
David M. Lloyd
david.lloyd at redhat.com
Thu Oct 11 20:32:02 EDT 2012
On 10/11/2012 07:25 PM, Ondrej Zizka wrote:
> Hi all,
>
> the AS public API javadoc is generated by scripts which follow the logic
> discussed earlier. In short, these are the rules for inclusion:
>
> * All modules NOT marked with <property name="jboss.api" value="private"/>
> * Their <dependencies> which are NOT marked with <property
> name="jboss.api" value="private"/>
> * "unsupported" is treated the same as "private"
> * All this is merged using union. I.e. if something is marked as
> private, but exposed as a non-private dependency of a non-private
> module, it's included.
>
> Is the last point ok? It leads to various jars included which would make
> more sense if not included.
> See https://issues.jboss.org/browse/JBPAPP-10099
> Perhaps a module marked private should override exposed deps?
Dependencies are non-transitive; i.e. they're not visible even if
they're included by a public module, so there's no reason to pull them
in. So only the first and third bullet really make any sense.
--
- DML
More information about the jboss-as7-dev
mailing list