add BuildServicesResolver.setBuildServices()

[Ladicek]

No description provided.

[manovotn]

@Ladicek should we also include the policy to only be able to set the impl only once?
We do the same thing for CDI providers.

[Ladicek]

@Ladicek should we also include the policy to only be able to set the impl only once? We do the same thing for CDI providers.

I considered that, but contrary to your statement (and contrary to the javadoc you link to), I didn't find CDI.setCDIProvider to check this.

[manovotn]

@Ladicek should we also include the policy to only be able to set the impl only once? We do the same thing for CDI providers.

I considered that, but contrary to your statement (and contrary to the javadoc you link to), I didn't find CDI.setCDIProvider to check this.

Indeed, you're correct. I only read the javadoc and assumed that.
It seems like a bug TBF

[Emily-Jiang]

Suggested change

	throw new IllegalStateException("Unable to locate BuildServices implementation");
	throw new IllegalStateException("Unable to locate a BuildServices implementation");

[manovotn]

This change was discussed during the meeting and agreed on it as a way forward.
We want to keep it as similar to how setting CDI provider works as possible (including the current CL used for loading the services).

@arjantijms do you need a service release with this fix or are you going to use the workaround mentioned in the issue?

[arjantijms]

do you need a service release with this fix or are you going to use the workaround mentioned in the issue?

I will use the workaround mentioned in the issue for now, so a service release is not strictly needed from my part.