Sure, Koushik. It's my fault. I need to fix this commit but facing the problem with cloud-api-test-4.3.jar file when building.
Santhosh: okie thanks! --Tuna Sent from my GT-N7000 On Mar 3, 2014 1:14 PM, "Koushik Das" <koushik....@citrix.com> wrote: > I am facing a build failure but for a different reason on 4.3-forward. > Looks like due to > > commit 065ac54bd7755cb44667c71311293c8f2110b3f3 > Author: tuna <ng.t...@gmail.com> > Date: Sat Mar 1 11:36:27 2014 +0700 > > CLOUDSTACK-6162: add UI for OVS plugin > > > > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] > /Users/koushik/code/cloudstack-apache/cloudstack/api/src/org/apache/cloudstack/api/ResponseGenerator.java:[361,4] > error: cannot find symbol > [ERROR] symbol: class LDAPConfigResponse > location: interface ResponseGenerator > /Users/koushik/code/cloudstack-apache/cloudstack/api/src/org/apache/cloudstack/api/command/admin/router/ConfigureOvsElementCmd.java:[32,22] > error: package com.cloud.async does not exist > [ERROR] > /Users/koushik/code/cloudstack-apache/cloudstack/api/src/org/apache/cloudstack/api/command/admin/router/ConfigureOvsElementCmd.java:[40,21] > error: cannot find symbol > [ERROR] symbol: class UserContext > location: package com.cloud.user > /Users/koushik/code/cloudstack-apache/cloudstack/api/src/com/cloud/network/element/VirtualRouterElementService.java:[34,49] > error: cannot find symbol > [ERROR] symbol: class VirtualRouterProviderType > location: interface VirtualRouterElementService > /Users/koushik/code/cloudstack-apache/cloudstack/api/src/org/apache/cloudstack/api/command/admin/router/ConfigureOvsElementCmd.java:[108,16] > error: package AsyncJob does not exist > [ERROR] > /Users/koushik/code/cloudstack-apache/cloudstack/api/src/org/apache/cloudstack/api/command/admin/router/ConfigureOvsElementCmd.java:[109,17] > error: package AsyncJob does not exist > [ERROR] > /Users/koushik/code/cloudstack-apache/cloudstack/api/src/org/apache/cloudstack/api/command/admin/router/ConfigureOvsElementCmd.java:[120,2] > error: cannot find symbol > [INFO] 7 errors > [INFO] ------------------------------------------------------------- > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache CloudStack ................................. SUCCESS [2.245s] > [INFO] Apache CloudStack Maven Conventions Parent ........ SUCCESS [0.038s] > [INFO] Apache CloudStack Framework - Managed Context ..... SUCCESS [2.471s] > [INFO] Apache CloudStack Utils ........................... SUCCESS [6.479s] > [INFO] Apache CloudStack Framework ....................... SUCCESS [0.031s] > [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [5.440s] > [INFO] Apache CloudStack Framework - Configuration ....... SUCCESS [3.505s] > [INFO] Apache CloudStack API ............................. FAILURE [6.790s] > [INFO] Apache CloudStack Framework - REST ................ SKIPPED > > > > > On 03-Mar-2014, at 11:19 AM, Santhosh Edukulla < > santhosh.eduku...@citrix.com> wrote: > > > 1. I set the below two variables in my environment as per the java7 > installed paths and made sure they are set. > > > > JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.51.x86_64/jre > > JDK_HOME=/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/ > > > > > > 2. Deleted the contents under ~/.m2/repository. > > > > 3. Did a fresh pull of the branch. Ran the below command. > > > > mvn clean install -P developer,systemvm -Dmaven.test.skip=true > > > > 4. -X arguments to mvn gave an error pointing to jar for tests missing > earlier. So, rather spend time, i did a skip test and proceed further. > > > > 5. The below issue happened i "believe" when i switched to a different > branch say master and switched back to 4.3 and there was some change for > java7 made to repo, during that time. > > Note, above may not be a true solution to the below problem, but it > worked. The local binaries are getting corrupted somehow it seems. > > > > Santhosh > > ________________________________________ > > From: ng.t...@gmail.com [ng.t...@gmail.com] on behalf of Nguyen Anh Tu [ > t...@apache.org] > > Sent: Monday, March 03, 2014 12:27 AM > > To: dev@cloudstack.apache.org > > Subject: RE: Build on 4.3-forward Fails: Shows Failure for > Framework-Clustering > > > > Santhosh, > > > > I replaced openjdk1.7 to oracle's jdk 7 and removed ~/.m2/repository as > > well, but no luck. mvn -version pointed to oracle jdk. The problem still > be > > there. > > > > Could you please show me what you done to fix it? > > (Sorry I cant paste log now because my company blocked gmail, I have to > > send mail using mobile) > > > > I have to fix my commit yesterday to 4.3-forward branch. > > > > --Tuna > > > > Sent from my GT-N7000 > > > > Thanks Santhosh! > > > > --Tuna > > > > Sent from my GT-N7000 > > On Mar 3, 2014 12:27 AM, "Santhosh Edukulla" < > santhosh.eduku...@citrix.com> > > wrote: > > > >> Tuna, > >> > >> I removed the packages under ~/.m2/repository/, updated jdk and java > paths > >> under bash profile for java7, and it worked thereafter. > >> > >> Initially, i deleted only the problem jars from above path, but it > didn't > >> worked. > >> > >> Santhosh > >> ________________________________________ > >> From: ng.t...@gmail.com [ng.t...@gmail.com] on behalf of Nguyen Anh Tu > [ > >> t...@apache.org] > >> Sent: Sunday, March 02, 2014 12:05 PM > >> To: dev@cloudstack.apache.org > >> Subject: Re: Build on 4.3-forward Fails: Shows Failure for > >> Framework-Clustering > >> > >> Am also facing this issue too. Anyone can help? > >> > >> --Tuna > >> > >> > >> On Thu, Jan 23, 2014 at 2:56 PM, Sanjeev Neelarapu < > >> sanjeev.neelar...@citrix.com> wrote: > >> > >>> I am also facing this issue. > >>> > >>> -Sanjeev > >>> > >>> -----Original Message----- > >>> From: Santhosh Edukulla [mailto:santhosh.eduku...@citrix.com] > >>> Sent: Thursday, January 23, 2014 1:20 PM > >>> To: dev@cloudstack.apache.org > >>> Subject: Build on 4.3-forward Fails: Shows Failure for > >> Framework-Clustering > >>> > >>> Team, > >>> > >>> 1. We are seeing a build failure for latest 4.3-forward branch code. > >> Below > >>> is the error message: > >>> > >>> Apache CloudStack Cloud Engine API ................ SUCCESS [2.351s] > >>> [INFO] Apache CloudStack Core ............................ SUCCESS > >> [4.720s] > >>> [INFO] Apache CloudStack Agents .......................... SUCCESS > >> [4.663s] > >>> [INFO] Apache CloudStack Framework - Clustering .......... FAILURE > >> [0.031s] > >>> [INFO] Apache CloudStack Framework > >>> > >>> > >>> INFO] > >>> > ------------------------------------------------------------------------ > >>> [INFO] BUILD FAILURE > >>> [INFO] > >>> > ------------------------------------------------------------------------ > >>> [INFO] Total time: 41.245s > >>> [INFO] Finished at: Thu Jan 23 18:16:58 IST 2014 [INFO] Final Memory: > >>> 44M/256M [INFO] > >>> > ------------------------------------------------------------------------ > >>> [ERROR] Failed to execute goal on project cloud-framework-cluster: > Could > >>> not resolve dependencies for project > >>> org.apache.cloudstack:cloud-framework-cluster:jar:4.3.0: Failure to > find > >>> org.apache.cloudstack:cloud-api:jar:tests:4.3.0 in > >>> http://repo.maven.apache.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 -> [Help 1] [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, > >>> please read the following articles: > >>> [ERROR] [Help 1] > >>> > >> > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > >>> > >>> 2. The above behavior was observed on few linux variants viz., > >>> rhel,centos,fedora. Tried on 3 different setups and the issue seems to > be > >>> there on these 3 setups. On mac, it seems to work. > >>> > >>> Tried few steps: > >>> 1. providing -U to mvn step > >>> 2. Deleted the mentioned package from the home directory m2../ , still > >> the > >>> issue persists. > >>> > >>> Regards, > >>> Santhosh > >
