Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nuget (3.5.0) push with PublishUrl errors out with ambiguous argument #1415

Closed
seanamosw opened this issue Nov 3, 2016 · 6 comments
Closed

Comments

@seanamosw
Copy link
Contributor

Description

When publishing a package with the Nuget helper and using Nuget 3.5.0, the publish fails with a Ambiguous option 's'. Possible values: Source SymbolSource SymbolApiKey. error.

Repro steps

  1. Ensure you are using Nuget 3.5.0.
  2. NuGet (fun p ->
        { p with
            ....
            Publish = true
            PublishUrl = url
        })
        ...

Expected behavior

The Nuget CLI should not throw a parameter error.

Actual behavior

A parameter error is thrown by the Nuget CLI:
Ambiguous option 's'. Possible values: Source SymbolSource SymbolApiKey.

Known workarounds

Manually push the package using the -Source parameter instead of -s.

@seanamosw seanamosw changed the title Nuget (3.5.0) push with source errors out with ambiguous argument Nuget (3.5.0) push with PublishUrl errors out with ambiguous argument Nov 3, 2016
@forki
Copy link
Member

forki commented Nov 4, 2016

could you please try to come up with a fix?
@emgarten @yishaigalatzer did nuget 3.5 have breaking changes?

@yishaigalatzer
Copy link

Cool catch. Just use the full name of the switch. The commandline can use a partial if there are no collisions. I believe we added a new switch which will break this shorthand.

Thinking out loud: we should keep it as is and perhaps call it out?

Thoughts?

@forki
Copy link
Member

forki commented Nov 4, 2016

tbh we are probably much faster to fix it in FAKE. but will -Source break older nuget.exes?

@yishaigalatzer
Copy link

It shouldn't because they always had it.

For example:
-s
-so
-so

Should all still work

@forki forki closed this as completed in aad67ca Nov 4, 2016
@forki
Copy link
Member

forki commented Nov 4, 2016

thanks.

just saw we already use -source in different command. so I think aad67ca is fine.

@yishaigalatzer
Copy link

That was fast!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants