You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Knowing that modularization is a rather big thing, I wanted to suggest it for the future roadmap.
Background: I am using JDOM in an android project and tried to exclude the jdom core as stated in the wiki. Since I referenced the maven artifact as a dependency and thus don't have a libs folder in my repo where the jdom jar resides in, I can't just remove the jdom core jar because gradle handles the download of the jar.
I can tell gradle to exclude certain parts of a jar (transitive dependencies), but only, if that transitive dependency is published as a seperate jar on maven central.
TL;DR I would like to exclude the jdom core from my build but am unable to do so. If jdom core was published as a separate artifact to maven central with jdom declaring a dependency on it, exclusion would be much easier.
The text was updated successfully, but these errors were encountered:
Knowing that modularization is a rather big thing, I wanted to suggest it for the future roadmap.
Background: I am using JDOM in an android project and tried to exclude the jdom core as stated in the wiki. Since I referenced the maven artifact as a dependency and thus don't have a libs folder in my repo where the jdom jar resides in, I can't just remove the jdom core jar because gradle handles the download of the jar.
I can tell gradle to exclude certain parts of a jar (transitive dependencies), but only, if that transitive dependency is published as a seperate jar on maven central.
TL;DR I would like to exclude the jdom core from my build but am unable to do so. If jdom core was published as a separate artifact to maven central with jdom declaring a dependency on it, exclusion would be much easier.
The text was updated successfully, but these errors were encountered: