In workspace environment, SetUpTestableTomcat will fail if initBundle has not been called

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.3.1 CE GA2, 7.3.10 DXP GA1, Master
• Component/s: Dev Tools, Dev Tools > Gradle Plugins
• Labels:
  • 7.3-devtools
• Epic Link: Liferay Workspace Support for New Test Integration Bridge

If you have not created the correct tomcat bundle layout (like a workspace directory where initBundle has not been called), when you call `setUpTestableTomcat` it will fail like the following:

Caused by: java.lang.NullPointerException
        at com.liferay.gradle.plugins.test.integration.tasks.SetUpTestableTomcatTask._setUpFilePermissions(SetUpTestableTomcatTask.java:286)
        at com.liferay.gradle.plugins.test.integration.tasks.SetUpTestableTomcatTask.setUpTestableTomcat(SetUpTestableTomcatTask.java:218)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)

This leaves the developer with serious head-scratch as to why this would ever be null and what to do next.