Skip to content

Commit

Permalink
add deploying manually section from @pameyer #3907
Browse files Browse the repository at this point in the history
  • Loading branch information
pdurbin committed Jun 20, 2017
1 parent a299f8a commit dccd9b0
Showing 1 changed file with 12 additions and 1 deletion.
13 changes: 12 additions & 1 deletion doc/sphinx-guides/source/developers/dev-environment.rst
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,18 @@ Deploy on Save

Out of the box, Netbeans is configured to "Deploy on Save" which means that if you save any changes to project files such as Java classes, XHTML files, or "bundle" files (i.e. Bundle.properties), the project is recompiled and redeployed to Glassfish automatically. This behavior works well for many of us but if you don't like it, you can turn it off by right-clicking "dataverse" under the Projects tab, clicking "Run" and unchecking "Deploy on Save".

Note that it's possible to deploy the war file using the ``asadmin`` command. The :doc:`/installation/installation-main` section of the Installation Guide has more information on this topic.
Deploying Manually
~~~~~~~~~~~~~~~~~~

For developers not using Netbeans, or deploying to a non-local system for development, code can be deployed manually.
There are four steps to this process:

1. Build the war file: ``mvn package``
2. Undeploy the Dataverse application (if necessary): ``asadmin undeploy dataverse-VERSION``
3. Copy the war file to the development server (if necessary)
4. Deploy the new code: ``asadmin deploy /path/to/dataverse-VERSION.war``

The :doc:`/installation/installation-main` section of the Installation Guide has more information on this topic.

Netbeans Connector Chrome Extension
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down

0 comments on commit dccd9b0

Please sign in to comment.