-
Notifications
You must be signed in to change notification settings - Fork 187
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
Issue with export/import on PC #90
Comments
I've just confirmed that this works successfully from OS X using the 32-bit force client (I couldn't download the 64-bit force client for OS X).
|
force import metadata_orig -v will give a bit more info. But it looks like it's looking for the packag.xml in the wrong place. I'll dig deeper. On Wed, Jul 16, 2014 at 8:48 AM, Wade Wegner notifications@github.com
Thanks, |
ok, just committed a fix for this. In the import.go file we had some hard-coded path separators that caused the method to fail due to adding entries into the zip file that looked like `c:\Users\Dave\Documents\Projects\test\metadata\objects/mycustomobject__c.object |
Wade please test with new version. |
dcarroll... I am having same issue in master release and 0.22.5 as well. It says "package.xml: No package.xml found" on PC- 32 bit. |
I'm struggling to determine if this is a bug or if I'm doing something incorrectly.
I've defined a number of objects in my DE org. I want to make it easier to reproduce in other orgs, so I thought I'd use the CLI to export the metadata so that, when using a different org, I could import it and get all my custom objects.
Simple tests won't work.
I've tried to run
force export metadata_orig
then, in the same org, runforce import metadata_orig
. I figured there'd be conflicts but all I get is:Failures - 1
Successes - 0
I've then logged into a different org and tried it again. Same error.
I've deleted everything but the
objects
folder and updated thepackage.xml
file so that only theCustomObject
type is listed. Same error.Not sure what else to do. Am I approaching this wrong?
This is the first I've tried it on a PC. I'm pretty sure I've done this on a Mac with no issues.
The text was updated successfully, but these errors were encountered: