Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Support for Cloning Submodules Over HTTP/HTTPS #76

Closed
loganfranken opened this issue Sep 11, 2012 · 4 comments
Closed

Support for Cloning Submodules Over HTTP/HTTPS #76

loganfranken opened this issue Sep 11, 2012 · 4 comments
Assignees
Milestone

Comments

@loganfranken
Copy link
Contributor

I think we discussed this at the workshop on Friday?

I was getting the Web Blocks build set up on a different computer and git submodule update kept failing with the error fatal: read error: Invalid argument

I eventually discovered it was a firewall issue; I went through and changed the submodule configurations to target https:// instead of git:// and the process went smoothly.

I'm not sure if it would be possible to either create a (1) configuration option or (2) at least some troubleshooting documentation to address this problem?

@ebollens
Copy link
Contributor

Based on the discussion during last Friday's workshop, I agree that we should use https rather than git for this. I will make the necessary changes. Assigning to myself to do.

@ebollens
Copy link
Contributor

For the time being, my change for this will simply modify the .gitmodules file. To use the new paths, you must delete existing packages (rm -rf package/*). A bit more long-term, as part of the custom builders, I'm also going to be retrofitting the whole way this stuff works.

@loganfranken
Copy link
Contributor Author

Blargh, I'm not sure if there's much we can do here, but jQuery complicates matters by having git:// submodules. So, when running a fresh rake, I had to go back in and change those still. This then seemed to cause the build to hiccup while trying to find a compiled version of jquery in a dist directory; I ran grunt manually to get things running again.

@ebollens
Copy link
Contributor

Hmmm, that's a problem, and I don't think we can get around it. jQuery's submodules are its own submodules. Of course, if you're not compiling jQuery as a package, then it isn't a problem. If you are, though, oh well, then you need to have support for the git:// protocol.

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

No branches or pull requests

2 participants