Another merge of 4.x to 5.0#6104
Conversation
Signed-off-by: Maxim Nesen <senivam@gmail.com>
[5.0] Exclude jersey-constants from the release test
…_dependencies Update deps to EE12 and fix code for it
Skip publishing patched modules
Update several versions
Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
- M1 depended on snapshot parent Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
- M1 depended on snapshot parent Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
…cies Updated Grizzly dependencies - fixed jpms
Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
Fixed schemaLocation for poms for 5.0
* eclipse/4.x: Fixed schemaLocation for poms resolve null @context in Spring-proxied Jersey resources (eclipse-ee4j#6080) Exclude jersey-constants from the release test Removed ReaderWriter::readAllBytes (eclipse-ee4j#6070) Fix memory leak (eclipse-ee4j#6075) InputStream.nullInputStream() and Reader.nullWriter() is more efficient than new ByteInputStream(new byte[0]) and new Reader(...(new byte[0]));
Merge of 4.0 changes to 5.0
# By David Matějček (8) and others # Via GitHub (6) and David Matějček (2) * eclipse/4.x: Updated HK2 from a milestone to 4.0.1 Removed supplier from log Added test from PR eclipse-ee4j#6086 Removed redundant surefire plugin without a version from helidon3-client Removed CompletedAsyncContextListener which redundantly completed processing Added logging of the redundant completition New test for AsyncContextDelegateProviderImpl Bump org.assertj:assertj-core from 3.21.0 to 3.27.7 Issue 6036; Media - Jackson3 Fixed schemaLocation for poms Fix memory leak (eclipse-ee4j#6075) # Conflicts: # NOTICE.md # etc/config/copyright-exclude # pom.xml
|
IIUC then you simply merge 4.x into 5.0, right? In that case, I am +1. As 5.0 is a development branch, maybe it is simpler to rebase it on 4.x? 🤔 |
Rebases are bit dangerous with shared branches, first you cut out all PRs, because rebase reapplies commits. All commits change ids, so also links to them would be lost. Merges are safer and more consistent. When we would keep this from time to time, we resolve conflicts, fix some differences, we can have less work with backports. However 2.x and 3.0 are already more problematic, I don't plan to spend my time with these branches. Also, sometimes conflicts point on some problems to resolve. |
Local build: