Paket should import build targets from packages in dependency groups

[sergey-tihon]

Not sure it is directly related to #1663
But after paket.exe update with version 2.64.2, paket removed by build targets from project file

[inosik]

The problem is the group name "Build". Other names seem to work fine.

Seems to be the same kind of problem as we had with "Lib"-named packages.

[sergey-tihon]

@inosik How group name affects Paket behavior?

[inosik]

It expects .targets and .props files to be directly in packages/Foo/build/ or in a framework specific sub-directory.

Now, if a group is named "Build", you get a path like packages/build/Foo/build/Foo.targets. I assume Paket checks only if Foo.targets is in packages/build/ or in packages/build/{framework}/, and if it isn't, it considers it as ignorable.

I tried installing the package from your screenshot and Paket installed it correctly when the group wasn't named "Build". With "Build", it didn't import the .targets file.

[sergey-tihon]

Just wonder how it worked before )

[forki]

@inosik so it's a string trimming issue, right?

[inosik]

I think so. We had something similar with packages which ended with "Lib", but I can't find the issue right now.

[forki]

@sergey-tihon if we have a repro I will try to fix it

[sergey-tihon]

@forki This PR is repro

[sergey-tihon]

It works!
Thanks again @forki !