Remove xliff-tasks source link mapping

[ViktorHofer]

Now that the xliff-tasks repo got merged into arcade and the xlifftasks.proj orchestrator project got deleted, we should delete the source-mapping for it to initialize the VMR and delete the sources from the VMR repo.

From what others mentioned, the source-mapping needs to stay until all nodes in the repo graph updated their Version.Details.xml entries and remove the xliff-tasks repo mention: https://github.com/search?q=repo%3Adotnet%2Fdotnet+xliff-tasks+path%3AVersion.Details.xml&type=code

[marcpopMSFT]

@premun I see merged PRs linked. Can this be closed?

[ViktorHofer]

No, this issue still tracks the removal of the source link mapping.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ViktorHofer]

The source-mappings.json file still lists xliff-tasks.

[ViktorHofer]

@premun there are two repos left that reference the xliff-tasks repo:

• command-line-api (older version, will soon get updated in the VMR -> not an issue)
• aspire: https://github.com/dotnet/dotnet/blob/02249bfe7b4ce17af68f99cf567cd598e8294c37/src/aspire/eng/Version.Details.xml#L176-L179

The aspire case is tricky. Would removing the entry in dotnet/dotnet allow us to remove the xliff-tasks entry in source-mapping.json and the folder in the VMR?

[premun]

We cannot remove xliff-tasks because the dependency tree of SDK commits would still contain it and the tooling would not know what to do about it and fail. So no matter what you do in the VMR, the source-mappings won't match the real source code tree from outside of the VMR. We'd have to remove aspire from sdk's V.D.xml and remove xliff-tasks from the command-line-api V.D.xml.

But, is there any harm in having those in the file? We can remove these next week when we switch to the flat flow?

[ViktorHofer]

The command-line-api one already got removed, it just needs to flow. That will happen this week.

But, is there any harm in having those in the file? We can remove these next week when we switch to the flat flow?

Last time when we talked about xliff-tasks in the sync, you mentioned that it would help removing it before we switch to flat flow. If that isn't the case anymore then I won't look further into this.

[akoeplinger]

just so I understand: we can still remove xliff-tasks from the VMR next week?