Tooling API should provide information about whether dependencies should be exported

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
Hide
Permalink
Kris De Volder added a comment -

This issue is blocking https://issuetracker.springsource.com/browse/STS-2460

Show
Kris De Volder added a comment - This issue is blocking https://issuetracker.springsource.com/browse/STS-2460
Luke Daley made changes -
Field Original Value New Value
Workflow jira with pivotal tracker [ 15301 ] jira with pivotal tracker (no resolved, only closed) [ 17593 ]
Luke Daley made changes -
Workflow jira with pivotal tracker (no resolved, only closed) [ 17593 ] Copy of jira with pivotal tracker (no closed, only resolved) [ 20235 ]
Unable to get TeamCity builds: No active plugin license is found! Please visit http://stiltsoft.com/teamcity for details

People

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

Dates

  • Created:
    Updated: