a3840c23c3
[maven-release-plugin] prepare for next development iteration
2016-08-16 11:59:55 -04:00
d38ef19bf6
[maven-release-plugin] prepare release 1.4.0
2016-08-16 11:59:36 -04:00
aed49b3894
Spelling fixes
2016-07-26 14:24:45 +03:00
9ae39f663f
[maven-release-plugin] prepare for next development iteration
2016-06-09 12:52:56 +01:00
221039e353
[maven-release-plugin] prepare release 1.3.0
2016-06-09 12:49:13 +01:00
319439ab27
[maven-release-plugin] prepare for next development iteration
2016-06-09 12:25:19 +01:00
2c5ab446be
[maven-release-plugin] prepare release 1.3.0
2016-06-09 12:24:48 +01:00
4a07091718
[maven-release-plugin] prepare for next development iteration
2016-06-09 11:25:03 +01:00
93cf7b4b9b
[maven-release-plugin] prepare release 1.3.0
2016-06-09 11:23:03 +01:00
4574b3ee13
[maven-release-plugin] prepare for next development iteration
2016-06-08 11:03:35 +01:00
2b3d22c5cc
[maven-release-plugin] prepare release 1.3.0
2016-06-08 11:02:14 +01:00
4922a7618a
Bump to next version to 1.3.0-SNAPSHOT
2016-01-20 17:25:07 +00:00
2c430e597b
[maven-release-plugin] prepare for next development iteration
2016-01-04 11:50:36 +00:00
f182c806b6
[maven-release-plugin] prepare release 1.2.0
2016-01-04 11:49:58 +00:00
5f32e6575c
[maven-release-plugin] prepare for next development iteration
2016-01-04 09:24:34 +00:00
150c5d87aa
[maven-release-plugin] prepare release 1.2.0
2016-01-04 09:19:35 +00:00
90c9469701
[maven-release-plugin] prepare for next development iteration
2015-12-17 17:03:40 +00:00
df61224d2d
[maven-release-plugin] prepare release 1.2.0
2015-12-17 17:01:58 +00:00
f8a1c5ba8e
Remove redundant type arguments
2015-12-07 22:55:05 +02:00
25ae472455
Add missing @Override annotations
2015-12-06 01:27:35 +02:00
1cdc01fc44
ARTEMIS-295 Remove 'yet' from log messages
2015-11-04 14:49:11 +00:00
7d6a6de8dd
[ARTEMIS-294] Use doPriviledged block for ServiceLoader
...
In ServiceUtils, loads services from an AccessController.doPriviledged
block and use the ServiceUtils's own classloader instead of the TCCL
(that may be different depending on who's requesting a managed
connection factory first)
JIRA: https://issues.apache.org/jira/browse/ARTEMIS-294
2015-11-04 12:26:48 +01:00
4bfb6e3a8c
[ARTEMIS-236] Improve Legacy support on older migrating clients
...
set the client protocol manager factory on the server locator
JIRA: https://issues.apache.org/jira/browse/ARTEMIS-236
2015-10-09 12:38:30 +02:00
206acdac7d
ARTEMIS-238 and ARTEMIS-236 Fixing Legacy protocol support
2015-10-08 20:32:43 -04:00
bb2c890803
[maven-release-plugin] prepare for next development iteration
2015-09-15 15:43:44 +01:00
63ea448728
[maven-release-plugin] prepare release 1.1.0
2015-09-15 15:41:37 +01:00
6408fd0357
[maven-release-plugin] prepare for next development iteration
2015-09-11 19:01:57 +01:00
c512f12a34
[maven-release-plugin] prepare release 1.1.0
2015-09-11 19:01:19 +01:00
fec6546480
[maven-release-plugin] prepare for next development iteration
2015-09-08 16:39:59 +01:00
4d0b15b043
[maven-release-plugin] prepare release 1.1.0
2015-09-08 16:29:09 +01:00
82f6a88d59
[maven-release-plugin] prepare for next development iteration
2015-09-07 10:02:01 +01:00
8c1e0e15fc
[maven-release-plugin] prepare release 1.1.0
2015-09-07 10:01:10 +01:00
a2aa18c123
[maven-release-plugin] prepare for next development iteration
2015-09-04 20:20:13 +01:00
a5decb659e
[maven-release-plugin] prepare release 1.1.0
2015-09-04 20:19:11 +01:00
4576ccea08
[maven-release-plugin] prepare for next development iteration
2015-09-04 19:48:52 +01:00
a6e513c23b
Pass JNDI name in XARecoveryConfig
...
Some TX managers require JNDI name for recovery purposes. This patch
passes JNDI name in RA to RecoveryRegistry implementations via
XARecoveryConfig objects.
2015-08-27 14:09:33 -04:00
bac96047f5
automatic checkstyle change
...
this is just calling Idea format on all the files using the new style
I am separating manual changes from automatic changes in case I have to repeat the manual changes again
2015-08-10 09:26:42 -04:00
b0a80ce1be
Spelling fixes
2015-07-09 10:41:03 -04:00
51c34c87d2
ARTEMIS-136 - XA Error fix with proper exception error
...
https://issues.apache.org/jira/browse/ARTEMIS-136
From what I researched from implementers of XA TM if you throw ERR over communication errors the transaction manager will create
an heuristic transaction to be manually dealt with.
Other XA Implementations (such as Oracle JDBC) are return FAIL over communication failures during any XA operation.
2015-06-15 16:34:55 -04:00
d48b4f4770
ARTEMIS-129 License header should be a normal comment
...
To reproduce this commit, apply a replace regex rule using:
search regex: /\*\*\n \* Licensed
replace: /\*\n \* Licensed
These files had to be changed manually:
artemis-selector/src/main/javacc/HyphenatedParser.jj
artemis-selector/src/main/javacc/StrictParser.jj
artemis-website/src/main/resources/styles/impact/css/pygmentize.css
artemis-website/src/main/resources/styles/impact/css/site.css
2015-06-03 10:19:45 -04:00
22d54c5830
[maven-release-plugin] prepare for next development iteration
2015-05-21 13:47:45 +01:00
3435d5948f
[maven-release-plugin] prepare release 1.0.0
2015-05-21 13:43:56 +01:00
97210427df
[maven-release-plugin] prepare for next development iteration
2015-05-20 11:26:38 +01:00
3fb3799f91
[maven-release-plugin] prepare release 1.0.0
2015-05-20 11:17:31 +01:00
73c5f2e342
[maven-release-plugin] prepare for next development iteration
2015-05-13 15:24:55 +01:00
bfc9d8f72d
[maven-release-plugin] prepare release 1.0.0
2015-05-13 15:24:16 +01:00
a17c828b85
Ensure all references to the project use ActiveMQ Artemis
2015-05-13 11:51:26 +01:00
1013e7f1dd
[maven-release-plugin] prepare for next development iteration
2015-05-12 13:51:35 +01:00
d6466b7a1b
[maven-release-plugin] prepare release 1.0.0
2015-05-12 13:50:56 +01:00
3e34044d2b
[maven-release-plugin] prepare for next development iteration
2015-05-11 21:50:41 +01:00
Clebert Suconic
Ville Skyttä
Martyn Taylor
Jeff Mesnil
Thiago Kronig