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.com>wrote: > >> >> >> >> On Mon, Feb 17, 2014 at 3:31 PM, Sagara Gunathunga <sag...@wso2.com>wrote: >> >>> >>> >>> >>> On Mon, Feb 17, 2014 at 12:14 PM, Sumedha Rubasinghe >>> <sume...@wso2.com>wrote: >>> >>>> 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.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> >>>>> >>>>> <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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> /sumedha >>>> m: +94 773017743 >>>> b : bit.ly/sumedha >>>> >>> >>> >>> >>> -- >>> 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 >>> >>> >> >> >> -- >> /sumedha >> m: +94 773017743 >> b : bit.ly/sumedha >> > > > > -- > 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 > > -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com <http://wso2.com/>* *Mobile:(+94)777219209* *Mobile USA:**(+1)918 813 2403* [image: Facebook] <https://www.facebook.com/vanjikumaran> [image: Twitter]<https://twitter.com/vanjikumaran> [image: LinkedIn] <http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> [image: Blogger] <http://vanjikumaran.blogspot.com/> [image: SlideShare]<http://www.slideshare.net/vanjikumaran> This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, re-transmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
