Hi Ruwan,

Great. Can we now get carbon-appmgt repository released on top of Carbon
Kernel 4.4.0?

Also, do we have features added upon all app-mgt functionalities so that
they can be installed into other products via P2 feature provisioning?

Cheers,
Prabath

On Wed, Jul 29, 2015 at 12:19 PM, Ruwan Abeykoon <[email protected]> wrote:

> Hi All,
> The branch "carbon-4.4.0-migration" has been merged back to "master" on
> both "carbon-appmgt" and "product-app-manager".
> The "carbon-4.4.0-migration" will be removed soon.
>
> How to build.
>
> 1. Get the enterprise store [1] switch to branch "app-manager". Build it.
> This is needed as the relevant ES version is not released yet.
>
> [1] https://github.com/wso2/product-es
> <https://github.com/wso2/product-es/tree/app-manager>
>
> Cheers,
> Ruwan
>
> On Tue, Jul 21, 2015 at 4:11 PM, Prabath Abeysekera <[email protected]>
> wrote:
>
>> Excellent stuff! Thanks Ruwan!
>>
>> Let me too give it a try and confirm if everything works as expected.
>>
>> Cheers,
>> Prabath
>>
>> On Tue, Jul 21, 2015 at 3:37 PM, Ruwan Abeykoon <[email protected]> wrote:
>>
>>> Hi All,
>>> I am glad to announce that the Carbon 4.4.0 migration along with version
>>> bump up to 1.1.0 (1.1.0-SNAPSHOT) has been done.
>>>
>>> How to build.
>>>
>>> 1. Get the enterprise store [3] switch to branch "app-manager". Build
>>> it. This is needed as the relevant ES version is not released yet.
>>> 2. Get the carbon-appmgt [2] and switch to
>>> branch "carbon-4.4.0-migration". Build it
>>> 3. Get the product-appmanager [1] and switch to branch
>>> "carbon-4.4.0-migration". Build it.
>>> 4. The pack will be generated at
>>> "<product-app-manager>/modules/distribution/product/target/wso2appm-1.1.0-SNAPSHOT.zip".
>>> Unzip and run as normal WSO2 product.
>>>
>>> Known Issues.
>>> 1. The pagination at "Store" shows "Next" link even when there are no
>>> more applications. This is due to change in Registry and need to be fixed
>>> in AppM store.
>>>
>>> [1] https://github.com/wso2/product-app-manager
>>> <https://github.com/wso2/product-app-manager/tree/carbon-4.4.0-migration>
>>> [2] https://github.com/wso2/carbon-appmgt
>>> <https://github.com/wso2/carbon-appmgt/tree/carbon-4.4.0-migration>
>>> [3] https://github.com/wso2/product-es
>>> <https://github.com/wso2/product-es/tree/app-manager>
>>>
>>> Cheers,
>>> Ruwan
>>>
>>>
>>> On Mon, Jul 20, 2015 at 9:57 PM, Prabath Abeysekera <[email protected]>
>>> wrote:
>>>
>>>> Great! Hope the changes can be committed soon so that the CDM team can
>>>> then fully integrate Mobile App Management features and start testing
>>>> things out end-to-end.
>>>>
>>>> Cheers,
>>>> Prabath
>>>>
>>>> On Mon, Jul 20, 2015 at 9:56 AM, Ruwan Abeykoon <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Prabath,
>>>>> The problem is isolated. Issue is having wadl and jaxb jars as
>>>>> bundles. Removing one of the bundles causes the problem disappear.
>>>>> I will work with governance/carbon teams to get a resolution.
>>>>>
>>>>> Cheers,
>>>>> Ruwan
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Jul 18, 2015 at 11:18 AM, Prabath Abeysekera <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Hi Ruwan,
>>>>>>
>>>>>> Did we manage to fix this?
>>>>>>
>>>>>> Cheers,
>>>>>> Prabath
>>>>>>
>>>>>> On Wed, Jul 15, 2015 at 7:54 PM, Ruwan Abeykoon <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>> Yet another update on $subject
>>>>>>> The intermittent classloader issue could not be resolved yet. Here
>>>>>>> are few observations.
>>>>>>>
>>>>>>> The jaggery application calls the CarbonWebappClassloader to lookup
>>>>>>> a class in governance API bundle. This fails.
>>>>>>> However the same class is properly loaded via different bundle (Say
>>>>>>> WebappManagment) classloader which is not initially loaded via
>>>>>>> Tomcat/Jaggary app.
>>>>>>> No issue found in "launch.ini". No apparent conflicting bundles or
>>>>>>> unsatisfied dependencies. There were few duplicate packaged exported by
>>>>>>> different bundles, but seems they are not causing the issue.
>>>>>>>
>>>>>>> I am working with Sameera  to find the underlying cause.
>>>>>>>
>>>>>>> I am unable to create a PR with the version change due to above
>>>>>>> issue.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Ruwan
>>>>>>>
>>>>>>> On Wed, Jul 8, 2015 at 11:28 AM, Ruwan Abeykoon <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Team,
>>>>>>>> I would like to update you on $subject
>>>>>>>>
>>>>>>>> 1. All the module versions are bumped up to 1.1.0-SNAPSHOT
>>>>>>>> 2. Removed all the carbon 4.2.0 and related features which depend
>>>>>>>> on C 4.2.0 and added Carbon 4.4.0 kernel and other features compatible 
>>>>>>>> with
>>>>>>>> Carbon 4.4.0 (registry, governance, mediation, Jaggery, etc).
>>>>>>>> 3. Forked ES for C 4.4.0 version bump up, upgraded the
>>>>>>>> dependencies, Had to change few classes in ES to be able to get it
>>>>>>>> compatible with governance 4.5.1.
>>>>>>>> 4. Changed few classes and jaggery files which needed to be changed
>>>>>>>> due to method signature changes in registry
>>>>>>>> (e.g. GenericArtifact.invokeAction(...)).
>>>>>>>>
>>>>>>>> Current Status with Carbon 4.4.0
>>>>>>>> 1. AppM builds and starts successfully
>>>>>>>> 2. Can create web applications, publish and subscribe.
>>>>>>>>
>>>>>>>> Present Issues which I am working on.
>>>>>>>> 1. Intermittent, Classloader or similar issue in loading
>>>>>>>> org.wso2.carbon.governance.api.generic [1]
>>>>>>>> 2. Need to test most of other areas(mobile apps, policy, throttling)
>>>>>>>> 3. At the moment, update synapse config to the gateway is failing.
>>>>>>>> 4. Clean up the code which had experimental/debug code
>>>>>>>> 5. Remove unwanted/duplicate jaggery modules [2]
>>>>>>>>
>>>>>>>> None of the changes are committed to any public repository yet.
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] Mail thread "[Dev]Class Loading issue in Jaggery, Carbon 4.4.0"
>>>>>>>> [2] Mail thread  "[Dev][AppM] Removing multiple "modules"
>>>>>>>> directories"
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> *Ruwan Abeykoon*
>>>>>>>> *Architect,*
>>>>>>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>>>>>>>> *lean.enterprise.middleware.*
>>>>>>>>
>>>>>>>> email: [email protected]
>>>>>>>> phone:(+94) 777739736
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> *Ruwan Abeykoon*
>>>>>>> *Architect,*
>>>>>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>>>>>>> *lean.enterprise.middleware.*
>>>>>>>
>>>>>>> email: [email protected]
>>>>>>> phone:(+94) 777739736
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Prabath Abeysekara
>>>>>> Technical Lead
>>>>>> WSO2 Inc.
>>>>>> Email: [email protected]
>>>>>> Mobile: +94774171471
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *Ruwan Abeykoon*
>>>>> *Architect,*
>>>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>>>>> *lean.enterprise.middleware.*
>>>>>
>>>>> email: [email protected]
>>>>> phone:(+94) 777739736
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Prabath Abeysekara
>>>> Technical Lead
>>>> WSO2 Inc.
>>>> Email: [email protected]
>>>> Mobile: +94774171471
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Ruwan Abeykoon*
>>> *Architect,*
>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>>> *lean.enterprise.middleware.*
>>>
>>> email: [email protected]
>>> phone:(+94) 777739736
>>>
>>
>>
>>
>> --
>> Prabath Abeysekara
>> Technical Lead
>> WSO2 Inc.
>> Email: [email protected]
>> Mobile: +94774171471
>>
>
>
>
> --
>
> *Ruwan Abeykoon*
> *Architect,*
> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
> *lean.enterprise.middleware.*
>
> email: [email protected]
> phone:(+94) 777739736
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: [email protected]
Mobile: +94774171471
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to