On Tue, May 8, 2012 at 11:07 AM, Prabath Abeysekera <[email protected]>wrote:
> Hi Sameera, > > On Tue, May 8, 2012 at 10:55 AM, Sameera Jayasoma <[email protected]>wrote: > >> Hi Dileepa, >> >> The idea here is to install a particular category onto a Carbon server >> right?. e.g. Installing AS category onto Carbon would result in an WSO2 >> Application Server. >> >> If thats the case, we need to add more features to these categories. >> > >> > All products contains logging feature, system statistics, etc. >> > > Would it make sense to introduce a common feature category containing all > such features (such as logging, etc) that are there in every product? I > believe that would make the profiles less redundant too. > This is a good suggestion. But the problem is, we don't support sub-categories yet. So for the moment, we have go with former approach. Thanks, Sameera. > > > >> You can find the complete list of features which makes a products by >> looking at the pom.xml of the p2-profile-gen module of a product. >> >> Thanks, >> Sameera. >> >> On Mon, May 7, 2012 at 6:19 PM, Dileepa Jayakody <[email protected]>wrote: >> >>> Hi All, >>> >>> When improving the kernel feature manager to accommodate >>> feature-groups(categories), we grouped some features in >>> platform/trunk/features/repository into sample categories for demo purposes. >>> Primarily the grouping was done based on product level categorisation, >>> so that the users can easily identify and install products on carbon server. >>> >>> I think this sample list can be improved as the actual list of feature >>> categories in Carbon platform. So please add missing features to relevant >>> categories or introduce new categories as appropriate. Please note that a >>> feature may belong to 1 or many categories. >>> >>> *AS* >>> >>> - org.wso2.carbon.jarservices >>> - org.wso2.carbon.jaxwsservices >>> - org.wso2.carbon.repomanager.axis2 >>> - org.wso2.carbon.security.mgt >>> - org.wso2.carbon.service.mgt >>> - org.wso2.carbon.servicehosting >>> - org.wso2.carbon.springservices >>> - org.wso2.carbon.webapp.mgt >>> >>> *BAM * >>> >>> - org.wso2.carbon.bam.data.publisher.activity.mediation >>> - org.wso2.carbon.bam.data.publisher.activity.service >>> - org.wso2.carbon.bam.data.publisher.mediationstats >>> - org.wso2.carbon.bam.data.publisher.servicestats >>> - org.wso2.carbon.bam >>> >>> *Data* >>> >>> - org.wso2.carbon.dataservices >>> - org.wso2.carbon.datasource >>> >>> *ESB* >>> >>> - org.wso2.carbon.deployment.synchronizer >>> - org.wso2.carbon.endpoint >>> - org.wso2.carbon.esb.mediation >>> - org.wso2.carbon.localentry >>> - org.wso2.carbon.mediation.artifactuploader >>> - org.wso2.carbon.mediation.configadmin >>> - org.wso2.carbon.mediation.initializer >>> - org.wso2.carbon.mediation.statistics >>> - org.wso2.carbon.mediation.templates >>> - org.wso2.carbon.mediation.tracer >>> - org.wso2.carbon.message.flows >>> - org.wso2.carbon.message.processor >>> - org.wso2.carbon.message.store >>> - org.wso2.carbon.messagebox >>> - org.wso2.carbon.priority >>> - org.wso2.carbon.proxyadmin >>> - org.wso2.carbon.rest.api >>> - org.wso2.carbon.sequences >>> - org.wso2.carbon.smooks >>> - org.wso2.carbon.statistics.transport >>> - org.wso2.carbon.transport.mgt >>> >>> * IS* >>> >>> - org.wso2.carbon.directory.service.mgr >>> - org.wso2.carbon.identity.authenticator.saml2.sso >>> - org.wso2.carbon.identity.authenticator.token >>> - org.wso2.carbon.identity.core >>> - org.wso2.carbon.identity.oauth >>> - org.wso2.carbon.identity.provider.openid.admin >>> - org.wso2.carbon.identity.provider >>> - org.wso2.carbon.identity.relying.party >>> - org.wso2.carbon.identity.self.registration >>> - org.wso2.carbon.identity.sso.saml >>> - org.wso2.carbon.identity.user.profile >>> - org.wso2.carbon.identity.xacml >>> - org.wso2.carbon.ldap.server >>> >>> *Registry* >>> >>> - org.wso2.carbon.governance.gadgets >>> - org.wso2.carbon.governance.lifecycle.management >>> - org.wso2.carbon.governance.metadata >>> - org.wso2.carbon.governance.notifications.configuration >>> - org.wso2.carbon.registry.activities >>> - org.wso2.carbon.registry.associations.dependencies >>> - org.wso2.carbon.registry.community.features >>> - org.wso2.carbon.registry.contentsearch >>> - org.wso2.carbon.registry.core >>> - org.wso2.carbon.registry.extensions >>> - org.wso2.carbon.registry.handler.configuration >>> - org.wso2.carbon.registry.profiles >>> - org.wso2.carbon.registry.resource.properties >>> - org.wso2.carbon.registry.social >>> - org.wso2.carbon.registry.ui.menu.governance >>> - org.wso2.carbon.registry.ui.menu >>> - org.wso2.carbon.registry.ws >>> >>> *Tools* >>> >>> - org.wso2.carbon.tryit >>> - org.wso2.carbon.wsdl.tools >>> >>> Thanks, >>> >>> Dileepa >>> On Wed, May 2, 2012 at 4:26 PM, Chethiya Abeysinghe >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> We have changed the p2-repo-gen to generate the repository with >>>> category information. So you can simply define categories and include >>>> appropriate features into those categories. Once that repo with category >>>> information is imported to the feature manger, you can see those defined >>>> categories in the UI. >>>> >>>> To feed in these information, you have to edit the >>>> carbon/platform/trunk/features/repository/pom.xml file in svn by adding >>>> <categories> element. An example of such a category is shown below. You can >>>> include multiple <category> elements. >>>> >>>> <categories> >>>> <category> >>>> <id>org.wso2.carbon.broker.category</id> >>>> <label>WSO2 Broker Category</label> >>>> <description>broker category</description> >>>> >>>> <features> >>>> <catFeature> >>>> <id>org.wso2.carbon.broker</id> >>>> <version>${carbon.version}</version> >>>> </catFeature> >>>> >>>> <catFeature> >>>> <id>org.wso2.carbon.brokermanager</id> >>>> <version>${carbon.version}</version> >>>> </catFeature> >>>> </features> >>>> </category> >>>> </categories> >>>> >>>> Please note that, <id> and <version> are required to include a feature >>>> to a category. <id> is the same ID used with p2-feature-gen goal of the >>>> carbon-p2-plugin. You can find that if you look at the pom.xml of any >>>> particular feature you want. >>>> >>>> A sample pom.xml file to reside in repository folder is attached here. >>>> >>>> Real pom file has a long list of features and hope people who are >>>> managing individual features will insert their respective category >>>> information also to this file. >>>> >>>> Thanks, >>>> >>>> -- >>>> Chethiya Abeysinghe >>>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>>> email: [email protected] phone: +94 777444891 >>>> blog: chethiya3000.blogspot.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Dileepa Jayakody, >>> Software Engineer, WSO2 Inc. >>> >>> Lean . Enterprise . Middleware >>> >>> Mobile : +94777-857616 >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sameera Jayasoma >> Technical Lead >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://tech.jayasoma.org >> >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Prabath Abeysekara > Software Engineer > WSO2 Inc. > Email: [email protected] <[email protected]> > Mobile: +94774171471 > > <http://harshana05.blogspot.com/> > > -- Sameera Jayasoma Technical Lead WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://tech.jayasoma.org Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
