Re: [Dev] [Architecture] [Carbon5] Coarse grained OSGi bundles
+1 and this will make out build also much much faster On Wed, Mar 13, 2013 at 6:57 AM, Afkham Azeez az...@wso2.com wrote: Folks, We got carried away a bit when we adopted OSGi started creating one OSGi bundle per top level package. So we ended up with 100s of bundles, and things have become unmanageable to a certain degree. We are going to fix that with Carbon 5 we will end up with a much smaller number of bundles. For example, the screenshot below shows the Carbon kernel OSGi bundle which now includes a number of top level packages. I think it may even be a good idea to rename the bundle to carbon-kernel.jar instead of org.wso2.carbon.kernel.jar. We will need to adopt the same practice for components where we would have to merge a number of existing components. For example, I can think of mediators.jar perhaps governance.jar. [image: Inline image 1] Thoughts suggestions about this approach are welcome. One concern would be that we won't be able to do fine-grained patching, but that is a compromise we are willing to make, and having a smaller number of bundles will make it easier to manage patches. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Srinath Perera, Ph.D. http://www.cs.indiana.edu/~hperera/ http://srinathsview.blogspot.com/ Screen Shot 2013-03-13 at 6.50.25 AM.png___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Problems importing WSO2 kernel as Maven project into Eclipse
Hi Eranda and Vijitha, Thanks for the prompt reply. Just want to make sure we are on the same page. The orbit URL you gave us is broken. What I need to do now are: 1. Check out orbit from https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/, run mvn clean install to build orbit 2. Check out kernel from https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/, run mvn clean install to build kernel 3. Then run maven eclipse:eclipse to convert them to eclipse projects. Am I doing the right thing? Thanks in advance. On Wed, Mar 13, 2013 at 11:44 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Bin, First you need to try building the kernel. To do that you need to check out orbit from https://svn.wso2.org/repos/wso2/carbon/kernel/orbit/4.0.0/and build it. Then there will be all the dependencies you need in your local maven repository and will be able to import to eclipse using vijitha's command at no time. thanks Eranda On Wed, Mar 13, 2013 at 8:00 AM, Bin Rong steven.r...@gmail.com wrote: Hi Vijitha, Many thanks for your reply. I tried the approach you pointed out to convert Maven project into eclipse project, then tried to import into Developer Studio 3.0. However, there are more than 20,000 dependencies problem. Tried to manually add some of the missing libraries, but it's just too tedious. Just wondering how you guys do the development within WSO2, or is there any developer guide/manual? We love the WSO2 concept and product, but it seems the learning curve is a little bit deep. Thanks very much for your time and help. On Mon, Feb 25, 2013 at 10:02 PM, Vijitha Kumara viji...@wso2.comwrote: Hi Bin, On Thu, Feb 21, 2013 at 7:51 PM, Bin Rong steven.r...@gmail.com wrote: Hi there, I tried to import WSO2 kernel as Maven project into Eclipse, however, there are all sorts of build path problems, in particular, couldn't locate the necessary libraries. FYI, I use Spring STS with m2eclipse plugin, and checkout source code from https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/. Could anyone point me to a developer guide or any documentation of how to develop/extend WSO2 kernel, and how to add/remove bundles when it's necessary. You'd need to point to a specific patch release pom files specifically if you intend to work on a such, or the pom file inside 4.0.0 for the initial 4.0.0 release. You can run maven eclipse:eclipse to convert them to eclipse projects. Regards, Vijitha. Thanks in advance. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Vijitha Kumara Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: viji...@wso2.com m: +1 408 874 5622 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Carbon5] JSON syntax for config files?
On Tue, Mar 12, 2013 at 8:32 PM, Senaka Fernando sen...@wso2.com wrote: Hi Azeez, More than docs, we need to consider the user experience aspect. People are using these things in real production environments. Some have scripted their deployments. How much of an effort is it to move from XML to JSON in that sense? I think that's not straightforward. Also, we use XML all over the place. Ex:- Synapse Config, Registry Handlers, Lifecycles, Endpoints - basically everything configuration across every single component is XML. Unless everything becomes JSON, the users have to train themselves to do two things. So, what looks cool to us does not look so cool to everybody. So, its not just kernel that we need to think about, its the whole platform. Unless we have a platform-wide move, I'm -0 for this. I agree with Senaka too. User experience is going to be an issue once dev-ops try to migrate from C4 to C5. For example we have a customer who experienced issue while migrating to C4 simply because we had split our config files and also moved them to different directories etc. This becomes more complicated with Stratos setup where dev-ops have written scripts etc to automate deployment. Obviously there will be changes in configs but moving from xml to JSON is too much of a leap IMO .. Also we cannot add comments in JSON based config files (if I am not mistaken), plus even a JSON based config file is going to look clattered once we introduce nested configurations.! Also, based on the last internal discussion on this, Paul said, Plain JSON is worse than plain XML, IIRC. I thought we agreed for configuration files like the LB model in that discussion, but again that would mean custom parsers, custom work, and adoption across the entire platform. Thanks, Senaka. On Tue, Mar 12, 2013 at 6:38 AM, Afkham Azeez az...@wso2.com wrote: I agree on the points everybody has mentioned in support of XML in config files. But it seems that most people still don't understand that Carbon 5 is going to be a major shift. We are removing the Axis2 dependency from the kernel, and minifying the kernel. Lots of things starting from some package structures will be changed. Docs will need updating. From Carbon 4.0 to 5.0 is going to be a major leap. Azeez On Tue, Mar 12, 2013 at 6:53 PM, Maninda Edirisooriya mani...@wso2.comwrote: I think JSON is more human readable than XML, as it is cleaner than XML. (I may be wrong as I am familiar with JavaScript) And as Nuwan said we will not get the Everything JSON feeling. But many web developers will be much familiar with JSON than XML as Jaggery and JavaScript are JSON based. But there is still a major XML dependancy, that is web services. As all the web services are still comes with XML, JSON Everyware story will not be complete. So I prefer moving to SOAP based web services to REST/JSON based system rather than changing configs from XML to JSON. The reason is current XML configs has no major problem and changing it will course lot of bugs and support issues. We can postpone this until XML becomes a unpopular language which will not happen in near future. Until that we can work on changing message protocols from XML/AXIOM to REST/JSON and improve the performance and simplicity of the implementation in ESB and AS. *Maninda Edirisooriya* Software Engineer *WSO2, Inc. *lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *Phone* : +94 777603226 On Tue, Mar 12, 2013 at 4:45 PM, Sagara Gunathunga sag...@wso2.comwrote: On Tue, Mar 12, 2013 at 12:41 PM, Afkham Azeez az...@wso2.com wrote: Folks, I am starting a new thread to see how everybody feels about using JSON syntax for the config files wer are using. I personally feel that it looks elegant, and very easy to edit with vi. Also, we don't do any schema validation of our config files, and the config file structures are simple, so JSON could be more appropriate. Thoughts? I'm -0 on this change. Other than user friendliness do we have any significant customer related issue to fix by changing configuration files into JSON ? If not we should target to solve significant C4 issues first. As some people mentioned this needs great amount of documentation and migration tools, I don't believe it's a good idea to do this at the beginning of C5. Thanks ! -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Architecture mailing list architect...@wso2.org
[Dev] Error in Compilation of platform/components/synapse-registries/org.wso2.carbon.mediation.registry/4.1.0
Hi [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/wso2/as501/latest/platform/components/synapse-registries/org.wso2.carbon.mediation.registry/4.1.0/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java:[50,7] org.wso2.carbon.mediation.registry.WSO2Registry is not abstract and does not override abstract method lookupFormat(java.lang.String) in org.apache.synapse.registry.Registry [ERROR] /home/wso2/as501/latest/platform/components/synapse-registries/org.wso2.carbon.mediation.registry/4.1.0/src/main/java/org/wso2/carbon/mediation/registry/ESBRegistry.java:[51,7] org.wso2.carbon.mediation.registry.ESBRegistry is not abstract and does not override abstract method lookupFormat(java.lang.String) in org.apache.synapse.registry.Registry Thanks *G. K. S. Munasinghe * *Software Engineer,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: ge...@wso2.com phone:(+94) 777911226 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Problems importing WSO2 kernel as Maven project into Eclipse
HI Bin, Sorry for the broken link, I was manually created it. Your procedure is correct for all bundles which is release in carbon 4.0.0. But if you need any other version you need to build the patch release according to that version. e.g. If you need to update 4.0.5 versioned bundle then you should build patch-releases/4.0.5. thanks Eranda On Wed, Mar 13, 2013 at 12:05 PM, Bin Rong steven.r...@gmail.com wrote: Hi Eranda and Vijitha, Thanks for the prompt reply. Just want to make sure we are on the same page. The orbit URL you gave us is broken. What I need to do now are: 1. Check out orbit from https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/, run mvn clean install to build orbit 2. Check out kernel from https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/, run mvn clean install to build kernel 3. Then run maven eclipse:eclipse to convert them to eclipse projects. Am I doing the right thing? Thanks in advance. On Wed, Mar 13, 2013 at 11:44 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Bin, First you need to try building the kernel. To do that you need to check out orbit from https://svn.wso2.org/repos/wso2/carbon/kernel/orbit/4.0.0/and build it. Then there will be all the dependencies you need in your local maven repository and will be able to import to eclipse using vijitha's command at no time. thanks Eranda On Wed, Mar 13, 2013 at 8:00 AM, Bin Rong steven.r...@gmail.com wrote: Hi Vijitha, Many thanks for your reply. I tried the approach you pointed out to convert Maven project into eclipse project, then tried to import into Developer Studio 3.0. However, there are more than 20,000 dependencies problem. Tried to manually add some of the missing libraries, but it's just too tedious. Just wondering how you guys do the development within WSO2, or is there any developer guide/manual? We love the WSO2 concept and product, but it seems the learning curve is a little bit deep. Thanks very much for your time and help. On Mon, Feb 25, 2013 at 10:02 PM, Vijitha Kumara viji...@wso2.comwrote: Hi Bin, On Thu, Feb 21, 2013 at 7:51 PM, Bin Rong steven.r...@gmail.comwrote: Hi there, I tried to import WSO2 kernel as Maven project into Eclipse, however, there are all sorts of build path problems, in particular, couldn't locate the necessary libraries. FYI, I use Spring STS with m2eclipse plugin, and checkout source code from https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/. Could anyone point me to a developer guide or any documentation of how to develop/extend WSO2 kernel, and how to add/remove bundles when it's necessary. You'd need to point to a specific patch release pom files specifically if you intend to work on a such, or the pom file inside 4.0.0 for the initial 4.0.0 release. You can run maven eclipse:eclipse to convert them to eclipse projects. Regards, Vijitha. Thanks in advance. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Vijitha Kumara Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: viji...@wso2.com m: +1 408 874 5622 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Products 4.0.7 #123 has FAILED. Change made by 4 authors.
--- WSO2 Carbon 4.0.x Products 4.0.7 #123 failed. --- Code has been updated by krishantha Samaraweera, Ishara Karunarathna, Ajith Vitharana, Dinusha Dilrukshi. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PRO007-123/ - Currently Responsible - Eranda Sooriyabandara (Assigned by Maheshika Goonetilleke) Isuru Udana Loku Narangoda (Automatically assigned) Manu Perera (Automatically assigned) Nuwan Dias (Assigned by Maheshika Goonetilleke) Prabath Siriwardena (Assigned by Maheshika Goonetilleke) Ruchira Wageesha (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 9 tests passed. -- Code Changes -- Ishara Karunarathna (167652): Fixed IDENTITY-774 Ajith Vitharana (167651): Fixing REGISTRY-1605 Ajith Vitharana (167650): Fixing REGISTRY-1606 -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] Carbon SNAPSHOT 4.1.0 Products #34 Default Job has FAILED. Change made by Isuru Wimalasundera.
Carbon SNAPSHOT 4.1.0 Products #34 Default Job failed. The build was triggered because the code has been changed. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WSO2CARBON-CSPR001-JOB1-34/ -- Code Changes -- Isuru Wimalasundera (167683): changing the pom.xml Isuru Wimalasundera (167679): changing dependecy folder structure Isuru Wimalasundera (167681): changing dependency folder structure -- Error Summary -- Usage: nbsp; kill pid ...nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; Send SIGTERM to every process listed. nbsp; kill signal pid ...nbsp; nbsp; nbsp; nbsp;Send a signal to every process listed. nbsp; kill -s signal pid ...nbsp; nbsp; Send a signal to every process listed. nbsp; kill -lnbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;List all signal names. nbsp; kill -Lnbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;List all signal names in a nice table. nbsp; kill -l signalnbsp; nbsp; nbsp; nbsp; nbsp; nbsp; Convert between signal numbers and names. find: `/home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-PRODUCTS-JOB1/products': No such file or directory -- This message is automatically generated by Atlassian Bamboo ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Carbon5] Coarse grained OSGi bundles
On Wed, Mar 13, 2013 at 6:57 AM, Afkham Azeez az...@wso2.com wrote: Folks, We got carried away a bit when we adopted OSGi started creating one OSGi bundle per top level package. So we ended up with 100s of bundles, and things have become unmanageable to a certain degree. We are going to fix that with Carbon 5 we will end up with a much smaller number of bundles. For example, the screenshot below shows the Carbon kernel OSGi bundle which now includes a number of top level packages. I think it may even be a good idea to rename the bundle to carbon-kernel.jar instead of org.wso2.carbon.kernel.jar. We will need to adopt the same practice for components where we would have to merge a number of existing components. For example, I can think of mediators.jar perhaps governance.jar. +1 for above approach and naming convention. Also with C5 can we enforce proper OSGi versioning convention for WSO2 bundles ? Thanks ! [image: Inline image 1] Thoughts suggestions about this approach are welcome. One concern would be that we won't be able to do fine-grained patching, but that is a compromise we are willing to make, and having a smaller number of bundles will make it easier to manage patches. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Screen Shot 2013-03-13 at 6.50.25 AM.png___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test Failure in rampart 1.6.1-wso2v9 in branch 4.1.0
Hi, Found the cause. 4.0.0 rampart depends on axis2 v5 still. When we have updated that to latest axis2 we are getting the test failure.! thanks, On Wed, Mar 13, 2013 at 8:42 AM, Supun Malinga sup...@wso2.com wrote: Hi, Yes!. I checked this but there was not significant diff there to identify.. Will copy over from the 4.0.0 branch and check. thanks, On Tue, Mar 12, 2013 at 11:54 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: This is failing only in 4.1.0 but 4.0.0 builds fine (rampart version in both v9). So I think there are some commits missing from 4.0.0 to 4.1.0. If there are no code level changes to rampart in 4.1.0, then the easy thing would be to remove the rampart sources form 4.1.0 and do a svn cp from 4.0.0 and add it again. On Tue, Mar 12, 2013 at 10:19 PM, Supun Malinga sup...@wso2.com wrote: Hi, Any update on this. This still happens on 4.1.0 branch. thanks, On Wed, Mar 6, 2013 at 6:02 PM, Supun Malinga sup...@wso2.com wrote: Please have a look, Test set: org.apache.rampart.RampartTest --- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.737 sec FAILURE! testWithPolicy(org.apache.rampart.RampartTest) Time elapsed: 6.734 sec FAILURE! junit.framework.ComparisonFailure: expected:[Expected encrypted part missing] but was:[Unexpected encrypted data found, no encryption required] at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.apache.rampart.RampartTest.testWithPolicy(RampartTest.java:134) thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Kernel 4.0.7 #63 has FAILED. Change made by 5 authors.
--- WSO2 Carbon 4.0.x Kernel 4.0.7 #63 failed. --- This build was manually triggered by Maheshika Goonetilleke. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-KER007-63/ - Currently Responsible - Asela Pathberiya (Automatically assigned) Chanaka Jayasena (Automatically assigned) Hasini Gunasinghe (Automatically assigned) Johann Nallathamby (Automatically assigned) Prabath Siriwardena (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Chanaka Jayasena (167665): Fix for issue https://wso2.org/jira/browse/IDENTITY-823 Hasini Gunasinghe (167659): fixing an issue related to login without domain name Chanaka Jayasena (167662): Fixing an IE 8 issue with button colors -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Build breaks in trunk orbit
*The trunk orbit fails to build in a clean m2 repo. Seems version 4.1.0
orbit-parent is used as a dependency to the trunk orbit.*
[INFO] Scanning for projects...
[ERROR] The build could not read 9 projects - [Help 1]
[ERROR]
[ERROR] The project org.glassfish.web.wso2:el-impl:2.2.wso2v1
(/home/maninda/c/carbon/orbit/trunk/el-impl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project javax.servlet.jsp.jstl.wso2:jstl:1.2.1.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jstl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project org.apache.tiles.wso2:tiles-jsp:2.0.5.wso2v2
(/home/maninda/c/carbon/orbit/trunk/tiles/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:tomcat:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.ha.wso2:tomcat-ha:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat-ha/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:jdbc-pool:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jdbc-pool/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.wso2.wadl.core.wso2:wadl-core:${wadl-core.version}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/wadl-core/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.httpcomponents.wso2:httpcore:${orbit.patch.version.httpcore}
(/home/maninda/c/carbon/orbit/trunk/httpcore/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 23, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.httpcomponents.wso2:httpcore-nio:4.2.3.wso2v1
(/home/maninda/c/carbon/orbit/trunk/httpcore-nio/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
Re: [Dev] Build breaks in trunk orbit
You need to build 4.1.0 orbit, to build trunk kernel and platform I
believe...
On Wed, Mar 13, 2013 at 6:17 PM, Maninda Edirisooriya mani...@wso2.comwrote:
*The trunk orbit fails to build in a clean m2 repo. Seems version 4.1.0
orbit-parent is used as a dependency to the trunk orbit.*
[INFO] Scanning for projects...
[ERROR] The build could not read 9 projects - [Help 1]
[ERROR]
[ERROR] The project org.glassfish.web.wso2:el-impl:2.2.wso2v1
(/home/maninda/c/carbon/orbit/trunk/el-impl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project javax.servlet.jsp.jstl.wso2:jstl:1.2.1.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jstl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project org.apache.tiles.wso2:tiles-jsp:2.0.5.wso2v2
(/home/maninda/c/carbon/orbit/trunk/tiles/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:tomcat:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.ha.wso2:tomcat-ha:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat-ha/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:jdbc-pool:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jdbc-pool/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.wso2.wadl.core.wso2:wadl-core:${wadl-core.version}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/wadl-core/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.httpcomponents.wso2:httpcore:${orbit.patch.version.httpcore}
(/home/maninda/c/carbon/orbit/trunk/httpcore/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 23, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.httpcomponents.wso2:httpcore-nio:4.2.3.wso2v1
(/home/maninda/c/carbon/orbit/trunk/httpcore-nio/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
Re: [Dev] Build breaks in trunk orbit
Hi,
On Wed, Mar 13, 2013 at 6:41 PM, Tharindu Mathew thari...@wso2.com wrote:
You need to build 4.1.0 orbit, to build trunk kernel and platform I
believe...
No.. we have fixed that by using externals. This is a seperate issue.
Httpcore was added recently and its relativePath is wrong. Thats the cause
of this issue.
thanks,
On Wed, Mar 13, 2013 at 6:17 PM, Maninda Edirisooriya mani...@wso2.comwrote:
*The trunk orbit fails to build in a clean m2 repo. Seems version 4.1.0
orbit-parent is used as a dependency to the trunk orbit.*
[INFO] Scanning for projects...
[ERROR] The build could not read 9 projects - [Help 1]
[ERROR]
[ERROR] The project org.glassfish.web.wso2:el-impl:2.2.wso2v1
(/home/maninda/c/carbon/orbit/trunk/el-impl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project javax.servlet.jsp.jstl.wso2:jstl:1.2.1.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jstl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project org.apache.tiles.wso2:tiles-jsp:2.0.5.wso2v2
(/home/maninda/c/carbon/orbit/trunk/tiles/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:tomcat:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.ha.wso2:tomcat-ha:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat-ha/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:jdbc-pool:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jdbc-pool/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.wso2.wadl.core.wso2:wadl-core:${wadl-core.version}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/wadl-core/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.httpcomponents.wso2:httpcore:${orbit.patch.version.httpcore}
(/home/maninda/c/carbon/orbit/trunk/httpcore/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 23, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.httpcomponents.wso2:httpcore-nio:4.2.3.wso2v1
(/home/maninda/c/carbon/orbit/trunk/httpcore-nio/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0
Re: [Dev] Build breaks in trunk orbit
All these externals are pointing to the 4.1.0 orbit parent pom [1], not the
trunk's orbit parent pom. That's why the above error occurs. Either you
will have to copy the 4.1.0 orbit parent to your m2 repo manually, and
build the trunk or build 4.1.0 branch first, and then try to build trunk.
These are workarounds. These will be fixed after hosting the 4.1.0 orbits
in wso2 nexus maven repo. That will happen within this week.
[1] http://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.1.0/pom.xml
On Wed, Mar 13, 2013 at 6:57 PM, Supun Malinga sup...@wso2.com wrote:
Hi,
On Wed, Mar 13, 2013 at 6:41 PM, Tharindu Mathew thari...@wso2.comwrote:
You need to build 4.1.0 orbit, to build trunk kernel and platform I
believe...
No.. we have fixed that by using externals. This is a seperate issue.
Httpcore was added recently and its relativePath is wrong. Thats the cause
of this issue.
thanks,
On Wed, Mar 13, 2013 at 6:17 PM, Maninda Edirisooriya
mani...@wso2.comwrote:
*The trunk orbit fails to build in a clean m2 repo. Seems version 4.1.0
orbit-parent is used as a dependency to the trunk orbit.*
[INFO] Scanning for projects...
[ERROR] The build could not read 9 projects - [Help 1]
[ERROR]
[ERROR] The project org.glassfish.web.wso2:el-impl:2.2.wso2v1
(/home/maninda/c/carbon/orbit/trunk/el-impl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project javax.servlet.jsp.jstl.wso2:jstl:1.2.1.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jstl/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project org.apache.tiles.wso2:tiles-jsp:2.0.5.wso2v2
(/home/maninda/c/carbon/orbit/trunk/tiles/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:tomcat:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.ha.wso2:tomcat-ha:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/tomcat-ha/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.tomcat.wso2:jdbc-pool:${version.tomcat}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/jdbc-pool/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.wso2.wadl.core.wso2:wadl-core:${wadl-core.version}.wso2v1
(/home/maninda/c/carbon/orbit/trunk/wadl-core/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:orbit-parent:pom:4.1.0 in http://repo1.maven.org/maven2was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 22, column 13 -
[Help 2]
[ERROR]
[ERROR] The project
org.apache.httpcomponents.wso2:httpcore:${orbit.patch.version.httpcore}
(/home/maninda/c/carbon/orbit/trunk/httpcore/pom.xml) has 1 error
[ERROR] Non-resolvable parent
[Dev] Where do we maintain the orbit bundles of the kernel?
Pradeep/Amila, Where should these be maintained? Do we need to have separate GitHub repositories per orbit bundle? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Kernel 4.1.0 build failure
Latest kernel 4.1.0 build failed due to following error. What could be the reason here ? Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.1:run (default) on project wso2carbon-core: Error executing ant tasks: /home/krishantha/svn/trunk/carbon/kernel/branches/4.1.0/distribution/kernel/4.1.0/target/WSO2Carbon/configuration/org.eclipse.equinox.simpleconfigurator not found Thanks, Krishantha. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Kernel 4.1.0 build failure
Hi, I'm also getting this. Any idea? thanks, On Wed, Mar 13, 2013 at 7:46 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Latest kernel 4.1.0 build failed due to following error. What could be the reason here ? Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.1:run (default) on project wso2carbon-core: Error executing ant tasks: /home/krishantha/svn/trunk/carbon/kernel/branches/4.1.0/distribution/kernel/4.1.0/target/WSO2Carbon/configuration/org.eclipse.equinox.simpleconfigurator not found Thanks, Krishantha. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.7 #139 has FAILED. Change made by 8 authors.
--- WSO2 Carbon 4.0.x Platform 4.0.7 #139 failed. --- Code has been updated by Ishara Karunarathna, Asela Pathberiya, Ajith Vitharana, Dinusha Dilrukshi, Nuwan Wimalasekara, Harsha Thirimanna, Chathura Kulasinghe, Chanaka Jayasena. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA007-139/ - Currently Responsible - Ajith Vitharana (Automatically assigned) Asela Pathberiya (Automatically assigned) Chanaka Jayasena (Automatically assigned) Chathura Kulasinghe (Automatically assigned) Dinusha Dilrukshi (Automatically assigned) Harsha Thirimanna (Automatically assigned) Ishara Karunarathna (Automatically assigned) Nuwan Wimalasekara (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 329 tests passed. -- Code Changes -- Chanaka Jayasena (167687): changing the breadcrumb size Chathura Kulasinghe (167669): getJsonTree method added Harsha Thirimanna (167693): ESB artifact for AppFactory -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Kernel 4.1.0 build failure
Hi, Fixed this. Had to branch p2-plugin 1.5.2. thanks, On Wed, Mar 13, 2013 at 7:51 PM, Supun Malinga sup...@wso2.com wrote: Hi, I'm also getting this. Any idea? thanks, On Wed, Mar 13, 2013 at 7:46 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Latest kernel 4.1.0 build failed due to following error. What could be the reason here ? Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.1:run (default) on project wso2carbon-core: Error executing ant tasks: /home/krishantha/svn/trunk/carbon/kernel/branches/4.1.0/distribution/kernel/4.1.0/target/WSO2Carbon/configuration/org.eclipse.equinox.simpleconfigurator not found Thanks, Krishantha. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Problems importing WSO2 kernel as Maven project into Eclipse
Hi Eranda, I tried to run mvn clean install for orbit, however, I got the following error: [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Project 'antlr.wso2:antlr' is duplicated in the reactor [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Project 'antlr.wso2:antlr' is duplicated in the reactor at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:300) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6 0) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.DuplicateProjectException: Project ' antlr.ws o2:antlr' is duplicated in the reactor at org.apache.maven.project.ProjectSorter.init(ProjectSorter.java:93) at org.apache.maven.execution.ReactorManager.init(ReactorManager.java: 99) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:288) ... 11 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Mar 13 23:56:28 CST 2013 [INFO] Final Memory: 6M/242M [INFO] I checked the project settings, there are two versions of antlr existed, they do differ by their version number. Could you please have a look? FYI, I checked out from https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/, and I am using jdk 1.6.43 and Maven 2.2.1. Thanks in advance. On Wed, Mar 13, 2013 at 3:11 PM, Eranda Sooriyabandara era...@wso2.comwrote: HI Bin, Sorry for the broken link, I was manually created it. Your procedure is correct for all bundles which is release in carbon 4.0.0. But if you need any other version you need to build the patch release according to that version. e.g. If you need to update 4.0.5 versioned bundle then you should build patch-releases/4.0.5. thanks Eranda On Wed, Mar 13, 2013 at 12:05 PM, Bin Rong steven.r...@gmail.com wrote: Hi Eranda and Vijitha, Thanks for the prompt reply. Just want to make sure we are on the same page. The orbit URL you gave us is broken. What I need to do now are: 1. Check out orbit from https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/, run mvn clean install to build orbit 2. Check out kernel from https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/, run mvn clean install to build kernel 3. Then run maven eclipse:eclipse to convert them to eclipse projects. Am I doing the right thing? Thanks in advance. On Wed, Mar 13, 2013 at 11:44 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Bin, First you need to try building the kernel. To do that you need to check out orbit from https://svn.wso2.org/repos/wso2/carbon/kernel/orbit/4.0.0/ and build it. Then there will be all the dependencies you need in your local maven repository and will be able to import to eclipse using vijitha's command at no time. thanks Eranda On Wed, Mar 13, 2013 at 8:00 AM, Bin Rong steven.r...@gmail.com wrote: Hi Vijitha, Many thanks for your reply. I tried the approach you pointed out to convert Maven project into eclipse project, then tried to import into Developer Studio 3.0. However, there are more than 20,000 dependencies problem. Tried to manually add some of the missing libraries, but it's just too tedious. Just wondering how you guys do the development within WSO2, or is there any developer guide/manual? We love the WSO2 concept and product, but it seems the learning curve is a little bit deep. Thanks very much for your time and help. On Mon, Feb 25, 2013 at 10:02 PM, Vijitha Kumara viji...@wso2.comwrote: Hi Bin, On Thu, Feb 21, 2013 at 7:51 PM, Bin Rong steven.r...@gmail.comwrote: Hi there, I tried to import WSO2 kernel as Maven project into Eclipse, however, there are all sorts of build path problems, in particular, couldn't locate the necessary libraries. FYI, I use Spring STS with m2eclipse plugin, and checkout source code from
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Products 4.0.7 #125 has FAILED. Change made by Ishara Karunarathna, Harsha Thirimanna and Chathura Kulasinghe.
--- WSO2 Carbon 4.0.x Products 4.0.7 #125 failed. --- Code has been updated by Ishara Karunarathna, Harsha Thirimanna, Chathura Kulasinghe. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PRO007-125/ - Currently Responsible - Chathura Kulasinghe (Automatically assigned) Harsha Thirimanna (Automatically assigned) Ishara Karunarathna (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 9 tests passed. -- Code Changes -- Harsha Thirimanna (167693): ESB artifact for AppFactory Chathura Kulasinghe (167703): changed CDN urls to local Chathura Kulasinghe (167697): -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] Carbon SNAPSHOT 4.1.0 Products #35 Default Job has FAILED. Change made by Isuru Wimalasundera.
Carbon SNAPSHOT 4.1.0 Products #35 Default Job failed. The build was triggered because the code has been changed. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WSO2CARBON-CSPR001-JOB1-35/ -- Code Changes -- Isuru Wimalasundera (167752): read from payload file -- Error Summary -- find: `/home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-PRODUCTS-JOB1/products': No such file or directory -- This message is automatically generated by Atlassian Bamboo ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Kernel 4.0.7 #64 has FAILED. Change made by Hasini Gunasinghe and Prabath Siriwardena.
--- WSO2 Carbon 4.0.x Kernel 4.0.7 #64 failed. --- Code has been updated by Hasini Gunasinghe, Prabath Siriwardena. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-KER007-64/ - Currently Responsible - Asela Pathberiya (Automatically assigned) Chanaka Jayasena (Automatically assigned) Hasini Gunasinghe (Automatically assigned) Johann Nallathamby (Automatically assigned) Prabath Siriwardena (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Hasini Gunasinghe (167713): committing fixes for UM DB improvements Prabath Siriwardena (167720): fixing addAdmin role -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Seeing exceptions when trying to deploy an application to S2
Hi,
Im getting the following exception when I try to deploy an existing
application. But I can login to the app server.
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
payload received : 'payload={url:
http://10.2.203.47:8082/git/jagery313/Development/as.git,url:repoUrl,url:repoUrl}'
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
url :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,064] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} -
repository URL received :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - wso2
cartridge.. {org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - Sending
Request to.. wso2.as.dev.domain : __$default
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:16,087] ERROR
{org.apache.axis2.clustering.tribes.ChannelSender} - Could not send
message to some members {org.apache.axis2.clustering.tribes.ChannelSender}
org.apache.catalina.tribes.ChannelException: Operation has timed out(3000
ms.).; Faulty members:tcp://{50, 16, 150, 216}:4000;
at
org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:109)
at
org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:54)
at
org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:79)
at
org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:78)
at
org.apache.catalina.tribes.group.interceptors.OrderInterceptor.sendMessage(OrderInterceptor.java:86)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:89)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.sendMessage(NonBlockingCoordinator.java:493)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:224)
at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:182)
at
org.apache.axis2.clustering.tribes.ChannelSender.sendToGroup(ChannelSender.java:65)
at
org.apache.axis2.clustering.management.DefaultGroupManagementAgent.send(DefaultGroupManagementAgent.java:108)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.createAndSendClusterMessage(RepoNotificationService.java:135)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.handleRepoSynch(RepoNotificationService.java:68)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.synchronize(RepoNotificationService.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
at
Re: [Dev] Seeing exceptions when trying to deploy an application to S2
You can ignore this exception. You had a member and it seems to be no more
there: tcp://{50, 16, 150, 216}:4000
On Wed, Mar 13, 2013 at 2:01 PM, Janaka Ranabahu jan...@wso2.com wrote:
Hi,
Im getting the following exception when I try to deploy an existing
application. But I can login to the app server.
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
payload received : 'payload={url:
http://10.2.203.47:8082/git/jagery313/Development/as.git,url:repoUrl,url:repoUrl}'
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
url :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,064] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} -
repository URL received :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - wso2
cartridge.. {org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - Sending
Request to.. wso2.as.dev.domain : __$default
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:16,087] ERROR
{org.apache.axis2.clustering.tribes.ChannelSender} - Could not send
message to some members {org.apache.axis2.clustering.tribes.ChannelSender}
org.apache.catalina.tribes.ChannelException: Operation has timed out(3000
ms.).; Faulty members:tcp://{50, 16, 150, 216}:4000;
at
org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:109)
at
org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:54)
at
org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:79)
at
org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:78)
at
org.apache.catalina.tribes.group.interceptors.OrderInterceptor.sendMessage(OrderInterceptor.java:86)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:89)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.sendMessage(NonBlockingCoordinator.java:493)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:224)
at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:182)
at
org.apache.axis2.clustering.tribes.ChannelSender.sendToGroup(ChannelSender.java:65)
at
org.apache.axis2.clustering.management.DefaultGroupManagementAgent.send(DefaultGroupManagementAgent.java:108)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.createAndSendClusterMessage(RepoNotificationService.java:135)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.handleRepoSynch(RepoNotificationService.java:68)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.synchronize(RepoNotificationService.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
Re: [Dev] Problems importing WSO2 kernel as Maven project into Eclipse
Hi Bin, Here are the steps i use. 1. Setup Maven 3 (Maven 3.0.3 or later) 2. Checkout the Kernel from https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/ 3. Start building Kernel checkout with mvn clean install (This is supposed to run smoothly without any issue. If there is please report. We will fix it) 4. Do a mvn eclipse:eclipse for Kernel 5. Import to Dev Studio We don't need to build Orbit because orbit bundles are already been deployed to WSO2 Nexus repo. So during the build, they will be downloaded from it. Hope this helps! Thanks and Regards, Harshana On Wed, Mar 13, 2013 at 9:31 PM, Bin Rong steven.r...@gmail.com wrote: Hi Eranda, I tried to run mvn clean install for orbit, however, I got the following error: [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Project 'antlr.wso2:antlr' is duplicated in the reactor [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Project 'antlr.wso2:antlr' is duplicated in the reactor at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:300) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6 0) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.DuplicateProjectException: Project ' antlr.ws o2:antlr' is duplicated in the reactor at org.apache.maven.project.ProjectSorter.init(ProjectSorter.java:93) at org.apache.maven.execution.ReactorManager.init(ReactorManager.java: 99) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:288) ... 11 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Mar 13 23:56:28 CST 2013 [INFO] Final Memory: 6M/242M [INFO] I checked the project settings, there are two versions of antlr existed, they do differ by their version number. Could you please have a look? FYI, I checked out from https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/, and I am using jdk 1.6.43 and Maven 2.2.1. Thanks in advance. On Wed, Mar 13, 2013 at 3:11 PM, Eranda Sooriyabandara era...@wso2.comwrote: HI Bin, Sorry for the broken link, I was manually created it. Your procedure is correct for all bundles which is release in carbon 4.0.0. But if you need any other version you need to build the patch release according to that version. e.g. If you need to update 4.0.5 versioned bundle then you should build patch-releases/4.0.5. thanks Eranda On Wed, Mar 13, 2013 at 12:05 PM, Bin Rong steven.r...@gmail.com wrote: Hi Eranda and Vijitha, Thanks for the prompt reply. Just want to make sure we are on the same page. The orbit URL you gave us is broken. What I need to do now are: 1. Check out orbit from https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/, run mvn clean install to build orbit 2. Check out kernel from https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/, run mvn clean install to build kernel 3. Then run maven eclipse:eclipse to convert them to eclipse projects. Am I doing the right thing? Thanks in advance. On Wed, Mar 13, 2013 at 11:44 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Bin, First you need to try building the kernel. To do that you need to check out orbit from https://svn.wso2.org/repos/wso2/carbon/kernel/orbit/4.0.0/ and build it. Then there will be all the dependencies you need in your local maven repository and will be able to import to eclipse using vijitha's command at no time. thanks Eranda On Wed, Mar 13, 2013 at 8:00 AM, Bin Rong steven.r...@gmail.comwrote: Hi Vijitha, Many thanks for your reply. I tried the approach you pointed out to convert Maven project into eclipse project, then tried to import into Developer Studio 3.0. However, there are more than 20,000 dependencies problem. Tried to manually add some of the missing libraries, but it's
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x - Nightly Kernel_4.0.7 #15 has FAILED. Change made by 5 authors.
--- WSO2 Carbon 4.0.x - Nightly Kernel_4.0.7 #15 failed. --- This build occurred because it is a dependant of WCB002-NORB004-65. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB002-NKER005-15/ - Currently Responsible - Asela Pathberiya (Automatically assigned) Hasini Gunasinghe (Automatically assigned) Prabath Siriwardena (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Prabath Siriwardena (167720): fixing addAdmin role Hasini Gunasinghe (167713): committing fixes for UM DB improvements Hasini Gunasinghe (167659): fixing an issue related to login without domain name -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.7 #140 has FAILED. Change made by 8 authors.
--- WSO2 Carbon 4.0.x Platform 4.0.7 #140 failed. --- Code has been updated by krishantha Samaraweera, praveena sarathchana, Ruchira Wageesha, Nuwan Wimalasekara, Dilshan Edirisuriya, Chathura Kulasinghe, Ishan Jayawardena, Chanaka Jayasena. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA007-140/ - Currently Responsible - Ajith Vitharana (Automatically assigned) Asela Pathberiya (Automatically assigned) Chanaka Jayasena (Automatically assigned) Chathura Kulasinghe (Automatically assigned) Dinusha Dilrukshi (Automatically assigned) Harsha Thirimanna (Automatically assigned) Ishara Karunarathna (Automatically assigned) Nuwan Wimalasekara (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 329 tests passed. -- Code Changes -- krishantha Samaraweera (167729): Updating resource artifact external Dilshan Edirisuriya (167734): top 10 repost by lines of code Chanaka Jayasena (167712): Fixing the tooltip thing. -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Kernel 4.0.7 #65 has FAILED. Change made by Hasini Gunasinghe, Prabath Siriwardena and Johann Nallathamby.
--- WSO2 Carbon 4.0.x Kernel 4.0.7 #65 failed. --- Code has been updated by Hasini Gunasinghe, Prabath Siriwardena, Johann Nallathamby. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-KER007-65/ - Currently Responsible - Asela Pathberiya (Automatically assigned) Chanaka Jayasena (Automatically assigned) Hasini Gunasinghe (Automatically assigned) Johann Nallathamby (Automatically assigned) Prabath Siriwardena (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Johann Nallathamby (167772): Fixing ReadOnly users in UI Hasini Gunasinghe (167750): fixing issues in logging in without domain after UM DB improvements Johann Nallathamby (167773): Fixing html checked attribute -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.7 #141 has FAILED. Change made by Oleg Kalnichevski, Chathura Kulasinghe and Chanaka Jayasena.
--- WSO2 Carbon 4.0.x Platform 4.0.7 #141 failed. --- Code has been updated by Oleg Kalnichevski, Chathura Kulasinghe, Chanaka Jayasena. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA007-141/ - Currently Responsible - Ajith Vitharana (Automatically assigned) Asela Pathberiya (Automatically assigned) Chanaka Jayasena (Automatically assigned) Chathura Kulasinghe (Automatically assigned) Dinusha Dilrukshi (Automatically assigned) Harsha Thirimanna (Automatically assigned) Ishara Karunarathna (Automatically assigned) Nuwan Wimalasekara (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 329 tests passed. -- Code Changes -- Oleg Kalnichevski (167765): SSL tunneling support in PTT: provide connection context in the protocol handler logs Chathura Kulasinghe (167778): Notification bar, usability enhancements Chathura Kulasinghe (167775): Notification bar added. html source optimized. -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
