ae554b43db
[maven-release-plugin] prepare for next development iteration
2023-06-14 18:20:58 -04:00
2be5c54cd0
[maven-release-plugin] prepare release 2.29.0
2023-06-14 18:20:45 -04:00
2378d187af
[maven-release-plugin] prepare for next development iteration
2023-01-31 07:22:48 -05:00
893e1e7916
[maven-release-plugin] prepare release 2.28.0
2023-01-31 07:22:47 -05:00
dce4ba3c1a
[maven-release-plugin] prepare for next development iteration
2022-11-08 13:17:38 -06:00
1fd6cb6239
[maven-release-plugin] prepare release 2.27.0
2022-11-08 12:46:20 -06:00
8cba446e2b
ARTEMIS-4048: stop -all client modules needlessly grabbing their own -SNAPSHOT sources during build
...
- Always produce the original basically-empty sources jar for the
module, before the shading, meaning its always available.
- Do the same for the main jar, to avoid the shading operating on a
previously-shaded renamed output from a prior run if not cleaning.
2022-10-13 13:06:09 +01:00
5d8e7fe829
[maven-release-plugin] prepare for next development iteration
2022-09-21 13:00:47 -04:00
2d7b1a3ef7
[maven-release-plugin] prepare release 2.26.0
2022-09-21 13:00:46 -04:00
4ad830fb95
Bumping artemis as 3.0
...
After removing ActiveMQ Artemis rest (per ARTEMIS-3987), we should start promoting Artemis as 3.0
2022-09-12 15:09:31 -04:00
11eab60584
[maven-release-plugin] prepare for next development iteration
2022-08-30 18:04:06 -04:00
fb1b362b47
[maven-release-plugin] prepare release 2.25.0
2022-08-30 18:04:05 -04:00
fa002728f2
[maven-release-plugin] prepare for next development iteration
2022-07-26 11:59:21 -04:00
897d9beaef
[maven-release-plugin] prepare release 2.24.0
2022-07-26 11:59:19 -04:00
79daf49105
[maven-release-plugin] prepare for next development iteration
2022-07-21 17:44:35 -04:00
cc4867ccba
[maven-release-plugin] prepare release 2.24.0
2022-07-21 17:44:33 -04:00
0fab0dae91
[maven-release-plugin] prepare for next development iteration
2022-06-07 12:39:09 -04:00
224ca0d4d7
[maven-release-plugin] prepare release 2.23.0
2022-06-07 12:39:07 -04:00
57fa8b8271
[maven-release-plugin] prepare for next development iteration
2022-04-27 17:26:46 -04:00
1a49845628
[maven-release-plugin] prepare release 2.22.0
2022-04-27 17:26:45 -04:00
6eb78a2634
ARTEMIS-3783: rationalise config for alternate jakarta spec versions to simplify and align their use
2022-04-20 10:57:32 +01:00
e97e239771
ARTEMIS-3782: use existing managed version for maven-shade-plugin uses
2022-04-20 10:33:57 +01:00
a0e7cb4eae
[maven-release-plugin] prepare for next development iteration
2022-03-22 13:34:58 -04:00
d57ac487c7
[maven-release-plugin] prepare release 2.21.0
2022-03-22 13:34:55 -04:00
e34677f5c0
[maven-release-plugin] prepare for next development iteration
2021-12-14 22:50:55 -05:00
3dea7eeb71
[maven-release-plugin] prepare release 2.20.0
2021-12-14 22:50:53 -05:00
bfc10dcf8b
ARTEMIS-3546 Jakarta javax.json incompability on jakarta all client
...
Domenico Bruscino provided the JSON Wrapper used here. Thanks Domenico!
2021-11-19 13:20:38 -05:00
402842062a
[maven-release-plugin] prepare for next development iteration
2021-10-11 13:35:57 -05:00
5fcb763234
[maven-release-plugin] prepare release 2.19.0
2021-10-11 13:35:06 -05:00
447422604c
ARTEMIS-3484 flesh out Jakarta Messaging support
...
Back in version 2.17.0 we began to provide Maven artifacts for Jakarta
Messaging client resources. This commit expands that support in the
following ways:
- Distribute a Jakarta Messaging 3.0 client with the broker (in the
'lib/client' directory alongside the JMS client.
- Update documentation.
- Add example using the Jakarta Messaging client.
- Update Artemis CLI to use core instead of JMS as it was causing
conflicts with the new Jarkarta Messaging client.
- Add example to build Jarkarta Messaging version of the JCA RA for
deployment into Jakarta EE 9 application servers.
2021-09-15 15:20:54 -04:00
Clebert Suconic
Justin Bertram
Robbie Gemmell