Re: [Dev] Guidelines to move project into GitHub
Hi Sagara, We are manage to stabilize the Synapse[1] in Git, Please do the need full to add this in the regular build process and Nexus upload. Thank you, Best Regards, vanji [1]https://github.com/wso2/wso2-synapse On Mon, Feb 17, 2014 at 6:09 PM, Sagara Gunathunga sag...@wso2.com wrote: On Mon, Feb 17, 2014 at 4:38 PM, Sumedha Rubasinghe sume...@wso2.comwrote: On Mon, Feb 17, 2014 at 3:31 PM, Sagara Gunathunga sag...@wso2.comwrote: On Mon, Feb 17, 2014 at 12:14 PM, Sumedha Rubasinghe sume...@wso2.comwrote: Hi Sagara, Small concern. It feels like the module name 'carbon-apis ( https://github.com/wso2/carbon-apis)' is confusing. And hosting both appmgt apimgt features ( https://github.com/wso2/carbon-apis/tree/master/features) inside 'carbon-apis' feels more confusing. 'carbon-apis' should be reserved for more 'Carbon related APIs' IMO. Can we change this to two module names such as 'carbon-apimgt' 'carbon-appmgt' instead? +1 to rename carbon-api as carbon-apimg. BTW I'm not clear with carbon-appmgt project what are the components belong to this project ? Is there any other project going to use those component ? if not we can maintain those components under appManger product instead of introducing new carbon-appmgt' project ( This what we do with other product as well) WDYT ? How AppManager project will move forward (with respective to a separate project or merged) is not clearly defined as of now. Right now, it's components are not being used by any other component. So for future refactoring needs, I would prefer to have 'carbon-appmgt' as a separate module. ES and UES components are already used by number of other projects but the team is happy to maintain ES/UES components under ES/UES products, the only potential issue is UES team has to release these products when ever dependent project require modifications. But the truth is ES/UES are relatively new and growing projects they any how have to release very often so for the time being above mention issue is not a real problem. What UES team agreed is maintain their components under each product for the time being and will move to separate project when products got matured and above issue become a real problem. in my POV technically same story goes with AppManager product as well WDYT ? We always can refactor in future if the real requirement arias. Now we already have around 15 platform projects and when we move products also into GitHub the number become 30 or more. If we allow to have carbon-appmgt project today there is no reason not to allow separate projects for ES/UES or any other product that wish to do so but think about the operational overhead. One of the main successive factor is we need to keep very less number of platform level projects on GitHub as an example BAM and CEP team sharing a single project. Another alternative is to have one platform level project to hold components belong to both APIManager and AppManager products. Thanks ! Thanks ! Sorry for this observation now. But realized this only after seeing the actual project structure. On Wed, Feb 12, 2014 at 12:07 AM, Sagara Gunathunga sag...@wso2.comwrote: 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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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
Re: [Dev] Guidelines to move project into GitHub
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.comwrote: Hi Madhuka, On Wed, Feb 12, 2014 at 11:30 AM, Madhuka Udantha madh...@wso2.comwrote: 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.comwrote: 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.comwrote: 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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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.
Re: [Dev] Guidelines to move project into GitHub
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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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 idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /pluginRepository pluginRepository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /pluginRepository pluginRepository idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/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 idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url /repository snapshotRepository idwso2.snapshots/id nameApache Snapshot Repository/name Why this is called *Apache* Snapshot Repository ? I guess name should be changed.
[Dev] Guidelines to move project into GitHub
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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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 idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /pluginRepository pluginRepository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /pluginRepository pluginRepository idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/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 idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url /repository snapshotRepository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://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] -
Re: [Dev] Guidelines to move project into GitHub
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.comwrote: 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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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 idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /pluginRepository pluginRepository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /pluginRepository pluginRepository idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/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 idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url /repository snapshotRepository idwso2.snapshots/id nameApache Snapshot
Re: [Dev] Guidelines to move project into GitHub
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 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.comwrote: 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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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 idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /pluginRepository pluginRepository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /pluginRepository pluginRepository idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy
Re: [Dev] Guidelines to move project into GitHub
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, please don't add a new repo instead add them directly to the product itself. 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.comwrote: 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.comwrote: 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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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 idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /pluginRepository pluginRepository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /pluginRepository pluginRepository idwso2-nexus/id
Re: [Dev] Guidelines to move project into GitHub
On Wed, Feb 12, 2014 at 11:52 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Madhuka, On Wed, Feb 12, 2014 at 11:30 AM, Madhuka Udantha madh...@wso2.comwrote: 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.comwrote: 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.comwrote: 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 moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection 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 groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/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 idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /pluginRepository pluginRepository
