Hi Niranjan, It was failing with the p2 repo that is created in p2-profile-gen. Looking at the pom at [1], this feature only imports the org.wso2.carbon.core which is available in IS but as a different patch release version. Does the difference in the patch release version matter here? Or is it due to something else?
[1] https://github.com/wso2/carbon-analytics-common/blob/v5.0.11/features/event-publisher/org.wso2.carbon.event.publisher.aggregate.feature/pom.xml On Fri, May 20, 2016 at 2:10 PM, Niranjan Karunanandham <[email protected]> wrote: > Hi Pulasthi, > > When building the product, are you referring to the p2-repo of the locally > built carbon-feature-repository or to a p2-repo that you create in > p2-profile-gen. If so this issue can happen if the feature that you are > installing has import features which are not there in your p2-repo. > > @Malith: As per the previous mail, can you close this PR since it need to > come from the PR from the product team which will be using the feature. > > Regards, > Nira > > Regards, > Nira > > On Fri, May 20, 2016 at 12:47 PM, Pulasthi Mahawithana <[email protected] > > wrote: > >> I tried to add this feature to product-is 's p2-profile-gen. But it fails >> saying, >> >> Installation failed. >> The installable unit >> org.wso2.carbon.event.publisher.aggregate.feature.group/5.0.11 has not been >> found. >> >> However I can install it from feature management UI when I merged and >> built the carbon feature repository locally with the PR at [1] and point >> that as a local repository. Any possible causes for this? >> >> [1] https://github.com/wso2/carbon-feature-repository/pull/46 >> >> On Wed, Apr 27, 2016 at 9:08 AM, Niranjan Karunanandham < >> [email protected]> wrote: >> >>> Hi Malith, >>> >>> Since this feature will be included in the next ESB release, IMO it >>> would be better to close the current PR and have it included in the same PR >>> after the product release. >>> >>> Regards, >>> Nira >>> >>> On Mon, Apr 25, 2016 at 6:05 PM, Malith Dhanushka <[email protected]> >>> wrote: >>> >>>> Hi Niranjan, >>>> >>>> Correction on my previous reply. we have to ship this feature by >>>> default with ESB and APIM. So this needs to be released with the immediate >>>> ESB or APIM release. >>>> >>>> @Viraj - Please include this feature in next ESB release. I have >>>> already sent a pull request by including this to carbon-feature-repository. >>>> >>>> Thanks, >>>> Malith >>>> >>>> On Mon, Apr 25, 2016 at 5:44 PM, Malith Dhanushka <[email protected]> >>>> wrote: >>>> >>>>> Hi Niranjan, >>>>> >>>>> Since this feature doesn't ship by default in any of the products, >>>>> please go ahead and merge this as an special case. >>>>> >>>>> Thanks, >>>>> Malith >>>>> >>>>> On Tue, Apr 12, 2016 at 10:56 AM, Niranjan Karunanandham < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Malith, >>>>>> >>>>>> On Fri, Mar 18, 2016 at 11:42 AM, Malith Dhanushka <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Mar 18, 2016 at 11:38 AM, Kishanthan Thangarajah < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> This new change is only for OSGi based servers in the platform >>>>>>>> right? Are there any changes for standalone data publishing API's used >>>>>>>> with >>>>>>>> non-OSGi servers in the platform or is it still the same as before? We >>>>>>>> have >>>>>>>> AS 6.0.0 which is based on pure tomcat and currently we are using the >>>>>>>> minimum required data publishing libs and the standalone data >>>>>>>> publishing >>>>>>>> API's to publish HTTP stats to DAS. >>>>>>>> >>>>>>> >>>>>>> Yes this new change is only for OSGi based servers and no change in >>>>>>> standalone data publishing API's. >>>>>>> >>>>>>> >>>>>>>> On Mon, Mar 14, 2016 at 4:51 PM, Malith Dhanushka <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> Please follow the steps bellow when publishing events from carbon >>>>>>>>> servers to DAS/CEP. Here we keep the DAS/CEP server location in >>>>>>>>> CARBON_HOME/repository/deployment/server/eventpublishers directory >>>>>>>>> and this >>>>>>>>> is common across platform. >>>>>>>>> >>>>>>>>> - Install the Event Publisher Aggregate feature from p2_repo [1] >>>>>>>>> >>>>>>>>> - Install Registry Core feature if not installed >>>>>>>>> >>>>>>>>> - Create event stream and deploy that to >>>>>>>>> CARBON_HOME/repository/deployment/server/eventstreams >>>>>>>>> >>>>>>>>> - Create publishers for the created stream and deploy that to >>>>>>>>> CARBON_HOME/repository/deployment/server/eventpublishers >>>>>>>>> Following is a sample configuration, >>>>>>>>> >>>>>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>>>>> <eventPublisher name="pubTest" statistics="disable" >>>>>>>>> trace="disable" xmlns="http://wso2.org/carbon/eventpublisher";> >>>>>>>>> <from streamName="streamTest" version="1.0.0"/> >>>>>>>>> <mapping customMapping="disable" type="wso2event"/> >>>>>>>>> <to eventAdapterType="wso2event"> >>>>>>>>> <property name="username">admin</property> >>>>>>>>> <property name="protocol">thrift</property> >>>>>>>>> <property name="publishingMode">non-blocking</property> >>>>>>>>> <property name="publishTimeout">0</property> >>>>>>>>> <property name="receiverURL">tcp://localhost:7611</property> >>>>>>>>> <property encrypted="true" name="password">XXXXXXXXX</property> >>>>>>>>> </to> >>>>>>>>> </eventPublisher> >>>>>>>>> >>>>>>>>> - Publish events to the created stream using >>>>>>>>> org.wso2.carbon.event.stream.core.EventStreamService OSGI service. >>>>>>>>> Following is a sample code snippet. >>>>>>>>> >>>>>>>>> Event event = new Event(); >>>>>>>>> event.setTimeStamp(System.currentTimeMillis()); >>>>>>>>> event.setStreamId("streamTest:1.0.0"); >>>>>>>>> event.setPayloadData(new Object[]{data}); >>>>>>>>> eventStreamService.publish(event); >>>>>>>>> >>>>>>>>> Please note that Event Publisher Aggregate feature is not yet >>>>>>>>> included in carbon feature repo. It will be available with the >>>>>>>>> immediate >>>>>>>>> analytics feature release. >>>>>>>>> >>>>>>>> Usually features are added to the p2-repo >>>>>> (carbon-feature-repository repo) when products are released. The product >>>>>> team has to send a PR of all the features they are using in the product >>>>>> (from the p2-profile-gen pom). Therefore this feature should come from >>>>>> the >>>>>> PR from the products which are using this feature when the product is >>>>>> released. >>>>>> >>>>>> >>>>>>> >>>>>>>>> [1] >>>>>>>>> https://github.com/wso2/carbon-analytics-common/tree/master/features/event-publisher/org.wso2.carbon.event.publisher.aggregate.feature >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Malith >>>>>>>>> -- >>>>>>>>> Malith Dhanushka >>>>>>>>> Senior Software Engineer - Data Technologies >>>>>>>>> *WSO2, Inc. : wso2.com <http://wso2.com/>* >>>>>>>>> *Mobile* : +94 716 506 693 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Dev mailing list >>>>>>>>> [email protected] >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Kishanthan Thangarajah* >>>>>>>> Associate Technical Lead, >>>>>>>> Platform Technologies Team, >>>>>>>> WSO2, Inc. >>>>>>>> lean.enterprise.middleware >>>>>>>> >>>>>>>> Mobile - +94773426635 >>>>>>>> Blog - *http://kishanthan.wordpress.com >>>>>>>> <http://kishanthan.wordpress.com>* >>>>>>>> Twitter - *http://twitter.com/kishanthan >>>>>>>> <http://twitter.com/kishanthan>* >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Malith Dhanushka >>>>>>> Senior Software Engineer - Data Technologies >>>>>>> *WSO2, Inc. : wso2.com <http://wso2.com/>* >>>>>>> *Mobile* : +94 716 506 693 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> Regards, >>>>>> Nira >>>>>> >>>>>> -- >>>>>> >>>>>> *Niranjan Karunanandham* >>>>>> Senior Software Engineer - WSO2 Inc. >>>>>> WSO2 Inc.: http://www.wso2.com >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Malith Dhanushka >>>>> Senior Software Engineer - Data Technologies >>>>> *WSO2, Inc. : wso2.com <http://wso2.com/>* >>>>> *Mobile* : +94 716 506 693 >>>>> >>>> >>>> >>>> >>>> -- >>>> Malith Dhanushka >>>> Senior Software Engineer - Data Technologies >>>> *WSO2, Inc. : wso2.com <http://wso2.com/>* >>>> *Mobile* : +94 716 506 693 >>>> >>> >>> >>> >>> -- >>> >>> *Niranjan Karunanandham* >>> Senior Software Engineer - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Pulasthi Mahawithana* >> Software Engineer >> WSO2 Inc., http://wso2.com/ >> Mobile: +94-71-5179022 >> Blog: http://blog.pulasthi.org >> > > > > -- > > *Niranjan Karunanandham* > Senior Software Engineer - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > -- *Pulasthi Mahawithana* Software Engineer WSO2 Inc., http://wso2.com/ Mobile: +94-71-5179022 Blog: http://blog.pulasthi.org
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
