ForceDotBundle | integrating TextMate with the Force.com Migration Tool

by joshbirk JavaScript Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | ForceDotBundle Summary

ForceDotBundle is a JavaScript library typically used in Manufacturing, Utilities, Machinery, Process applications. ForceDotBundle has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

I've got videos on using the bundle on YouTube: You may also wish to check out MavensMate, a ForceDotCom bundle for TextMate created by Mavens Software. It has some extremely pretty interfaces and some great functionality: This is unofficial software and unsupported as well. I've been able to keep up with updates and bug fixes so far, but make no promises.

Support

Quality

Security

License

Reuse

Support

ForceDotBundle has a low active ecosystem.

It has 29 star(s) with 8 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

There are 3 open issues and 6 have been closed. On average issues are closed in 11 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of ForceDotBundle is current.

Quality

ForceDotBundle has 0 bugs and 0 code smells.

Security

ForceDotBundle has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ForceDotBundle code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ForceDotBundle does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

ForceDotBundle releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

ForceDotBundle saves you 1350 person hours of effort in developing the same functionality from scratch.

It has 3025 lines of code, 0 functions and 43 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ForceDotBundle

Get all kandi verified functions for this library.

ForceDotBundle Key Features

No Key Features are available at this moment for ForceDotBundle.

ForceDotBundle Examples and Code Snippets

No Code Snippets are available at this moment for ForceDotBundle.

Community Discussions

No Community Discussions are available at this moment for ForceDotBundle.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ForceDotBundle

Once you've installed the bundle, create a new project.
Create a new directory in Finder, name it something reasonable for your project.
Drag the folder to the project pane in TextMate.
Create some kind of scratch file.
Open the empty file. Now use "Create New Project" from the ForceDotBundle bundle. A popup will give the overview of the changes. These changes may not appear right away in the project pane. They will be in Finder.
Update "build.properties" with your username, password and if needed, the login URL (for sandboxes).
If you want to pull down existing files, run "Get Latest". These changes may not appear right away in the project pane. They will be in Finder.
Or if you just want to be additive, right click on say, classes, and use one of the templates.
Enjoy.
You may need to whitelist your IP for some of the features.

Support

in build.properties. The next step is swap out your password with "password:accountname", highlight that text and then run "Add Password" under the Keychain menu in the bundle. There will be some keychain prompts and then your password will be replaced with just "accountname". From there on out, the bash will swap out your password in build.properties when it runs a build, and then swap it back when it is done. I highly recommend this for everyone concerned with having passwords in a text file on your laptop. Which should be everyone. The only downside is with multiple builds that execute against build.properties at the same time may wipe the file out. Working on it.

Find more information at: