jdaugherty commented on issue #14780:
URL: https://github.com/apache/grails-core/issues/14780#issuecomment-2968993043

   @Hardes1 We've merged 
[PR#1480](https://github.com/apache/grails-core/pull/14805) which should bring 
the number of these deprecations to 43.  The remaining list can be found here: 
https://ge.grails.org/s/zdvivgcln46ss/deprecations 
   
   The remaining issues are: 
   
   1. (gradle 10 deprecation) 1 usage of 
StartParameter.isConfigurationCacheRequested.  This is the asciidoctor plugin & 
the open ticket is 
https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/751 
   2. (gradle 10 deprecation) asset plugin is using project inside of it's 
task.  I've opened https://github.com/wondrify/asset-pipeline/issues/377 to 
address this.
   3. (gradle 9 deprecation) Test.classpath & Test.testClassesDirs in custom 
Test tasks has been deprecated.  This is due to Grails' IntegrationTestPlugin 
defining it's integration tests the legacy way.  Unfortunately, the expected 
replacement is JVM Test Suites, which is still incubating.  We intend to 
address this under https://github.com/apache/grails-core/issues/14738 once the 
JVM test suites are out of incubation.
   4. (gradle 10 deprecation) project is used inside of extractConstraints.  We 
don't have an easy solution for this one at this time, since this task is what 
generates our dependency versions that's stored in our [help 
documentation](https://docs.grails.org/latest/ref/Versions/Grails%20BOM.html).  
I need to open an upstream gradle ticket on this one.  I've opened 
https://github.com/apache/grails-core/issues/14810 to address this. 
   
   Since we have separate tickets for the remaining deprecations and we've 
removed all of the easy ones / dropped it from 
[604](https://ge.grails.org/s/lzwhvyazvn33k/deprecations) to 
[43](https://ge.grails.org/s/zdvivgcln46ss/deprecations?expanded=WyIzIl0), I'm 
going to close this ticket.  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to