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 > >
