- Restore it but in pulsar.util.
 - Fix #91 while at it.

 - Depend on galaxy-lib.
 - Move things into pulsar.util and/or pulsar.client.util as makes sense.
 - Use more Galaxy idioms.

Fix bug introduced in 22070bc2 .

Closing out old doc bug

due to refactoring).

Fixes #30

Resubmit messages to the right queue

consumer. Also, resubmit messages to the correct queue.

Fix config.py on Windows.

Add new logo

Fix deepcopy() error with copying the errback method from PulsarExchange.

Updated the job_conf_sample_remote_cluster.xml for the right default …

Ensure AMQP consumers receive published messages

actually a PEP-8-suggested acceptable option of how to handle the
offending situation. =P

Added the slash for the self-closed plugin pulsar tag

Small typo fix

Small typo fix: `context` instead of `contxt`

guarantee that a published message is actually received by the server.

Fixes #77

In the `job_conf_sample_remote_cluster.xml`, the default destinations attribute was set on `drmaa` instead of `local_cluster`.

This was producing the following Exception:

```
Exception: Problem parsing the XML in file /Users/marenc01/Dev/galaxy/config/job_conf.xml, please correct the indicated portion of the file and restart Galaxy.<destinations> default attribute 'pulsar' does not match a defined id or tag in a child element
```

When launching Galaxy.

Added the slash for the self-closed plugin pulsar tag, otherwise we get the Exception:

```
Exception: Problem parsing the XML in file /Users/marenc01/Dev/galaxy/config/job_conf.xml, please correct the indicated portion of the file and restart Galaxy.mismatched tag: line 6, column 6
```

Add a job manager for XSEDE jobs

submission).

Fix pip dependency installation