Hi All, Maintaining MB components and features within the product-mb is the right thing to do IMO.
Do we have a real requirement release separate features individually? Thanks, Sameera. On Wed, Feb 10, 2016 at 11:35 AM, Akalanka Pagoda Arachchi < [email protected]> wrote: > To be clear on this, if we have all the features in one repository, > connecting them from the same parent pom, we will not be able release one > feature without releasing the others. > > Therefore, if the requirement is to make these available to be > individually released, we have to logically separate them which ideally > means to have separate repositories per each feature. > > Thanks, > Akalanka. > > On Tue, Feb 9, 2016 at 5:24 PM, Hasitha Hiranya <[email protected]> wrote: > >> Hi Asitha, >> >> Yep. If we install above 4 features on a vanila Cabon server, it should >> become a MB server. >> >> Thanks >> >> On Tue, Feb 9, 2016 at 4:26 PM, Asitha Nanayakkara <[email protected]> >> wrote: >> >>> Adding dev@ >>> >>> On Tue, Feb 9, 2016 at 4:03 PM, Hasitha Hiranya <[email protected]> >>> wrote: >>> >>>> hi Asitha, >>>> >>>> Ah, so there is no need for components be in a separate repo? >>>> I think the reason to keep components in a separate repo was to share >>>> the components between various product level features. >>>> >>>> Agreed, if we want to do a release for a specific feature then we have >>> to release the whole product. If we have a separate repo for features we >>> won't have that issue. At the moment we don't have such requirement. Will >>> this be a valid requriment in future? >>> >>> Even though we are moving all the components and features to product mb >>> repo still we will have four features. Namely they are >>> Andes feature - andes core functionality will be implemented in this >>> feature >>> MB-UI feature - ui components of MB >>> AMQP-feature - AMQP transport implementation >>> MQTT feature - MQTT transport implementation >>> >>> So these features can be used in other products. For instance we can >>> have a lean MB with Andes feature and MQTT feature. >>> >>> Regards, >>> Asitha >>> >>> >>> >>>> Let us use Dev/Architecture mail threads to discuss these. >>>> >>>> Thanks >>>> >>>> On Tue, Feb 9, 2016 at 3:55 PM, Asitha Nanayakkara <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> We (Hemika and I) are in the process of bootstrapping the product. >>>>> >>>>> We have come up with a folder structure for the project[2]. We will be >>>>> working on product-mb/c5-migration branch [1]. >>>>> >>>>> We will be moving all the components and features to product-mb repo >>>>> (since we don't have any shared features in there) and eventually will get >>>>> rid of the cabon-business-messaging repo >>>>> >>>>> Any concerns,thoughts and suggestions on the approach? >>>>> >>>>> [1] https://github.com/wso2/product-mb/tree/c5-migration >>>>> [2] >>>>> . >>>>> ├── carbon-mb >>>>> │ ├── components >>>>> │ │ ├── andes >>>>> │ │ │ ├── andes.iml >>>>> │ │ │ ├── pom.xml >>>>> │ │ │ ├── src >>>>> │ │ │ └── target >>>>> │ │ ├── mb-ui >>>>> │ │ │ ├── mb-ui.iml >>>>> │ │ │ ├── pom.xml >>>>> │ │ │ ├── src >>>>> │ │ │ └── target >>>>> │ │ └── transports >>>>> │ │ ├── amqp >>>>> │ │ └── mqtt >>>>> │ └── features >>>>> │ ├── andes.feature >>>>> │ │ ├── andes.feature.iml >>>>> │ │ ├── pom.xml >>>>> │ │ └── target >>>>> │ ├── etc >>>>> │ │ └── feature.properties >>>>> │ ├── mb-ui.feature >>>>> │ │ ├── mb-ui.feature.iml >>>>> │ │ ├── pom.xml >>>>> │ │ └── target >>>>> │ └── transports >>>>> │ ├── amqp.feature >>>>> │ └── mqtt.feature >>>>> ├── LICENSE.txt >>>>> ├── pom.xml >>>>> ├── README.md >>>>> ├── README.txt >>>>> ├── tests >>>>> │ └── osgi-tests >>>>> │ ├── carbon-mb-osgi-tests.iml >>>>> │ ├── pom.xml >>>>> │ └── target >>>>> │ ├── carbon-mb-osgi-tests-3.5.0-SNAPSHOT.jar >>>>> │ ├── classes >>>>> │ ├── maven-archiver >>>>> │ ├── maven-shared-archive-resources >>>>> │ └── test-classes >>>>> └── tools >>>>> ├── mb-tools.iml >>>>> ├── pom.xml >>>>> └── target >>>>> ├── classes >>>>> │ └── META-INF >>>>> ├── maven-archiver >>>>> │ └── pom.properties >>>>> ├── maven-shared-archive-resources >>>>> │ └── META-INF >>>>> ├── mb-tools-3.5.0-SNAPSHOT.jar >>>>> └── test-classes >>>>> └── META-INF >>>>> >>>>> >>>>> Regards, >>>>> >>>>> -- >>>>> *Asitha Nanayakkara* >>>>> Software Engineer >>>>> WSO2, Inc. http://wso2.com/ >>>>> Mob: + 94 77 85 30 682 >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Hasitha Abeykoon* >>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>> *cell:* *+94 719363063* >>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>>> >>>> >>> >>> >>> -- >>> *Asitha Nanayakkara* >>> Software Engineer >>> WSO2, Inc. http://wso2.com/ >>> Mob: + 94 77 85 30 682 >>> >>> >> >> >> -- >> *Hasitha Abeykoon* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Darshana Akalanka Pagoda Arachchi,* > *Software Engineer* > *078-4721791* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://blog.sameera.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
