Issue Summary

When a Bamboo plan is published via Java Specs with DockerConfiguration.enabled(false) on a Job, the Docker configuration is silently discarded by the server. Exporting the plan after publish shows no dockerConfiguration on the job at all.

The same configuration set via the Bamboo UI is correctly persisted and exported.

Steps to Reproduce

1. Create a Java Specs plan with a job that has Docker explicitly disabled: 

   new Job("My Job", new BambooKey("JOB1"))
   ...
       .tasks(new CleanWorkingDirectoryTask())
       .cleanWorkingDirectory(true)
       .dockerConfiguration(new DockerConfiguration()
           .enabled(false) 

1. Publish the plan: mvn -Ppublish-specs
2. In the Bamboo UI, go to the plan → Configure Plan → Export Plan
3. Observe that the exported Java code for JOB1 has no .dockerConfiguration(...) call

Expected Results

The export includes .dockerConfiguration(new DockerConfiguration().enabled(false))

Actual Results

No dockerConfiguration appears on the job

Workaround

After the initial Java Specs publish, manually toggle Docker on then off for the affected job via the Bamboo UI (Job Configuration → Docker → enable → save → disable → save). Once the Docker configuration exists in the database via UI interaction, subsequent Java Specs publishes will preserve it.

Note: this will only work if the Java Specs was pushed via Maven. If pushed through Repository Stored Specs (RSS) the plan will be locked out and there will be no way to modify it other than setting the property to true and quickly restore it to false via repository pushes.