Gradle

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
To raise new issues or bugs against Gradle, please use forums.gradle.org.
  • Gradle
  • GRADLE-2114

Tooling API should provide information about whether dependencies should be exported

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Resolution: Unresolved
  • Affects Version/s: 1.0-milestone-7, 1.0-milestone-8
  • Fix Version/s: None

Description

Currently, STS, lacking information from the tooling API whether a dependency is to be exported or not is exporting all dependencies.

Some users however feel strongly that this is a very bad solution. For an example see here:
http://forum.springsource.org/showthread.php?123333-Gradle-import-produces-wrong-classpath-files&p=402394#post402394

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • History
  • Activity
  • TeamCity
  • Commits
  • Source
  • Reviews
Luke Daley made changes - 03/Jan/13 5:09 AM
Field Original Value New Value
Workflow jira with pivotal tracker [ 15301 ] jira with pivotal tracker (no resolved, only closed) [ 17593 ]
Luke Daley made changes - 04/Jan/13 5:10 AM
Workflow jira with pivotal tracker (no resolved, only closed) [ 17593 ] Copy of jira with pivotal tracker (no closed, only resolved) [ 20235 ]

People

  • Assignee:
    Unassigned
    Reporter:
    Kris De Volder
Vote (3)
Watch (3)

Dates

  • Created:
    21/Feb/12 3:00 PM
    Updated:
    22/Feb/12 12:18 PM
  • Atlassian JIRA (v5.0.3#729-sha1:bf569e4)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Gradle. Try JIRA - bug tracking software for your team.