How do I get Gradle to comply with the properties standard?

[jcllings (Jim C.)]

Continuing the discussion from Dotted properties in Gradle:

@Peter_Niederwieser

You can use dotted properties, but I don’t recommend it. You will have to use special syntax for accessing them in the build script, and they don’t translate to nested properties. Dotted properties are less needed in Gradle than Ant because:

• A typical Gradle build has far fewer user-defined properties because Gradle has an extensive build (object) model

• User-defined properties can not just be defined on ‘project’ but also on nested objects. (Search for extra properties in the Gradle User Guide.)

That’s not what I call flexible. This is a serious pain in my backside since I have a massive project I’m trying to convert with a large number of properties files. Since the project is massive, I can’t change the names as converting it is likely to take months and Maven has to continue working. A little backward compatibility would be nice. Also, I can’t get ConfigSlurper to work. IDK why but it’s probably something I’ve not yet learned about Imports. I’m new to both Gradle and Groovy and I don’t see this class available anywhere.

[jcllings (Jim C.)]

BUG! exception in phase ‘semantic analysis’ in source unit ‘default_profile_dmmqiztond012huu6njr8dkq1’ String index out of range: 22

The implication here, I think, is that ConfigSlurper is broken and can’t handle property names longer than 22 characters. Is that right?