Remoting5 integration #30
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tadamski
force-pushed
the
remoting5_integration
branch
from
d287116 to
9a11df5
Compare
|
Discussed some compilation issues with @tadamski and found that building this depends on the following PRs: wildfly/wildfly-transaction-client#1 |
|
After updating jboss-ejb-client to the HEAD new smoke test errors appeared: |
|
There also also quite a few references to the client inside basic integration testsuite - looking about it currently. |
|
Closing this one since it's been superseded by #44. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merged my ejb3 subsystem work into remoting5_integration branch. Have to update wildfly-naming-client for the smoke tests to work.