-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Issues running Rome with --no-skip-current #237
Comments
This is equivalent to Carthage's --no-skip-current. Try removing the repositoryMap. You can check in the integration tests of the project how this is set up for Alamofire I think |
Ah thanks for the tip. Looks like the integration tests are using this Romefile:
with the following Rome command:
I've revised my Romefile to this:
Here's the commands I'm running:
One thing to note: My project has a regular |
No, that shouldn't matter. But it does need a Try |
It does contain a
Running
|
Does If you try with Alamofire does it work? There shouldn't be any difference. Also, i see that the currentMap contains But from your log, not ever protobuff is being uploaded. What version of carthage are you using? |
Ah that was the issue. Thanks for helping me debug! I'll take a look at the README to see if there's details that can be added. |
This is in response to this recently closed issue tmspzz#237
This is in response to this recently closed issue #237
Bug Report
I'm not sure if my project is set up correctly or not, but I can't seem to get Rome to work with the
--no-skip-current
option.Steps which explain the enhancement or reproduce the bug
Here's my setup:
GitHub repo:
Romefile:
Rome command:
Current behavior
Rome does not upload for the FaireProtobuf framework.
Suggested behavior
I'd like Rome to cache all Carthage dependencies, including the FaireProtobuf framework when the
--no-skip-current
is specified.Why would the enhancement be useful to most users
This is useful for framework projects that need to be pre-cached.
Rome version:
OS and version:
macOS Big Sur 11.1 (20C69)
The text was updated successfully, but these errors were encountered: