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-2223

1.0-rc1 breaks GWT unit test framework

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Resolution: Fixed
  • Affects Version/s: 1.0-rc-1
  • Fix Version/s: 1.0-rc-2

Description

The RC1 release of gradle, with its change to the test classpath, has broken the GWT unit test framework. Deep inside the GWT framework, it uses the URLClassloader when searching for resources and classes for testing. In the RC1 release notes, it suggests to check the classpath in the manifest of the jar it generates, but this cannot be easily done without rewriting large parts of the GWT test framework. I imaging this change could cause various problems in other frameworks as well, as it is a bit non-standard.

Perhaps an alternative to the current jar manifest approach would be to copy the jars to a directory, and then use a wildcard for the classpath (e.g. java -cp mydir/*)? This would only work with JDK 1.6 however. How does Ant handle this problem?

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    stack.txt
    11/Apr/12 5:38 PM
    4 kB
    Bryan

Activity

  • All
  • Comments
  • History
  • Activity
  • TeamCity
  • Commits
  • Source
  • Reviews

People

  • Assignee:
    Unassigned
    Reporter:
    Bryan
Vote (0)
Watch (0)

Dates

  • Created:
    11/Apr/12 5:20 PM
    Updated:
    04/Jan/13 5:10 AM
    Resolved:
    18/Apr/12 3:19 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.