jruby-jms 0.9.0
Sign up to get free protection for your applications and to get access to all the features.
- data/HISTORY.md +13 -0
- data/LICENSE.txt +201 -0
- data/README.md +276 -0
- data/Rakefile +22 -0
- data/examples/consumer.rb +23 -0
- data/examples/jms.yml +22 -0
- data/examples/log4j.properties +31 -0
- data/examples/performance/consumer.rb +27 -0
- data/examples/performance/producer.rb +31 -0
- data/examples/producer.rb +23 -0
- data/lib/jms.rb +25 -0
- data/lib/jms/connection.rb +480 -0
- data/lib/jms/javax_jms_map_message.rb +91 -0
- data/lib/jms/javax_jms_message.rb +264 -0
- data/lib/jms/javax_jms_message_consumer.rb +114 -0
- data/lib/jms/javax_jms_object_message.rb +26 -0
- data/lib/jms/javax_jms_queue_browser.rb +27 -0
- data/lib/jms/javax_jms_session.rb +285 -0
- data/lib/jms/javax_jms_text_message.rb +31 -0
- metadata +74 -0
data/HISTORY.md
ADDED
@@ -0,0 +1,13 @@
|
|
1
|
+
## 0.9.0 (2011-01-23)
|
2
|
+
|
3
|
+
* Revised API with cleaner interface
|
4
|
+
* Publish GEM
|
5
|
+
|
6
|
+
## 0.8.0 (2011-01-22)
|
7
|
+
|
8
|
+
* Release to the wild for general use
|
9
|
+
|
10
|
+
## 2008, 2009, 2010
|
11
|
+
|
12
|
+
* Previously known as jms4jruby
|
13
|
+
* Running in production at an enterprise processing a million messages a day
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright 2008, 2009, 2010, 2011 J. Reid Morrison, Inc.
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,276 @@
|
|
1
|
+
jruby-jms
|
2
|
+
=========
|
3
|
+
|
4
|
+
* http://github.com/reidmorrison/jruby-jms
|
5
|
+
|
6
|
+
### Current Activities & Backward Compatibility
|
7
|
+
|
8
|
+
Currently reviewing Logging which uses Apache Commons logging by default.
|
9
|
+
For now add the following Apache Commons and log4j libraries to your classpath
|
10
|
+
* commons-logging-1.1.1.jar
|
11
|
+
* log4j-1.2.16.jar
|
12
|
+
|
13
|
+
Please read the source files for now for documentation. Looking into rdoc doc
|
14
|
+
generation issue.
|
15
|
+
|
16
|
+
There may still be some changes to the API to make things better and/or simpler.
|
17
|
+
|
18
|
+
Once the code goes to V1.0.0 I will make every effort to not break the
|
19
|
+
existing interface in any way.
|
20
|
+
|
21
|
+
Feedback is welcome and appreciated :)
|
22
|
+
* Need input on Logging and any other tips and tricks on extending Interfaces
|
23
|
+
** For example, currently cannot override Interface methods with JRuby versions
|
24
|
+
(See Session::create_session, which is Session::session at this time)
|
25
|
+
* Looking for ideas on the best way to specify jar files so that they can be
|
26
|
+
'required' by jruby-jms rather than having to use the classpath
|
27
|
+
* Need to get rdoc working for
|
28
|
+
|
29
|
+
### Introduction
|
30
|
+
|
31
|
+
jruby-jms has been around in my toolbox since 2008. Since I was not an expert
|
32
|
+
in JMS I have held off releasing to the wild. I believe it is now of sufficient
|
33
|
+
quality and usefulness to release into the wild. In fact it has been used
|
34
|
+
in production at an enterprise site for 2 years now.
|
35
|
+
|
36
|
+
jruby-jms attempts to "rubify" the Java JMS API without
|
37
|
+
compromising performance. It does this by sprinkling "Ruby-goodness" into the
|
38
|
+
existing JMS Java interfaces, I.e. By adding Ruby methods to the existing
|
39
|
+
classes and interfaces. Since jruby-jms exposes the JMS
|
40
|
+
Java classes directly there is no performance impact that would have been
|
41
|
+
introduced had the entire API been wrapped in a Ruby layer.
|
42
|
+
|
43
|
+
In this way, using regular Ruby constructs a Ruby program can easily
|
44
|
+
interact with JMS in a highly performant way. Also, in this way you are not
|
45
|
+
limited to whatever the Ruby wrapper would have exposed, since the entire JMS
|
46
|
+
API is available to you at any time.
|
47
|
+
|
48
|
+
### Install
|
49
|
+
|
50
|
+
gem install jruby-jms
|
51
|
+
|
52
|
+
### Simplification
|
53
|
+
|
54
|
+
One of the difficulties with the regular JMS API is that it use completely
|
55
|
+
separate classes for Topics and Queues in JMS 1.1. This means that once a
|
56
|
+
program writes to a Queue for example, that without changing the program it
|
57
|
+
could not be changed to write to a topic. Also a consumer on a topic or a queue
|
58
|
+
are identical. jruby-jms fixes this issue by allowing you to have a Consumer
|
59
|
+
or Producer that is independent of whether it is producing or consuming to/from
|
60
|
+
or a Topic or a Queue. The complexity of which JMS class is used is taken care
|
61
|
+
of by jruby-jms.
|
62
|
+
|
63
|
+
Concepts & Terminology
|
64
|
+
----------------------
|
65
|
+
|
66
|
+
### Java Message Service (JMS) API
|
67
|
+
|
68
|
+
The JMS API is a standard interface part of Java EE 6 as a way for programs to
|
69
|
+
send and receive messages through a messaging and queuing system.
|
70
|
+
|
71
|
+
For more information on the JMS API: http://download.oracle.com/javaee/6/api/index.html?javax/jms/package-summary.html
|
72
|
+
|
73
|
+
### Broker / Queue Manager
|
74
|
+
|
75
|
+
Depending on which JMS provider you are using they refer to their centralized
|
76
|
+
server as either a Broker or Queue Manager. The Broker or Queue Manager is the
|
77
|
+
centralized "server" through which all messages pass through.
|
78
|
+
|
79
|
+
Some Brokers support an in-vm broker instance so that messages can be passed
|
80
|
+
between producers and consumers within the same Java Virtual Machine (JVM)
|
81
|
+
instance. This removes the need to make any network calls. Highly recommended
|
82
|
+
for passing messages between threads in the same JVM.
|
83
|
+
|
84
|
+
### Connection
|
85
|
+
|
86
|
+
In order to connect to any broker the Client JMS application must create a
|
87
|
+
connection. In traditional JMS a ConnectionFactory is used to create connections.
|
88
|
+
In jruby-jms the JMS::Connection takes care of the complexities of dealing with
|
89
|
+
the factory class, just pass the required parameters to Connection.new at it
|
90
|
+
takes care of the rest.
|
91
|
+
|
92
|
+
### Queue
|
93
|
+
|
94
|
+
A queue used for holding messages.
|
95
|
+
The queue is defined prior to the message being sent and is used to hold the
|
96
|
+
messages. The consumer does not have to be running in order to receive messages.
|
97
|
+
|
98
|
+
### Topic
|
99
|
+
|
100
|
+
Instead of sending messages to a single queue, a topic can be used to publish
|
101
|
+
messages and allow multiple consumers to register for messages that match the
|
102
|
+
topic they are interested in
|
103
|
+
|
104
|
+
### Producer
|
105
|
+
|
106
|
+
Producers write message to a queue or topic
|
107
|
+
|
108
|
+
ActiveMQ Example:
|
109
|
+
require 'rubygems'
|
110
|
+
|
111
|
+
# Include Active MQ Jar files (Not required if already in classpath)
|
112
|
+
require '~/Applications/apache-activemq-5.4.2/activemq-all-5.4.2.jar'
|
113
|
+
|
114
|
+
# Include Apache Commons Logging Jar file (For now, if not already in classpath)
|
115
|
+
require '~/Applications/apache-activemq-5.4.2/lib/commons-logging-1.1.jar'
|
116
|
+
require '~/Applications/apache-activemq-5.4.2/lib/optional/log4j-1.2.14.jar'
|
117
|
+
|
118
|
+
# Include JMS after ActiveMQ
|
119
|
+
require 'jms'
|
120
|
+
|
121
|
+
# Connect to ActiveMQ
|
122
|
+
config = {
|
123
|
+
:factory => 'org.apache.activemq.ActiveMQConnectionFactory',
|
124
|
+
:broker_url => 'tcp://localhost:61616'
|
125
|
+
}
|
126
|
+
|
127
|
+
JMS::Connection.session(config) do |session|
|
128
|
+
session.producer(:q_name => 'ExampleQueue') do |producer|
|
129
|
+
producer.send(session.message("Hello World"))
|
130
|
+
end
|
131
|
+
end
|
132
|
+
|
133
|
+
### Consumer
|
134
|
+
|
135
|
+
Consumers read message from a queue or topic
|
136
|
+
|
137
|
+
Example:
|
138
|
+
require 'rubygems'
|
139
|
+
|
140
|
+
# Include Active MQ Jar files (Not required if already in classpath)
|
141
|
+
require '~/Applications/apache-activemq-5.4.2/activemq-all-5.4.2.jar'
|
142
|
+
|
143
|
+
# Include Apache Commons Logging Jar file (For now, if not already in classpath)
|
144
|
+
require '~/Applications/apache-activemq-5.4.2/lib/commons-logging-1.1.jar'
|
145
|
+
require '~/Applications/apache-activemq-5.4.2/lib/optional/log4j-1.2.14.jar'
|
146
|
+
|
147
|
+
# Include JMS after ActiveMQ
|
148
|
+
require 'jms'
|
149
|
+
|
150
|
+
# Connect to ActiveMQ
|
151
|
+
config = {
|
152
|
+
:factory => 'org.apache.activemq.ActiveMQConnectionFactory',
|
153
|
+
:broker_url => 'tcp://localhost:61616'
|
154
|
+
}
|
155
|
+
|
156
|
+
JMS::Connection.session(config) do |session|
|
157
|
+
session.consume(:q_name => 'ExampleQueue', :timeout=>1000) do |message|
|
158
|
+
p message
|
159
|
+
end
|
160
|
+
end
|
161
|
+
|
162
|
+
Overview
|
163
|
+
--------
|
164
|
+
|
165
|
+
jruby-jms is a complete JRuby API into the Java Messaging Specification (JMS)
|
166
|
+
followed by many JMS Providers.
|
167
|
+
|
168
|
+
In order to communicate with a JMS provider jruby-jms needs the jar files in the
|
169
|
+
CLASSPATH that are supplied by the JMS Provider.
|
170
|
+
|
171
|
+
Threading
|
172
|
+
---------
|
173
|
+
|
174
|
+
A JMS::Connection instance can be shared between threads, whereas a session,
|
175
|
+
consumer, producer, and any artifacts created by the session should only be
|
176
|
+
used by one thread at a time.
|
177
|
+
|
178
|
+
For consumers, it is recommended to create a session for each thread and leave
|
179
|
+
that thread blocked on Consumer.receive. Or, even better use Connection.on_message
|
180
|
+
which will create a session, within which any message received from the specified
|
181
|
+
queue or topic match will be passed to the block.
|
182
|
+
|
183
|
+
### Example
|
184
|
+
|
185
|
+
Logging
|
186
|
+
-------
|
187
|
+
|
188
|
+
jruby-jms currently uses Apache Commons logging, but this is subject to changes
|
189
|
+
since many users of jruby-jms will want to use the Rails logger
|
190
|
+
|
191
|
+
Dependencies
|
192
|
+
------------
|
193
|
+
|
194
|
+
### JRuby
|
195
|
+
|
196
|
+
jruby-jms has been tested against JRuby 1.5.1, but should work with any
|
197
|
+
current JRuby version.
|
198
|
+
|
199
|
+
### JMS
|
200
|
+
|
201
|
+
Every JMS Provider has details on which jar files to include in your CLASSPATH
|
202
|
+
for their JMS client to work. Some examples for connection settings are covered
|
203
|
+
in the Connection.new documentation
|
204
|
+
|
205
|
+
Development
|
206
|
+
-----------
|
207
|
+
|
208
|
+
Want to contribute to jruby-jms?
|
209
|
+
|
210
|
+
First clone the repo and run the tests:
|
211
|
+
|
212
|
+
git clone git://github.com/reidmorrison/jruby-jms.git
|
213
|
+
cd jruby-jms
|
214
|
+
jruby -S rake test
|
215
|
+
|
216
|
+
Feel free to ping the mailing list with any issues and we'll try to resolve it.
|
217
|
+
|
218
|
+
|
219
|
+
Contributing
|
220
|
+
------------
|
221
|
+
|
222
|
+
Once you've made your great commits:
|
223
|
+
|
224
|
+
1. [Fork][1] Resque
|
225
|
+
2. Create a topic branch - `git checkout -b my_branch`
|
226
|
+
3. Push to your branch - `git push origin my_branch`
|
227
|
+
4. Create an [Issue][2] with a link to your branch
|
228
|
+
5. That's it!
|
229
|
+
|
230
|
+
You might want to checkout our [Contributing][cb] wiki page for information
|
231
|
+
on coding standards, new features, etc.
|
232
|
+
|
233
|
+
|
234
|
+
Mailing List
|
235
|
+
------------
|
236
|
+
|
237
|
+
TBA
|
238
|
+
|
239
|
+
Meta
|
240
|
+
----
|
241
|
+
|
242
|
+
* Code: `git clone git://github.com/reidmorrison/jruby-jms.git`
|
243
|
+
* Home: <http://github.com/reidmorrison/jruby-jms>
|
244
|
+
* Docs: <http://jruby-jms.github.com/jruby-jms/>
|
245
|
+
* Bugs: <http://github.com/reidmorrison/jruby-jms/issues>
|
246
|
+
* List: TBA
|
247
|
+
* Gems: <http://gemcutter.org/gems/jruby-jms>
|
248
|
+
|
249
|
+
This project uses [Semantic Versioning][sv].
|
250
|
+
|
251
|
+
|
252
|
+
Author
|
253
|
+
------
|
254
|
+
|
255
|
+
Reid Morrison :: rubywmq@gmail.com :: @reidmorrison
|
256
|
+
|
257
|
+
[1]: http://help.github.com/forking/
|
258
|
+
[2]: http://github.com/reidmorrison/jruby-jms/issues
|
259
|
+
[sv]: http://semver.org/
|
260
|
+
|
261
|
+
License
|
262
|
+
-------
|
263
|
+
|
264
|
+
Copyright 2008, 2009, 2010, 2011 J. Reid Morrison
|
265
|
+
|
266
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
267
|
+
you may not use this file except in compliance with the License.
|
268
|
+
You may obtain a copy of the License at
|
269
|
+
|
270
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
271
|
+
|
272
|
+
Unless required by applicable law or agreed to in writing, software
|
273
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
274
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
275
|
+
See the License for the specific language governing permissions and
|
276
|
+
limitations under the License.
|