Gradle 4.0.1 Deprecation Warning

Forum on this website is being phased out. New threads or replies cannot be posted. Existing content remains available for now in read only mode. You can contact technical support at support@zeroturnaround.com.

ZeroTurnaround Homepage Forums JRebel Development and Plugins Gradle 4.0.1 Deprecation Warning

This topic contains 2 replies, has 3 voices, and was last updated by  solemamark 4 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #64547

    krisspring
    Member

    Upon upgrading from Gradle 3.5 to Gradle 4.0.1 the following warning now appears in association with the JRebel Gradle plugin.

    
    :generateRebel
    Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0
    

    This warning disappears if I comment out the JRebel plugin.

    I am using the following for the Gradle plugin:

    
    plugins {
        id "org.zeroturnaround.gradle.jrebel" version "1.1.5"
    }
    

    I have JRebel Agent 7.0.12 (201707101444) installed locally.

    • This topic was modified 9 months, 1 week ago by  krisspring.
    #64813

    Tiit Oja
    Rebel Staff

    Hi!

    This deprecation issue has been fixed in the 1.1.6 release of JRebel Gradle plugin.

    #67372

    solemamark
    Member

    Hello

    Deprecation Warning as an argument to Python. Better though to resolve the issue.

    ____________________________________________
    Best Affordable Assignment Help in Australia

Viewing 3 posts - 1 through 3 (of 3 total)

The forum ‘JRebel Development and Plugins’ is closed to new topics and replies.