# Gradle equivalent of Eclipse Java Build Path "exported entries"

**URL:** <https://discuss.gradle.org/t/gradle-equivalent-of-eclipse-java-build-path-exported-entries/2720>\
**Category:** Old Forum Archive\
**Created:** [September 23, 2013, 4:36pm UTC](https://discuss.gradle.org/t/gradle-equivalent-of-eclipse-java-build-path-exported-entries/2720 "2013-09-23T16:36:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastien\_Tardif](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/sebastien_tardif/32/238_2.png) [@Sebastien\_Tardif](https://discuss.gradle.org/u/Sebastien_Tardif)\
**Post date:** [September 23, 2013, 4:36pm UTC](https://discuss.gradle.org/t/gradle-equivalent-of-eclipse-java-build-path-exported-entries/2720/1 "2013-09-23T16:36:00Z")

</div>

How do we handle in Gradle the Eclipse concept of Java Build Path “exported entries” ?

When I have a Java project that only produce a jar, we don’t have in Gradle the concept of War called compileOnly, but in Eclipse we can at least tell the dependents to not include some of the library/jar file.

My exact problem is that I have project A using some EJB container API, then project B depends on project A, then project C which is a War project depends on project B and so also A. I don’t want to have the related Jar files of the EJB container API added to the War of project C that are coming from project A. Since I may have like 10 different War project that all end-up to someone import project A directly or indirectly, it makes more sense for me to specify the exclusion in project A. I believe in Eclipse I can do that easily by using the “exported entries” feature.