Hi all, Thanks for the quick turnaround and releasing the required repo quickly. Appreciate your support very much!
Unfortunately, it seems the jaggery-extensions-1.4.1 is still packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. Please see the artifact packed inside the plugins folder in the zip at [1]. Can you check why the old version is still getting packed and provide a release with the fixes? I think there is an issue in how the wss4j dependency has been specified. It is not there in the dependencyManagement section of the top level pom, but has been specified as a dependency without versions in child level poms. Also I could not find any place where the 'wss4j.osgi.version' seems to be used. Can you check on these issues and fix it so that the proper jar is packed if needed (or drop the jar altogether from the feature if possible) ? [1] http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/ Thanks, Lasantha On 10 September 2015 at 19:58, KasunG Gajasinghe <[email protected]> wrote: > > Released the repo from staging. > > On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena <[email protected]> > wrote: > >> Hi all, >> >> We have prepared the release steps for jagggery-extensions 1.4.1. >> Builder team please close the repo and release jagggery-extensions 1.4.1. >> >> Thanks! >> -Chanaka >> >> On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando <[email protected]> >> wrote: >> >>> Hi Manu, UES team, >>> >>> It seems this is fixed in jaggery 0.11.0. If we move our dashboard >>> dependency version from 0.10.3 to 0.11.0, will this affect our current >>> dashboard functionality? (Any API changes, functionality changes of >>> existing features) >>> >>> Also, as per the thread started by KasunG, it seems this issue is there >>> in jaggery-extensions as well. So can we get a release for >>> jaggery-extensions and jaggery (if upgrade does not work) with the proper >>> fix? >>> >>> We are currently planning to put an RC release of CEP tomorrow and >>> currently we are blocked on releasing the dependent repos because of this. >>> Would appreciate a response at your earliest please. >>> >>> Thanks, >>> Lasantha >>> >>> On 10 September 2015 at 15:17, Lasantha Fernando <[email protected]> >>> wrote: >>> >>>> Thanks Harsha anyway for the suggestion.. :-) >>>> >>>> After removing the older wss4j from the bundles.info of the pack as >>>> suggested by Gokul, the pack is starting fine. So I guess we will have to >>>> fix the jaggery features properly to resolve this issue. >>>> >>>> Thanks, >>>> Lasantha >>>> >>>> On 10 September 2015 at 15:03, Harsha Thirimanna <[email protected]> >>>> wrote: >>>> >>>>> Sorry , didn't see your reply. :) >>>>> On Sep 10, 2015 3:02 PM, "Harsha Thirimanna" <[email protected]> wrote: >>>>> >>>>>> Hi Lasantha, >>>>>> >>>>>> Can't we enable logs and check whether which component will take more >>>>>> time >>>>>> OR >>>>>> do profiling to get the root cause. >>>>>> On Sep 10, 2015 2:34 PM, "Gokul Balakrishnan" <[email protected]> wrote: >>>>>> >>>>>>> We're facing the same issue in the later DAS packs, where the pack >>>>>>> startup is much slower after the upgrade. This is apparent under Java 8 >>>>>>> as >>>>>>> well (1.8.0_51). >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> On 10 September 2015 at 14:29, Lasantha Fernando <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Devs, >>>>>>>> >>>>>>>> For product-cep, after upgrading the dependent carbon identity repo >>>>>>>> version from 4.5.5 to 4.5.6, the server startup has become extremely >>>>>>>> slow. >>>>>>>> If you downgrade this particular identity version back to 4.5.5, it >>>>>>>> starts >>>>>>>> normally. >>>>>>>> >>>>>>>> The difference is from around 24-30 sec startup time with identity >>>>>>>> 4.5.5 and 70-80 sec startup time for identity 4.5.6 with no other >>>>>>>> changes. >>>>>>>> >>>>>>>> In the OSGi console, all bundles are active and all our WSO2 OSGi >>>>>>>> services are also active for both packs. >>>>>>>> >>>>>>>> Any idea why this issue is coming up? A similar issue was reported >>>>>>>> in DAS packs as well after they upgraded their dependent repos. >>>>>>>> >>>>>>>> These tests were done with JDK 1.7.0_80. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Lasantha >>>>>>>> >>>>>>>> -- >>>>>>>> *Lasantha Fernando* >>>>>>>> Senior Software Engineer - Data Technologies Team >>>>>>>> WSO2 Inc. http://wso2.com >>>>>>>> >>>>>>>> email: [email protected] >>>>>>>> mobile: (+94) 71 5247551 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Gokul Balakrishnan >>>>>>> Senior Software Engineer, >>>>>>> WSO2, Inc. http://wso2.com >>>>>>> Mob: +94 77 593 5789 | +1 650 272 9927 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>> >>>> >>>> -- >>>> *Lasantha Fernando* >>>> Senior Software Engineer - Data Technologies Team >>>> WSO2 Inc. http://wso2.com >>>> >>>> email: [email protected] >>>> mobile: (+94) 71 5247551 >>>> >>> >>> >>> >>> -- >>> *Lasantha Fernando* >>> Senior Software Engineer - Data Technologies Team >>> WSO2 Inc. http://wso2.com >>> >>> email: [email protected] >>> mobile: (+94) 71 5247551 >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Chanaka Jayasena >> Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: [email protected]; cell: +94 77 785 5565 >> blog: http://chanaka3d.blogspot.com >> > > > > -- > > *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > > -- *Lasantha Fernando* Senior Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: [email protected] mobile: (+94) 71 5247551
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
