"Refresh Gradle Project" changes order of buildCommands in project file

[TTTThomas]

Before the call of "refresh gradle project", the commands in the file .project are ordered in the following way:

		<buildCommand>
			<name>org.eclipse.wst.jsdt.core.javascriptValidator</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.jdt.core.javabuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.wst.common.project.facet.core.builder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.jboss.tools.jst.web.kb.kbbuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.jboss.tools.cdi.core.cdibuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.wst.validation.validationbuilder</name>
			<arguments>
			</arguments>
		</buildCommand>

Afterwards the gradle builder is added but the order of the commands changed:

<buildCommand>
			<name>org.eclipse.jdt.core.javabuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.wst.common.project.facet.core.builder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.wst.validation.validationbuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.buildship.core.gradleprojectbuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.wst.jsdt.core.javascriptValidator</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.jboss.tools.jst.web.kb.kbbuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.jboss.tools.cdi.core.cdibuilder</name>
			<arguments>
			</arguments>
		</buildCommand>

This leads to the following eclipse error:
CDI Core Validator cannot run on project because Validation Builder precedes CDI (Contexts and Dependency Injection) Builder.

[donat]

Hi! Sorry for the late reply. Where do those project natures come from? I've run a quick test and if I declare the build commands in the build script, then the ordering stays stable.

apply plugin: 'eclipse'

eclipse {
    project {
        buildCommand 'org.jboss.tools.cdi.core.cdibuilder'
        buildCommand 'org.eclipse.wst.validation.validationbuilder'
    }
}

[mauromol]

I'm not the reporter, but I suppose these are "custom" build commands which Buildship now (correctly) keeps as per #392. Probably, if in this case ordering is important, the only way to go is to declare them in the build script...

[TTTThomas]

eclipse {
    project {
			buildCommands.clear();
			buildCommand 'org.eclipse.jdt.core.javabuilder'
			buildCommand 'org.eclipse.wst.common.project.facet.core.builder'
                        ........
   }
}

Works for me.

Thanks.

[donat]

@mauromol That is correct.
@TTTThomas I'm glad you've found the solution.