Hi,
In MB 3.0 alpha pack I can see that there is a new file called
metrics-datasources.xml. All kernel and carbon component level data
sources are defined in masterdatasource.xml. On top of that, any valid
reason for this to move to a separate file. If this fact already raised in
an old
Hi All,
Since we have not released a single product with Carbon 4.4.X version, we
need to think about creating a P2 repository for the products which are
going to be released with the same carbon version. What should be the
methodology to create a P2 repository for ESB 4.9.0 version which is
Hi Chanaka,
For the p2 repo, we already have the carbon-feature-repository [1], which
will have all the features in the main pom.xml. We had a review [2] with
regard to this and during the review it was suggested whether we need to
have the nested-categories within the product or should it be
Hi All,
Currently we are working on a feature that will enable to develop, deploy
and manage CAR files via App Factory. As the first part of this I started
working on CAR application type and the ESB runtime.
In this phase the expectation is to
1.
Create an car type multi module
Hi All,
While working with the previous deployment (See the attached image in
previous replies) I came across a blocker as follows:
-
Since we have isolated SM from Docker containers by having separate
user-stores and governance registries, the tenant created in AF side will
be seen
