-
Notifications
You must be signed in to change notification settings - Fork 693
Geode 8461 - Add ModuleServerLauncher #5734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…les. (apache#5234) JBossModuleServiceImpl can now register and load Modules using ModuleDescriptor. The ModuleDescriptor can now contain source paths to be included in the module as code sources or have dependencies on other modules. The same functionality can now be represented/retrieved from the Manifest file contained within the jar files. Amended gradle scripts for geode-common-services and geode-common to now generate manifest files containing "Class-Path" dependencies and project module dependencies described in the "Dependent-Modules" attribute in the manifest file.
…ules' attirbutes to manifest file. (apache#5297) GEODE-8043 - Create JBossModuleService and implement loadModule. (apache#5081) GEODE-8294 - Integrate ModuleService into Geode. Integrated ModuleService into geode-membership. Integrate ModuleService into geode-cq. Integrate ModuleService into WAnServiceProvider Integrate ModuleService into ServerConnectionfactory. Integrate ModuleService into ListCollectingServiceLoader and InternalDistributedSystemMetricsService. Integrate ModuleService into HandshakeRequestOperationHandler and ValueSerializer Integrate ModuleService into CacheXml. Integrate ModuleService into CommandManager. Cleaned up library dependencies Moved BootstrappingService.java to geode-common-services Integrate ModuleService into tests and comments.. GEODE-8306 - Introduce GeodeEntityResolver2Interface.
* Added ComponentIdentifier and ComponentManagementService * Amended BootstrappingServiceImpl to use ComponentIdentifier * ManagementService delegates to Bootstrapping set up ENV before loading the ComponentManagementService to create the component
…ntManagementService to load Geode Log4j implementation from a the known log4j2.xml file, stored within geode-log4j
…ules' attirbutes to manifest file. (apache#5297) GEODE-8043 - Create JBossModuleService and implement loadModule. (apache#5081) GEODE-8294 - Integrate ModuleService into Geode. Integrated ModuleService into geode-membership. Integrate ModuleService into geode-cq. Integrate ModuleService into WAnServiceProvider Integrate ModuleService into ServerConnectionfactory. Integrate ModuleService into ListCollectingServiceLoader and InternalDistributedSystemMetricsService. Integrate ModuleService into HandshakeRequestOperationHandler and ValueSerializer Integrate ModuleService into CacheXml. Integrate ModuleService into CommandManager. Cleaned up library dependencies Moved BootstrappingService.java to geode-common-services Integrate ModuleService into tests and comments.. GEODE-8306 - Introduce GeodeEntityResolver2Interface.
* Added ComponentIdentifier and ComponentManagementService * Amended BootstrappingServiceImpl to use ComponentIdentifier * ManagementService delegates to Bootstrapping set up ENV before loading the ComponentManagementService to create the component
…les. (apache#5234) JBossModuleServiceImpl can now register and load Modules using ModuleDescriptor. The ModuleDescriptor can now contain source paths to be included in the module as code sources or have dependencies on other modules. The same functionality can now be represented/retrieved from the Manifest file contained within the jar files. Amended gradle scripts for geode-common-services and geode-common to now generate manifest files containing "Class-Path" dependencies and project module dependencies described in the "Dependent-Modules" attribute in the manifest file.
…ules' attirbutes to manifest file. (apache#5297) GEODE-8043 - Create JBossModuleService and implement loadModule. (apache#5081) GEODE-8294 - Integrate ModuleService into Geode. Integrated ModuleService into geode-membership. Integrate ModuleService into geode-cq. Integrate ModuleService into WAnServiceProvider Integrate ModuleService into ServerConnectionfactory. Integrate ModuleService into ListCollectingServiceLoader and InternalDistributedSystemMetricsService. Integrate ModuleService into HandshakeRequestOperationHandler and ValueSerializer Integrate ModuleService into CacheXml. Integrate ModuleService into CommandManager. Cleaned up library dependencies Moved BootstrappingService.java to geode-common-services Integrate ModuleService into tests and comments.. GEODE-8306 - Introduce GeodeEntityResolver2Interface.
* Added ComponentIdentifier and ComponentManagementService * Amended BootstrappingServiceImpl to use ComponentIdentifier * ManagementService delegates to Bootstrapping set up ENV before loading the ComponentManagementService to create the component
|
This pull request introduces 2 alerts and fixes 2 when merging 47f1d5f into c99087a - view on LGTM.com new alerts:
fixed alerts:
|
|
This pull request introduces 2 alerts and fixes 2 when merging 48d0808 into f23e01a - view on LGTM.com new alerts:
fixed alerts:
|
|
This pull request introduces 2 alerts and fixes 2 when merging b062fbd into f23e01a - view on LGTM.com new alerts:
fixed alerts:
|
|
This PR has been inactive for some while, can it be closed? |
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop)?Is your initial contribution a single, squashed commit?
Does
gradlew buildrun cleanly?Have you written or updated unit tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.