Today we had a review meeting with team representatives and please find following meeting notes.
- It seems most of the teams have made great progress on identifying dependant GitHub projects and most cases a product need at most 4 or 5 GitHub projects. - Planning to complete per team doc by this week and will publish on early next week. - There was a little confusion to decide owner project for OAuth2 mediator and few similar mediators, IS and ESB folks will sit together to resolve this. - For the time being components belong to US/UES will remains under product level, once these product get matured we can think about any changes required. - For the time being ESB team own "Cloud Gateway " product but we need a strategy level discussion to find long term owner. - Once the APIM dependency doc is completed they will review with ESB and IS teams. - Once BAM and CEP dependency docs are completed both teams have to review together. - There is a concern about maintaining Hive modification privately, BAM team should come up with a strategy to handle this. - BPS team will own JScrepaer ,unified end point and few other features which only used by them ( Thilini will start separate thread on this ) - We will immediately move Synapse, ODE and Hive forked codes into GitHub - About Stratos - Each team should review their Stratos dependencies make sure whether they really need them. - Pradep will prepare a list of Stratos components that need to maintain at WSO2 - We forgotten to include ELB. Isuru/Vanji, please create a dependency doc for ELB. - We didn't receive dependency docs from MB and SS teams. Thanks ! On Wed, Feb 12, 2014 at 12:18 PM, Madhuka Udantha <madh...@wso2.com> wrote: > > > > On Wed, Feb 12, 2014 at 11:52 AM, Eranda Sooriyabandara > <era...@wso2.com>wrote: > >> Hi Madhuka, >> >> >> >> On Wed, Feb 12, 2014 at 11:30 AM, Madhuka Udantha <madh...@wso2.com>wrote: >> >>> Hi, >>> >>> Jaggery, UES[2] and ES[3] almost developed and maintain in git, for we >>> only had git external for SVN. >>> We have missed UES and ES features and component shared google spread >>> sheet caled 'Moving to Git'. >>> pls added those, It will helpful who are work on $subject >>> >>> >> ES and UES features which are only used by those relevant products, >> > Nope, other products are using/ will use > > UES feature will be used in BAM, CEP > *ES features will be used in other products (such as Greg - service > store,ESB - connector store) - > >> please don't add a new repo instead add them directly to the product >> itself. >> > No planing to added new repo, Since other product can get feature from > ES/UES product. > (In this case then depend on products so one of product release we will > need product release) > > > >> >> thanks >> Eranda >> >> >> >> >> >>> Jaggery will be consider as project and jaggery feature can be found in >>> jaggery product[1]. >>> >>> [1] https://github.com/wso2/jaggery >>> [2] https://github.com/wso2/enterprise-store >>> [3] https://github.com/wso2/ues >>> [4] https://github.com/wso2/jaggery-extensions >>> >>> >>> On Wed, Feb 12, 2014 at 9:38 AM, Sagara Gunathunga <sag...@wso2.com>wrote: >>> >>>> >>>> >>>> >>>> On Wed, Feb 12, 2014 at 9:20 AM, Isuru Udana <isu...@wso2.com> wrote: >>>> >>>>> Hi Sagara, >>>>> >>>>> >>>>> On Wed, Feb 12, 2014 at 12:07 AM, Sagara Gunathunga >>>>> <sag...@wso2.com>wrote: >>>>> >>>>>> >>>>>> Please find POM restructuring guidelines in addition to things we >>>>>> discussed during today's meeting. >>>>>> >>>>>> 1. Top level POM file is the 'parent POM' for your project and there >>>>>> is no real requirement to have separate Maven module to host parent POM >>>>>> file. >>>>>> >>>>>> 2. Eliminate POM files available on 'component' , 'service-stub' and >>>>>> 'features' directories as there is no gain from them instead directly >>>>>> call >>>>>> real Maven modules from parent pom file ( REF - [1] ) >>>>>> >>>>>> e.g - >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <modules> >>>>>> <module>service-stubs/service-mgt</module> >>>>>> <module>service-stubs/webapp-mgt</module> >>>>>> >>>>>> <module>components/service-mgt</module> >>>>>> <module>components/webapp-mgt</module> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <module>features/as-runtimes</module> >>>>>> >>>>>> <module>features/service-mgt</module> >>>>>> <module>features/webapp-mgt</module> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> </modules> >>>>>> >>>>>> >>>>>> >>>>>> [ You can keep same directory structure to enhance human readability >>>>>> ] >>>>>> >>>>>> 3. You must have a <dependencyManagement> section on parent POM >>>>>> and should define all your project dependencies along with versions. ( >>>>>> REF >>>>>> - [1] ) >>>>>> >>>>>> >>>>>> 5. You CAN'T have <dependencyManagement> sections on any other POM >>>>>> file other than parent POM. >>>>>> >>>>>> 6. In each submodule make sure you have Maven dependencies WITHOUT >>>>>> versions ( REF - [2] ) >>>>>> >>>>>> e.g - <dependency> >>>>>> >>>>>> <groupId>org.apache.axis2.wso2</groupId> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <artifactId>axis2</artifactId> >>>>>> >>>>>> </dependency> >>>>>> >>>>>> >>>>>> When you introduce a new Maven dependency define it's version under >>>>>> <dependencyManagement> >>>>>> section of parent POM file. >>>>>> >>>>>> 7. Make sure you have defined following repositories and plugin >>>>>> repositories on parent POM file. These will be used to drag SNAPSHOT >>>>>> versions of other carbon projects which used as dependencies of your >>>>>> project. >>>>>> >>>>>> <repositories> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <repository> >>>>>> <id>wso2-nexus</id> >>>>>> <name>WSO2 internal Repository</name> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/groups/wso2-public/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <releases> >>>>>> <enabled>true</enabled> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <updatePolicy>daily</updatePolicy> >>>>>> <checksumPolicy>ignore</checksumPolicy> >>>>>> </releases> >>>>>> </repository> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <repository> >>>>>> <id>wso2.releases</id> >>>>>> <name>WSO2 internal Repository</name> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/repositories/releases/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <releases> >>>>>> <enabled>true</enabled> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <updatePolicy>daily</updatePolicy> >>>>>> <checksumPolicy>ignore</checksumPolicy> >>>>>> </releases> >>>>>> </repository> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <repository> >>>>>> <id>wso2.snapshots</id> >>>>>> <name>Apache Snapshot Repository</name> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/repositories/snapshots/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <snapshots> >>>>>> <enabled>true</enabled> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <updatePolicy>daily</updatePolicy> >>>>>> </snapshots> >>>>>> <releases> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <enabled>false</enabled> >>>>>> </releases> >>>>>> </repository> >>>>>> >>>>>> </repositories> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <pluginRepositories> >>>>>> >>>>>> <pluginRepository> >>>>>> <id>wso2.releases</id> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <name>WSO2 internal Repository</name> >>>>>> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/repositories/releases/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <releases> >>>>>> <enabled>true</enabled> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <updatePolicy>daily</updatePolicy> >>>>>> >>>>>> <checksumPolicy>ignore</checksumPolicy> >>>>>> </releases> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> </pluginRepository> >>>>>> >>>>>> >>>>>> <pluginRepository> >>>>>> <id>wso2.snapshots</id> >>>>>> <name>Apache Snapshot Repository</name> >>>>>> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/repositories/snapshots/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <snapshots> >>>>>> <enabled>true</enabled> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <updatePolicy>daily</updatePolicy> >>>>>> >>>>>> </snapshots> >>>>>> <releases> >>>>>> >>>>>> <enabled>false</enabled> >>>>>> </releases> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> </pluginRepository> >>>>>> >>>>>> <pluginRepository> >>>>>> <id>wso2-nexus</id> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <name>WSO2 internal Repository</name> >>>>>> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/groups/wso2-public/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <releases> >>>>>> <enabled>true</enabled> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <updatePolicy>daily</updatePolicy> >>>>>> >>>>>> <checksumPolicy>ignore</checksumPolicy> >>>>>> </releases> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> </pluginRepository> >>>>>> >>>>>> </pluginRepositories> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> 8. Make sure you have defined distribution management section as >>>>>> follows on your parent POM file. Jenkins will use these details to >>>>>> deploy >>>>>> your project's SNAPSHOT artefacts into Nexus so that others can use your >>>>>> components without building locally. >>>>>> >>>>>> <distributionManagement> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <repository> >>>>>> <id>wso2.releases</id> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <name>WSO2 internal Repository</name> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/repositories/releases/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> </repository> >>>>>> >>>>>> <snapshotRepository> >>>>>> <id>wso2.snapshots</id> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <name>Apache Snapshot Repository</name> >>>>>> >>>>>> Why this is called *Apache* Snapshot Repository ? I guess name >>>>> should be changed. >>>>> >>>> >>>> Yes, it should be 'WSO2' not 'Apache'. Geeth, please note and modify >>>> on [1]. >>>> >>>> Thanks ! >>>> >>>>> >>>>> Thanks. >>>>> >>>>>> >>>>>> <url>http://maven.wso2.org/nexus/content/repositories/snapshots/</url> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> </snapshotRepository> >>>>>> </distributionManagement> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Please use carbon-deployment[3] as a reference project. Eranda/Geeth >>>>>> please add if I missed anything. >>>>>> >>>>>> >>>>>> [1] - https://github.com/wso2/carbon-deployment/blob/master/pom.xml >>>>>> >>>>>> [2] - >>>>>> https://github.com/wso2/carbon-deployment/blob/master/components/webapp-mgt/org.wso2.carbon.webapp.mgt.ui/pom.xml >>>>>> >>>>>> [3] - https://github.com/wso2/carbon-deployment/ >>>>>> >>>>>> >>>>>> >>>>>> Thanks ! >>>>>> -- >>>>>> Sagara Gunathunga >>>>>> >>>>>> Senior Technical Lead; WSO2, Inc.; http://wso2.com >>>>>> V.P Apache Web Services; http://ws.apache.org/ >>>>>> Linkedin; http://www.linkedin.com/in/ssagara >>>>>> Blog ; http://ssagara.blogspot.com >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Isuru Udana* >>>>> Senior >>>>> * Software Engineer* >>>>> WSO2 Inc.; http://wso2.com >>>>> email: isu...@wso2.com cell: +94 77 3791887 >>>>> blog: http://mytecheye.blogspot.com/ >>>>> twitter: http://twitter.com/isudana >>>>> >>>> >>>> >>>> >>>> -- >>>> Sagara Gunathunga >>>> >>>> Senior Technical Lead; WSO2, Inc.; http://wso2.com >>>> V.P Apache Web Services; http://ws.apache.org/ >>>> Linkedin; http://www.linkedin.com/in/ssagara >>>> Blog ; http://ssagara.blogspot.com >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Madhuka* Udantha >>> Senior Software Engineer >>> Development Technologies >>> WSO2 Inc. : http://wso2.com >>> >>> *Mobile*: +94774066336 >>> *Blog*: http://madhukaudantha.blogspot.com/ >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Eranda Sooriyabandara*Senior Software Engineer; >> Integration Technologies Team; >> WSO2 Inc.; http://wso2.com >> Lean . Enterprise . Middleware >> >> E-mail: eranda AT wso2.com >> Mobile: +94 716 472 816 >> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >> Blog: http://emsooriyabandara.blogspot.com/ >> >> >> >> >> > > > -- > *Madhuka* Udantha > Senior Software Engineer > Development Technologies > WSO2 Inc. : http://wso2.com > > *Mobile*: +94774066336 > *Blog*: http://madhukaudantha.blogspot.com/ > -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev