Recent changes to Development Environment

Development Environment modified by Patrick Brunschwig

Patrick Brunschwig — Wed, 20 Apr 2016 11:01:09 -0000

--- v46
+++ v47
@@ -28,7 +28,7 @@
     + Place the file in the extensions folder of your profile and restart the application.
     + If everything was installed correctly, you will be asked once by the AddOn Manager to confirm the usage of the Enigmail AddOn.

-+ For **static code analysis** (useful whenever you edit the code) you need eslint:
++ For **static code analysis** (useful whenever you edit the code) you need eslint, version 2.x:
     + Ideally you download eslint from the node-js project:
         + Download and install [node-js](https://www.nodejs.org/)
         + install eslint with: "npm install -g eslint"

Development Environment modified by Ludwig Hügelschäfer

Ludwig Hügelschäfer — Fri, 08 Jan 2016 18:19:01 -0000

--- v45
+++ v46
@@ -31,7 +31,7 @@
 + For **static code analysis** (useful whenever you edit the code) you need eslint:
     + Ideally you download eslint from the node-js project:
         + Download and install [node-js](https://www.nodejs.org/)
-        + install jshint with: "npm install -g eslint"
+        + install eslint with: "npm install -g eslint"
         + If not part of the path (e.g. under cygwin) extend the PATH accordingly.
                For example under Windows with cygwin, it might look like:

Development Environment modified by Patrick Brunschwig

Patrick Brunschwig — Thu, 07 Jan 2016 16:56:56 -0000

--- v44
+++ v45
@@ -28,17 +28,17 @@
     + Place the file in the extensions folder of your profile and restart the application.
     + If everything was installed correctly, you will be asked once by the AddOn Manager to confirm the usage of the Enigmail AddOn.

-+ For **static code analysis** (useful whenever you edit the code) you need jshint:
-    + Ideally you download jshint from the node-js project:
++ For **static code analysis** (useful whenever you edit the code) you need eslint:
+    + Ideally you download eslint from the node-js project:
         + Download and install [node-js](https://www.nodejs.org/)
-        + install jshint with: "npm install -g jshint"
+        + install jshint with: "npm install -g eslint"
         + If not part of the path (e.g. under cygwin) extend the PATH accordingly.
                For example under Windows with cygwin, it might look like:

                    PATH="$PATH:/cygdrive/C/Program Files/nodejs"
                    PATH="$PATH:/cygdrive/C/Users/<username>/AppData/Roaming/npm"

-    + Perform static code analysis with '**make jshint**' (included also in other targets)                     
+    + Perform static code analysis with '**make eslint**' (included also in other targets)                     

 + To run **unit tests** you need JSUnit:
     + Install the [JSUnit Addon](https://sourceforge.net/u/pbrunschwig/jsunit/wiki/Home/) in the Thunderbird profile that is used for unit tests.

Development Environment modified by Nicolai Josuttis

Nicolai Josuttis — Sat, 19 Sep 2015 09:29:32 -0000

--- v43
+++ v44
@@ -51,4 +51,4 @@
     + Perform unit tests with '**make test**' (included also in other targets)

 + Note that [some Thoughworks guys](http://www.thoughtworks.com/insights/blog/lessons-learned-working-enigmail) did provide support for complete development environment with **Vagrant** or **Docker**
-    + See directory [provisioning](https://sourceforge.net/p/enigmail/source/ci/master/tree/provisioning/) in the Enigmail sources
+    + See directory [provisioning/](https://sourceforge.net/p/enigmail/source/ci/master/tree/provisioning/) in the Enigmail sources

Development Environment modified by Nicolai Josuttis

Nicolai Josuttis — Sat, 19 Sep 2015 09:28:51 -0000

--- v42
+++ v43
@@ -19,8 +19,9 @@
         + According the [recommendations in the MozillaDevNetwork](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment), you should:
             + start Thunderbird in all development profiles with the **-no-remote**  option to be able to run unit tests, while having another Thunderbird/Firefox open
             + start your regular Thunderbird with the **-new-instance** option to be able to start your ordinary mailer while running unit tests
-+ "Install" Enigmail in both profiles using the "Proxy File" method (see the [MDN hints about this](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment#Firefox_extension_proxy_file))
-    1. Create the file "{847b3a00-7ab1-11d4-8f02-006008948af5}" in the "extensions" directory under your profile directory.
+
++ "Install" Enigmail in all development profiles using the "Proxy File" method (see the [MDN hints about this](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment#Firefox_extension_proxy_file))
+    + Create the file "{847b3a00-7ab1-11d4-8f02-006008948af5}" in the "extensions" directory under your profile directory.
         * Note: You can't create directories without suffixes under Windows. Use mkdir from cygwin instead.
     + The contents of this file should be the path to the _build/dist_ directory of the Enigmail source tree (i.e. after make was run). E.g. _/home/patrick/develop/enigmail/build/dist_. Remember to remove any trailing whitespace.
         * Note: If you already installed the extension via XPI, you should uninstall it first before creating the pointer file.

Development Environment modified by Nicolai Josuttis

Nicolai Josuttis — Sat, 19 Sep 2015 09:27:20 -0000

--- v41
+++ v42
@@ -14,12 +14,11 @@
     * After installed, you can start it at any time from Thunderbird under Extras -> Tiny JS Debugger

 + For **development in general** we recommend two have **2** (two!) additional Thunderbird **profiles** (beside the one that is used as your day-to-day emailer):
-    1. One is used for developing and manual tests testing.
-    2. One is exclusively used for unit tests. 
-    + See http://kb.mozillazine.org/Profile_Manager for general information about multiple profiles
-    + According the [recommendations in the MozillaDevNetwork](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment), you should:
-        + start Thunderbird in all development profiles with the **-no-remote**  option to be able to run unit tests, while having another Thunderbird/Firefox open
-        + start your regular Thunderbird with the **-new-instance** option to be able to start your ordinary mailer while running unit tests
+    + One is used for developing or manual tests and one is exclusively used for unit tests. 
+        + See http://kb.mozillazine.org/Profile_Manager for general information about multiple profiles
+        + According the [recommendations in the MozillaDevNetwork](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment), you should:
+            + start Thunderbird in all development profiles with the **-no-remote**  option to be able to run unit tests, while having another Thunderbird/Firefox open
+            + start your regular Thunderbird with the **-new-instance** option to be able to start your ordinary mailer while running unit tests
 + "Install" Enigmail in both profiles using the "Proxy File" method (see the [MDN hints about this](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment#Firefox_extension_proxy_file))
     1. Create the file "{847b3a00-7ab1-11d4-8f02-006008948af5}" in the "extensions" directory under your profile directory.
         * Note: You can't create directories without suffixes under Windows. Use mkdir from cygwin instead.

Development Environment modified by Nicolai Josuttis

Nicolai Josuttis — Sat, 19 Sep 2015 09:26:10 -0000

--- v40
+++ v41
@@ -18,8 +18,8 @@
     2. One is exclusively used for unit tests. 
     + See http://kb.mozillazine.org/Profile_Manager for general information about multiple profiles
     + According the [recommendations in the MozillaDevNetwork](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment), you should:
-        + start Thunderbird (in all development profiles) with the -no-remote option to be able to run unit tests, while having another Thunderbird/Firefox open
-        + start your regular Thunderbird with the -new-instance option to be able to start your ordinary mailer while running unit tests
+        + start Thunderbird in all development profiles with the **-no-remote**  option to be able to run unit tests, while having another Thunderbird/Firefox open
+        + start your regular Thunderbird with the **-new-instance** option to be able to start your ordinary mailer while running unit tests
 + "Install" Enigmail in both profiles using the "Proxy File" method (see the [MDN hints about this](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment#Firefox_extension_proxy_file))
     1. Create the file "{847b3a00-7ab1-11d4-8f02-006008948af5}" in the "extensions" directory under your profile directory.
         * Note: You can't create directories without suffixes under Windows. Use mkdir from cygwin instead.

Development Environment modified by Nicolai Josuttis

Nicolai Josuttis — Sat, 19 Sep 2015 09:24:15 -0000

--- v39
+++ v40
@@ -18,7 +18,8 @@
     2. One is exclusively used for unit tests. 
     + See http://kb.mozillazine.org/Profile_Manager for general information about multiple profiles
     + According the [recommendations in the MozillaDevNetwork](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment), you should:
-        + start Thunderbird (in all profiles) with the -no-remote option to be able to run unit tests, while having Thunderbird open
+        + start Thunderbird (in all development profiles) with the -no-remote option to be able to run unit tests, while having another Thunderbird/Firefox open
+        + start your regular Thunderbird with the -new-instance option to be able to start your ordinary mailer while running unit tests
 + "Install" Enigmail in both profiles using the "Proxy File" method (see the [MDN hints about this](https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment#Firefox_extension_proxy_file))
     1. Create the file "{847b3a00-7ab1-11d4-8f02-006008948af5}" in the "extensions" directory under your profile directory.
         * Note: You can't create directories without suffixes under Windows. Use mkdir from cygwin instead.

Development Environment modified by Nicolai Josuttis

Nicolai Josuttis — Wed, 16 Sep 2015 05:57:14 -0000

--- v38
+++ v39
@@ -49,5 +49,5 @@
        https://sourceforge.net/u/pbrunschwig/jsunit/wiki/TipsAndTricks/
     + Perform unit tests with '**make test**' (included also in other targets)

-+ Note that [some Thoughworks guys](http://www.thoughtworks.com/insights/blog/lessons-learned-working-enigmail) did provide a development environment with **Vagrant and Docker**
++ Note that [some Thoughworks guys](http://www.thoughtworks.com/insights/blog/lessons-learned-working-enigmail) did provide support for complete development environment with **Vagrant** or **Docker**
     + See directory [provisioning](https://sourceforge.net/p/enigmail/source/ci/master/tree/provisioning/) in the Enigmail sources

Development Environment modified by Nicolai Josuttis

Nicolai Josuttis — Tue, 15 Sep 2015 18:50:43 -0000

--- v37
+++ v38
@@ -49,5 +49,5 @@
        https://sourceforge.net/u/pbrunschwig/jsunit/wiki/TipsAndTricks/
     + Perform unit tests with '**make test**' (included also in other targets)

-+ Note that some guys did provide a development environment with **Vagrant and Docker**
++ Note that [some Thoughworks guys](http://www.thoughtworks.com/insights/blog/lessons-learned-working-enigmail) did provide a development environment with **Vagrant and Docker**
     + See directory [provisioning](https://sourceforge.net/p/enigmail/source/ci/master/tree/provisioning/) in the Enigmail sources