LPS-49118 New API for the cache configurators
LPS-49118 Extract the logic from the hot deployer and create a robust API and implementation which we will reuse within the module framework
LPS-49118 Wire all the stuff through the Spring context. This will allow us to publish the configurator as an OSGi service, so we will be able to consume it from the OSGi container
LPS-49118 Export the new API to the internal modules so we can reuse it within the OSGi container
LPS-49118 Sort
LPS-49118 SF
LPS-48415 - Create a portal-smoke component
LPS-49114 Abstraction to configure the service components independently of the location. It is missing a builder, but for now this should be enough to break the dependency within the Servlet API. A basic implementation backed by a Servlet context is provided
LPS-49114 Remove the dependency within the Servlet API and put our custom abstraction in place
LPS-49114 AUTOGENERATED
LPS-49114 Use the new abstraction
LPS-49114 rename
LPS-49114 rename
LPS-49114 SF
LPS-46155
LPS-46155 SF
LPS-49131 Create a composite bundle so we can make the lookups across a bunch of them. Note this is just a bundle for looking resources (spring xml files) so you cannot use it with different purposes (actually it is marked as internal and all the non-usable method will throw an UnsupportedOperationException)
LPS-49131 Custom OSGi Spring context so we can create the resource loader ourselves
LPS-49131 Use the new application context so we do the lookup of the resources across both bundles (the deployed bundle and the spring extender one)
LPS-49131 Eclipse