Enable VerifyClosure target to run independently of other validations

[NikolaMilosavljevic]

Fixes: #6098
Related to the following Runtime PR that needs this change to work: dotnet/runtime#41698

We need to run VerifyClosure target independently of other validations. This change updates the target condition to allow this.

[ericstj]

Didn't you also mention that you needed to update the task to ensure it creates the directory:

arcade/src/Microsoft.DotNet.Build.Tasks.Packaging/src/VerifyClosure.cs

Lines 388 to 391 in 9915500

	using (var file = File.Create(dependencyGraphFilePath))
	{
	doc.Save(file);
	}

[NikolaMilosavljevic]

Didn't you also mention that you needed to update the task to ensure it creates the directory:

arcade/src/Microsoft.DotNet.Build.Tasks.Packaging/src/VerifyClosure.cs

Lines 388 to 391 in 9915500

	using (var file = File.Create(dependencyGraphFilePath))
	{
	doc.Save(file);
	}

There is a different issue for that fix: #6090

I tried to minimize amount of changes in Arcade, to be able to pick up only SharedFrameworks package for RC2. Directory is being created with a new target you proposed for runtime repo.

[ericstj]

Doesn't this package carry the task and you're already updating it? You can have fewer moving parts and not need a workaround that you have to remove later.

[NikolaMilosavljevic]

Doesn't this package carry the task and you're already updating it? You can have fewer moving parts and not need a workaround that you have to remove later.

No, unfortunately, the task is in a different package: Microsoft.DotNet.Build.Tasks.Packaging

[ericstj]

Hmm, I thought that @jkoritzinsky duplicated it, but maybe that's in a later PR.

[jkoritzinsky]

The duplication is in the new Shared Framework SDK at #5714 that I'm still waiting on reviews on before I can merge in.

[ericstj]

Understood (my review too, apologies). I'll leave it to you @NikolaMilosavljevic to choose what you think is the least risky here.

[NikolaMilosavljevic]

The duplication is in the new Shared Framework SDK at #5714 that I'm still waiting on reviews on before I can merge in.

Jeremy, that PR is for 6.0, right?

[jkoritzinsky]

Yes that PR is for 6.0, but given the size of the change I'm hoping to get it in early in 6.0 so we can make sure that any issues that come up are solved before we start the release process.