root
2d7cb47edd
[maven-release-plugin] prepare for next development iteration
2018-09-27 19:00:45 +00:00
root
3a9ac829d5
[maven-release-plugin] prepare release netty-4.1.30.Final
2018-09-27 18:56:12 +00:00
root
a580dc7585
[maven-release-plugin] prepare for next development iteration
2018-08-24 06:36:33 +00:00
root
3fc789e83f
[maven-release-plugin] prepare release netty-4.1.29.Final
2018-08-24 06:36:06 +00:00
root
fcb19cb589
[maven-release-plugin] prepare for next development iteration
2018-07-27 04:59:28 +00:00
root
ff785fbe39
[maven-release-plugin] prepare release netty-4.1.28.Final
2018-07-27 04:59:06 +00:00
root
b4dbdc2036
[maven-release-plugin] prepare for next development iteration
2018-07-11 15:37:40 +00:00
root
1c16519ac8
[maven-release-plugin] prepare release netty-4.1.27.Final
2018-07-11 15:37:21 +00:00
root
7bb9e7eafe
[maven-release-plugin] prepare for next development iteration
2018-07-10 05:21:24 +00:00
root
8ca5421bd2
[maven-release-plugin] prepare release netty-4.1.26.Final
2018-07-10 05:18:13 +00:00
Norman Maurer
64bb279f47
[maven-release-plugin] prepare for next development iteration
2018-05-14 11:11:45 +00:00
Norman Maurer
c67a3b0507
[maven-release-plugin] prepare release netty-4.1.25.Final
2018-05-14 11:11:24 +00:00
Karl Pauls
5256d17363
Make osgi testing work with java>=9 by updating to felix framework 5.6.10 ( #7923 )
...
Motivation:
Currently, the testing-osgi is set to skip if run with java>=9. That is not necessary when using a newer version of Felix.
Modification:
Update to Felix framework 5.6.10 (which has better jpms support), add some more --add-opens to not have WARN messages, and remove the skipOsgiTestsuite setting from the parent pom.
Result:
OSGi tests run and pass on java>=9.
2018-05-09 18:26:38 +02:00
Norman Maurer
b75f44db9a
[maven-release-plugin] prepare for next development iteration
2018-04-19 11:56:07 +00:00
Norman Maurer
04fac00c8c
[maven-release-plugin] prepare release netty-4.1.24.Final
2018-04-19 11:55:47 +00:00
root
0a61f055f5
[maven-release-plugin] prepare for next development iteration
2018-04-04 10:44:46 +00:00
root
8c549bad38
[maven-release-plugin] prepare release netty-4.1.23.Final
2018-04-04 10:44:15 +00:00
Norman Maurer
69582c0b6c
[maven-release-plugin] prepare for next development iteration
2018-02-21 12:52:33 +00:00
Norman Maurer
786f35c6c9
[maven-release-plugin] prepare release netty-4.1.22.Final
2018-02-21 12:52:19 +00:00
Norman Maurer
e71fa1e7b6
[maven-release-plugin] prepare for next development iteration
2018-02-05 12:02:35 +00:00
Norman Maurer
41ebb5fcca
[maven-release-plugin] prepare release netty-4.1.21.Final
2018-02-05 12:02:19 +00:00
Norman Maurer
ea58dc7ac7
[maven-release-plugin] prepare for next development iteration
2018-01-21 12:53:51 +00:00
Norman Maurer
96c7132dee
[maven-release-plugin] prepare release netty-4.1.20.Final
2018-01-21 12:53:34 +00:00
Norman Maurer
264a5daa41
[maven-release-plugin] prepare for next development iteration
2017-12-15 13:10:54 +00:00
Norman Maurer
0786c4c8d9
[maven-release-plugin] prepare release netty-4.1.19.Final
2017-12-15 13:09:30 +00:00
Norman Maurer
b2bc6407ab
[maven-release-plugin] prepare for next development iteration
2017-12-08 09:26:15 +00:00
Norman Maurer
96732f47d8
[maven-release-plugin] prepare release netty-4.1.18.Final
2017-12-08 09:25:56 +00:00
Norman Maurer
188ea59c9d
[maven-release-plugin] prepare for next development iteration
2017-11-08 22:36:53 +00:00
Norman Maurer
812354cf1f
[maven-release-plugin] prepare release netty-4.1.17.Final
2017-11-08 22:36:33 +00:00
Norman Maurer
625a7426cd
[maven-release-plugin] prepare for next development iteration
2017-09-25 06:12:32 +02:00
Norman Maurer
f57d8f00e1
[maven-release-plugin] prepare release netty-4.1.16.Final
2017-09-25 06:12:16 +02:00
Norman Maurer
b967805f32
[maven-release-plugin] prepare for next development iteration
2017-08-24 15:38:22 +02:00
Norman Maurer
da8e010a42
[maven-release-plugin] prepare release netty-4.1.15.Final
2017-08-24 15:37:59 +02:00
Norman Maurer
52f384b37f
[maven-release-plugin] prepare for next development iteration
2017-08-02 12:55:10 +00:00
Norman Maurer
8cc1071881
[maven-release-plugin] prepare release netty-4.1.14.Final
2017-08-02 12:54:51 +00:00
Norman Maurer
2a376eeb1b
[maven-release-plugin] prepare for next development iteration
2017-07-06 13:24:06 +02:00
Norman Maurer
c7f8168324
[maven-release-plugin] prepare release netty-4.1.13.Final
2017-07-06 13:23:51 +02:00
Norman Maurer
fd67a2354d
[maven-release-plugin] prepare for next development iteration
2017-06-08 21:06:24 +02:00
Norman Maurer
3acd5c68ea
[maven-release-plugin] prepare release netty-4.1.12.Final
2017-06-08 21:06:01 +02:00
Norman Maurer
0db2901f4d
[maven-release-plugin] prepare for next development iteration
2017-05-11 16:00:55 +02:00
Norman Maurer
f7a19d330c
[maven-release-plugin] prepare release netty-4.1.11.Final
2017-05-11 16:00:16 +02:00
Norman Maurer
6915ec3bb9
[maven-release-plugin] prepare for next development iteration
2017-04-29 14:10:00 +02:00
Norman Maurer
f30f242fee
[maven-release-plugin] prepare release netty-4.1.10.Final
2017-04-29 14:09:32 +02:00
Norman Maurer
2b8c8e0805
[maven-release-plugin] prepare for next development iteration
2017-03-10 07:46:17 +01:00
Norman Maurer
1db58ea980
[maven-release-plugin] prepare release netty-4.1.9.Final
2017-03-10 07:45:28 +01:00
Norman Maurer
c5324ea48c
Make netty build work on Java9
...
Motivation:
We missed some stuff in 5728e0eb2c
and so the build failed on java9
Modifications:
- Add extra cmdline args when needed
- skip the autobahntestsuite as jython not works with java9
- skip the osgi testsuite as the maven plugin not works with java9
Result:
Build finally passed on java9
2017-02-16 20:26:30 +01:00
Norman Maurer
735d6dd636
[maven-release-plugin] prepare for next development iteration
2017-01-30 15:14:02 +01:00
Norman Maurer
76e22e63f3
[maven-release-plugin] prepare release netty-4.1.8.Final
2017-01-30 15:12:36 +01:00
Norman Maurer
7f01da8d0f
[maven-release-plugin] prepare for next development iteration
2017-01-12 11:36:51 +01:00
Norman Maurer
7a21eb1178
[maven-release-plugin] prepare release netty-4.1.7.Final
2017-01-12 11:35:58 +01:00
Norman Maurer
5f533b7358
[maven-release-plugin] prepare for next development iteration
2016-10-14 13:20:41 +02:00
Norman Maurer
35fb0babe2
[maven-release-plugin] prepare release netty-4.1.6.Final
2016-10-14 12:47:19 +02:00
Norman Maurer
54b1a100f4
[maven-release-plugin] prepare for next development iteration
2016-08-26 10:06:32 +02:00
Norman Maurer
1208b90f57
[maven-release-plugin] prepare release netty-4.1.5.Final
2016-08-26 04:59:35 +02:00
Norman Maurer
cb7cf4491c
[maven-release-plugin] prepare for next development iteration
2016-07-27 13:29:56 +02:00
Norman Maurer
9466b32d05
[maven-release-plugin] prepare release netty-4.1.4.Final
2016-07-27 13:16:59 +02:00
Norman Maurer
047f6aed28
[maven-release-plugin] prepare for next development iteration
2016-07-15 09:09:13 +02:00
Norman Maurer
b2adea87a0
[maven-release-plugin] prepare release netty-4.1.3.Final
2016-07-15 09:08:53 +02:00
Norman Maurer
4676a2271c
[maven-release-plugin] prepare for next development iteration
2016-07-01 10:33:32 +02:00
Norman Maurer
ad270c02b9
[maven-release-plugin] prepare release netty-4.1.2.Final
2016-07-01 09:07:40 +02:00
Guido Medina
f0a5ee068f
Update dependencies and plugins to latest possible versions.
...
Motivation:
It is good to have used dependencies and plugins up-to-date to fix any undiscovered bug fixed by the authors.
Modification:
Scanned dependencies and plugins and carefully updated one by one.
Result:
Dependencies and plugins are up-to-date.
2016-06-27 13:35:35 +02:00
Norman Maurer
4dec7f11b7
[maven-release-plugin] prepare for next development iteration
2016-06-07 18:52:34 +02:00
Norman Maurer
cf670fab75
[maven-release-plugin] prepare release netty-4.1.1.Final
2016-06-07 18:52:22 +02:00
Norman Maurer
6ca49d1336
[maven-release-plugin] prepare for next development iteration
2016-05-25 19:16:44 +02:00
Norman Maurer
446b38db52
[maven-release-plugin] prepare release netty-4.1.0.Final
2016-05-25 19:14:15 +02:00
Norman Maurer
572bdfb494
[maven-release-plugin] prepare for next development iteration
2016-04-10 08:37:18 +02:00
Norman Maurer
c6121a6f49
[maven-release-plugin] prepare release netty-4.1.0.CR7
2016-04-10 08:36:56 +02:00
Norman Maurer
6e919f70f8
[maven-release-plugin] rollback the release of netty-4.1.0.CR7
2016-04-09 22:13:44 +02:00
Norman Maurer
4cdd51509a
[maven-release-plugin] prepare release netty-4.1.0.CR7
2016-04-09 22:05:34 +02:00
Trustin Lee
3b941c2a7c
[maven-release-plugin] prepare for next development iteration
2016-04-02 01:25:05 -04:00
Trustin Lee
7368ccc539
[maven-release-plugin] prepare release netty-4.1.0.CR6
2016-04-02 01:24:55 -04:00
Norman Maurer
cee38ed2b6
[maven-release-plugin] prepare for next development iteration
2016-03-29 16:45:13 +02:00
Norman Maurer
9cd9e7daeb
[maven-release-plugin] prepare release netty-4.1.0.CR5
2016-03-29 16:44:33 +02:00
Norman Maurer
28d03adbfe
[maven-release-plugin] prepare for next development iteration
2016-03-21 11:51:50 +01:00
Norman Maurer
4653dc1d05
[maven-release-plugin] prepare release netty-4.1.0.CR4
2016-03-21 11:51:12 +01:00
Xiaoyan Lin
4a5e484c5a
Add xml-maven-plugin to check indentation and fix violations
...
Motivation:
See https://github.com/netty/netty-build/issues/5
Modifications:
Add xml-maven-plugin to check indentation and fix violations
Result:
pom.xml will be checked in the PR build
2016-02-29 09:46:32 +01:00
Norman Maurer
ca443e42e0
[maven-release-plugin] prepare for next development iteration
2016-02-19 23:00:11 +01:00
Norman Maurer
f39eb9a6b2
[maven-release-plugin] prepare release netty-4.1.0.CR3
2016-02-19 22:59:52 +01:00
Norman Maurer
75a2ddd61c
[maven-release-plugin] prepare for next development iteration
2016-02-04 16:51:44 +01:00
Norman Maurer
7eb3a60dba
[maven-release-plugin] prepare release netty-4.1.0.CR2
2016-02-04 16:37:06 +01:00
Norman Maurer
1c417e5f82
[maven-release-plugin] prepare for next development iteration
2016-01-21 15:35:55 +01:00
Norman Maurer
c681a40a78
[maven-release-plugin] prepare release netty-4.1.0.CR1
2016-01-21 15:28:21 +01:00
Norman Maurer
2ecce8fa56
[maven-release-plugin] prepare for next development iteration
2015-11-10 22:59:33 +01:00
Norman Maurer
6a93f331d3
[maven-release-plugin] prepare release netty-4.1.0.Beta8
2015-11-10 22:50:57 +01:00
Norman Maurer
2ff2806ada
[maven-release-plugin] prepare for next development iteration
2015-10-02 09:03:29 +02:00
Norman Maurer
5a43de10f7
[maven-release-plugin] prepare release netty-4.1.0.Beta7
2015-10-02 09:02:58 +02:00
Norman Maurer
34de2667c7
[maven-release-plugin] prepare for next development iteration
2015-09-02 11:45:20 +02:00
Norman Maurer
2eb444ec1d
[maven-release-plugin] prepare release netty-4.1.0.Beta6
2015-09-02 11:36:11 +02:00
Trustin Lee
cfd7b391c8
Add a property to disable osgi testsuite run
2015-08-13 09:53:26 +09:00
Norman Maurer
f23b7b4efd
[maven-release-plugin] prepare for next development iteration
2015-05-07 14:21:08 -04:00
Norman Maurer
871ce43b1f
[maven-release-plugin] prepare release netty-4.1.0.Beta5
2015-05-07 14:20:38 -04:00
Norman Maurer
fce0989844
[maven-release-plugin] prepare for next development iteration
2015-03-03 02:06:47 -05:00
Norman Maurer
ca3b1bc4b7
[maven-release-plugin] prepare release netty-4.1.0.Beta4
2015-03-03 02:05:52 -05:00
Robert Varga
fa64625522
Add a pax-exam based OSGi test suite
...
Motivation:
Release 4.0.25 was not usable in OSGi environments due to a simple typo.
An automated test could have caught the problem even before it was
committed.
Modifications:
This patch introduces a new artifact, osgitests, which pulls in all
production artifacts (which we want to be checked for OSGi compliance).
It contains only a single unit test, which runs a pax-exam container
with felix OSGi.
At initialization time, it scans all the artifact's dependencies,
looking for things belonging to io.netty group. The container is
configured to deploy those artifacts as bundles and fail if any bundle
is found to be unresolved. It performs a final check to see if any
bundles were tested this way, to make sure the mechanism is not
completely broken.
We are using wrappedBundle(), as two of our third-party dependencies do
not export packages correctly -- this masks the problem, assuming that
whoever deploys our artifacts depending on them will figure out how to
OSGify them.
Result:
Simple typos and other bundle manifest errors should be caught during
test phase of every build.
2015-02-18 16:00:15 +01:00
Trustin Lee
407f0a36f5
Simplify bundle generation / Add io.netty.versions.properties to all JARs
...
- Fixes #2003 properly
- Instead of using 'bundle' packaging, use 'jar' packaging. This is
more robust because some strict build tools fail to retrieve the
artifacts from a Maven repository unless their packaging is not 'jar'.
- All artifacts now contain META-INF/io.netty.version.properties, which
provides the detailed information about the build and repository.
- Removed OSGi testsuite temporarily because it gives false errors
during split package test and examination.
- Add io.netty.util.Version for easy retrieval of version information
2013-11-26 22:01:46 +09:00
Norman Maurer
db78581bbb
[maven-release-plugin] prepare for next development iteration
2013-11-07 18:11:45 +01:00
Norman Maurer
2386777af8
[maven-release-plugin] prepare release netty-4.0.12.Final
2013-11-07 18:11:38 +01:00
Norman Maurer
ceab146b54
[maven-release-plugin] prepare for next development iteration
2013-10-21 07:43:42 +02:00
Norman Maurer
27a89d6032
[maven-release-plugin] prepare release netty-4.0.11.Final
2013-10-21 07:41:49 +02:00
Norman Maurer
d7da19f745
[maven-release-plugin] prepare for next development iteration
2013-10-02 15:48:52 +02:00