WALA/com.ibm.wala.util
Ben Liblit b3dbdd3357 Fix a tricky cross-subproject Javadoc dependency
By default, each subproject's Javadoc task depends on the same
subproject's Java compilation task, and uses the same classpath.
Thus, any classes that some Java code uses will also be visible when
building the same Java code's documentation.

In this case, we need to see one of the "com.ibm.wala.core" classes in
order to build the "com.ibm.wala.util" documentation.  However, we
cannot have Java compilation of "com.ibm.wala.util" depend on Java
compilation of "com.ibm.wala.core", because that would create a
dependency cycle.  So we need to add this as a special dependency just
for the "com.ibm.wala.util" documentation task, and add the
appropriate classpath as well.

I'm quite proud of myself for figuring out how to do this properly.
2018-04-18 11:29:24 -05:00
..
.settings Many improvements to Gradle build support, including within Eclipse 2018-04-18 11:29:24 -05:00
META-INF Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
OSGI-INF/l10n Externalize bundle names and vendors 2017-06-07 17:42:11 +02:00
src/com/ibm/wala Escape "<" and ">" in Javadoc when not used as HTML tag syntax 2017-12-19 16:53:52 -06:00
.classpath Many improvements to Gradle build support, including within Eclipse 2018-04-18 11:29:24 -05:00
.gitignore [releng] added preliminary maven tycho build support 2013-04-29 13:13:22 +02:00
.project Many improvements to Gradle build support, including within Eclipse 2018-04-18 11:29:24 -05:00
build.gradle Fix a tricky cross-subproject Javadoc dependency 2018-04-18 11:29:24 -05:00
build.properties Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
mvncentral.xml Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
pom.xml Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00