Adding package when sources are splitted (command line or UI) #137
Labels
Comments
SuperRoflCopter
changed the title
|
Do you have a concrete dependencies file concrete paket add command for
me to repro?
Am 10.03.2017 11:08 vorm. schrieb "ThomasPomme" <[email protected]>:
… I've noticed an issue when adding package to a project via "paket add"
command line or "Add Package" interface.
When your dependencies file look like this :
source https://www.nuget.org/api/v3/
nuget nuget1
nuget nuget2
source https://InternalRepository
nuget nuget3
If you try adding a package from the "InternalRepository" you'll get the
following error message :
[image: image]
<https://cloud.githubusercontent.com/assets/1961983/23791029/c6f70af4-0581-11e7-970b-a2eecb45aa7c.png>
A possible fix would be to be able to target a specific source, or for the
paket add command to add the package at the right place in the dependencies
file depending on the source of the package.
..or not splitting the packages by sources.. but it is faster that way. :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#137>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADgNNkmMQClPX3_W0pwQcGhNB-bRUpsks5rkSEtgaJpZM4MZMtP>
.
|
|
You can use this case for example (random public feed) : Try add this package from https://sitecore.myget.org/F/sc-packages/ repo : (paket add nuget Data-Exchange-Framework-Remote-SDK) And I get the following error : |
|
Thanks for the quick fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've noticed an issue when adding package to a project via "paket add" command line or "Add Package" interface.
When your dependencies file look like this :
If you try adding a package from the "InternalRepository" you'll get the following error message :
A possible fix would be to be able to target a specific source, or for the paket add command to add the package at the right place in the dependencies file depending on the source of the package.
..or not splitting the packages by sources.. but it is faster that way. :)
The text was updated successfully, but these errors were encountered: