The issue here is a planned change to how "publishing" blocks work. Per <https://docs.gradle.org/4.9/userguide/publishing_maven.html#publishing_maven:deferred_configuration>, the right way to prepare for this change is to enable it and check for unexpected changes in what gets published to a local repository. I have done this, and find no unexpected changes. So we are actually ready for Gradle 5.0; the warning is a false positive for us. Leaving the future change enabled means we won't keep seeing this warning. It also means that any further changes to our use of "publishing" will be tested under that future change, which is a good way to avoid surprises later.
40 lines
1.0 KiB
Groovy
40 lines
1.0 KiB
Groovy
rootProject.name = 'com.ibm.wala'
|
|
|
|
include(
|
|
'com.ibm.wala-repository',
|
|
'com.ibm.wala.cast',
|
|
'com.ibm.wala.cast.java',
|
|
'com.ibm.wala.cast.java.ecj',
|
|
'com.ibm.wala.cast.java.test',
|
|
'com.ibm.wala.cast.java.test.data',
|
|
'com.ibm.wala.cast.js',
|
|
'com.ibm.wala.cast.js.html.nu_validator',
|
|
'com.ibm.wala.cast.js.nodejs',
|
|
'com.ibm.wala.cast.js.nodejs.test',
|
|
'com.ibm.wala.cast.js.rhino',
|
|
'com.ibm.wala.cast.js.rhino.test',
|
|
'com.ibm.wala.cast.js.test',
|
|
'com.ibm.wala.cast.js.test.data',
|
|
'com.ibm.wala.cast.test',
|
|
'com.ibm.wala.core',
|
|
'com.ibm.wala.core.testdata',
|
|
'com.ibm.wala.core.tests',
|
|
'com.ibm.wala.dalvik',
|
|
'com.ibm.wala.dalvik.test',
|
|
'com.ibm.wala.ide',
|
|
'com.ibm.wala.ide.jdt',
|
|
'com.ibm.wala.ide.jdt.test',
|
|
'com.ibm.wala.ide.jsdt',
|
|
'com.ibm.wala.ide.jsdt.tests',
|
|
'com.ibm.wala.ide.tests',
|
|
'com.ibm.wala.ide_feature',
|
|
'com.ibm.wala.scandroid',
|
|
'com.ibm.wala.shrike',
|
|
'com.ibm.wala.tests.ide_feature',
|
|
'com.ibm.wala.tests_feature',
|
|
'com.ibm.wala.util',
|
|
'com.ibm.wala_feature',
|
|
)
|
|
|
|
enableFeaturePreview('STABLE_PUBLISHING')
|