README.md in leap_salesforce-1.3.1 vs README.md in leap_salesforce-1.4.0

@@ -102,10 +102,12 @@
 
 * 'client_id'
 * 'client_secret'
 * 'password'
 
+> If these variables can be set in a `.env` file they will be loaded automatically
+
 > Security tokens can be set for each user (adding to password in OAuth like in [this article](https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_login.htm))
 > To do that set an environment variable as USER_KEY_token. E.g, so for a user with a key of :admin
 > the token would be set with the `admin_token` environment variable
 
 Tests can be run using the default `Rake` task.
@@ -171,9 +173,22 @@
 E.g., `Broker: Broker__c` will mean that a Ruby class called `Broker` will be created that will map to the `Broker__c`
 custom object.
 
 A separate file with the ending `_field_names` is also created from the metadata for each object. This creates
 accessors for each field in the table with names that map from a Ruby friendly name to the Salesforce backend name.
+
+A java class can be created using the following syntax in `.leap_salesforce.yml`. The default language will be Ruby
+
+```yaml
+language: java
+lib_folder: main/java  # Path to store auto generated Java classes
+soql_field_start_text: |
+  package com.salesforce.test.pojo.soqlObjects;
+```
+
+These task can also be executed from the executable of this project with `leap_salesforce create_soql_objects --language=ruby`
+
+For generation of other languages, raise an issue
 
 * `leaps:create_enums`
 
 This task reads the soql objects defined in `.leap_salesforce.yml` and creates a `metadata/enum` folder that has
 picklist information for all the picklist fields of each object. These are designed to be readonly as they will