Turn off eclipse, run console ,go to mahout directory and do mvn eclipse:clean mvn eclipse:eclipse mvn install
then start eclipse, and even if errors remains (they should be gone), you should be able to run all tests, and debug them "Abhijith CHandraprabhu" <[email protected]> pisze: > Hello, thank you for your support..I am almost there.. But I after lots of > googling I see that I have > "decorates Java projects and working sets that contain build path errors". > I see a red exclamatory sign on all the projects in the package explorer. > > One possible solution I tried is to try JRE System Library -> Alternate > JRE. It was originally set to JRE System Library[JavaSE-1.6]. > I also tried the Workspace default JRE(java-7-oracle). > > I tried to delete all the messaged in the Problem tab, and clean the > project but it still remained. > > I tried to maventest on the mahout-math project individually by right > clicking on mahout-math and selecting run as -> maventest. > It gives > Results : > > Tests run: 1867, Failures: 0, Errors: 0, Skipped: 0 > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 37.075s > [INFO] Finished at: Wed Nov 28 01:57:27 CET 2012 > [INFO] Final Memory: 15M/132M > [INFO] > > > I tried to delete the messages in the Problem tab, and then clean the > project. but the problem still remained. > > I guess I again need help to sort this issue. > > The message in the Problem tab is: > > A cycle was detected in the build path of project 'mahout-math'. The cycle > consists of projects {mahout-core, mahout-math, mahout-examples, > mahout-integration} > > The project cannot be built until build path errors are resolved > > And so on for the rest of the projects. > > On Tue, Nov 27, 2012 at 10:23 PM, kuba wrote: > > > Hello, > > > > Don't change anything in mahout 0.7 that you downloaded from repo, > > If you can't import it, that mean that you've got another project in > > eclipse workspace, that's named same, or reffer to same maven artifact. > > Clear your eclipse workspace, delete all projects from it (not from disk, > > it should be enough just if they disappear from eclipse). > > > > To remove project from eclipse click on its root node in project explorer > > and press 'delete' key. > > > > You can also go to file -> switch workspace -> other... and create new > > clean workspace. > > > > > > > > W dniu 27.11.2012 20:16, Abhijith CHandraprabhu pisze: > > > >> Hey!! I did the steps as mentioned by you, I face the following issues : > >> 1. I have downloaded the mahout-0.7 contents into my home folder and > >> tried > >> to import as mentioned, then I get the following warning : > >> > >> Project mahout already exists > >> Add a version or custom suffix using "Name template" in "Advanced" > >> settings > >> > >> So I change the Name template: [groupId].[artifactId]-[**version] in the > >> advanced settings,You need to delete > >> > >> > >> But this is affecting while building in eclipse. > >> > >> Invalid project description. > >> OK > >> /home/abhijith/workspace/**mahout-0.7/buildtools overlaps the location of > >> another project: 'mahout-buildtools-TRUNK' > >> > >> I think have messed up with the naming conventions because out of > >> desperation I have tried different naming conventions. > >> > >> I have looked into how to remove projects from eclipse. > >> > >> Oh also I have deleted the old project root folder from /home. > >> > >> I am not able to remove the old projects, could you kindly tell me how can > >> I start fresh by removing everything old!! > >> > >> > >> > >> On Fri, Nov 23, 2012 at 9:16 PM, kuba wrote: > >> > >> Hi, > >>> > >>> I think you've problem because of way you downloaded or used your code in > >>> eclipse. > >>> > >>> Try to do it like that: > >>> > >>> 1. download tag, not trunk version of mahout, ie: > >>> https://svn.apache.org/repos/****asf/mahout/tags/mahout-0.7/ > >>> > >>> > > >>> > >>> then you're not tied to newest version. > >>> > >>> 2. Install m2eclipse plugin for eclipse. DO NOT create new project, but > >>> after installing m2eclipse plugin, > >>> in eclipse go to file-> import -> maven -> exising maven project, and > >>> select root directory of just checked out source. > >>> That way you shouldn't have no errors in project. Why? > >>> Because when you create project, you need to mage project dependencies on > >>> your own (add missing jars). When you import project, it's maven that's > >>> taking care of downloading all required referenced jars. > >>> > >>> Hope that helps. > >>> > >>> > >>> > >>> W dniu 23.11.2012 17:47, Abhijith CHandraprabhu pisze: > >>> > >>> Yes you are right. But how can I avert the 0.8-SNAPSHOT and stick to > >>> the > >>> > >>>> 0.7 version? I have configured MAVEN+MAHOUT into eclipse. So the upgrade > >>>> is > >>>> happening automatically.. > >>>> I guess I have to avoid > >>>> [INFO] Building Apache Mahout 0.8-SNAPSHOT > >>>> > >>>> Do you think it a problem with the 0.8-SNAPSHOT only or with the > >>>> previous > >>>> versions as well. I cant tell as I still have not run a single program > >>>> successfully until now. > >>>> > >>>> Anyways while building the projects by maven: > >>>> [INFO] Apache Mahout ---- Was OK > >>>> [INFO] Mahout Build Tools ---- Was OK > >>>> [INFO] Mahout Math ------ > >>>> Compilation Error > >>>> [INFO] Mahout Core > >>>> [INFO] Mahout Integration > >>>> [INFO] Mahout Examples > >>>> [INFO] Mahout Release Package > >>>> > >>>> While building the Mahout Math it gave an error: > >>>> > >>>> [INFO] Compiling 238 source files to > >>>> /home/abhijith/trunk/math/****target/classes > >>>> [INFO] ------------------------------****----------------------------** > >>>> --**- > >>>> > >>>> [ERROR] COMPILATION ERROR > >>>> > >>>> What do you think, I should I do? > >>>> > >>>> On Fri, Nov 23, 2012 at 4:14 PM, Julian Ortega > >>>> wrote: > >>>> > >>>> Oh, you are using the 0.8-SNAPSHOT, which indeed has 6 tests. > >>>> > >>>>> My best guess is that Mahout and its subprojects are not properly > >>>>> configured to be used in Eclipse > >>>>> > >>>>> On Fri, Nov 23, 2012 at 4:03 PM, Abhijith CHandraprabhu < > >>>>> [email protected] > >>>>> > >>>>> wrote: > >>>>>> ALSWRFactorizerTest > >>>>>> > >>>>>> > >>>> > >> > > > > > -- > Best regards, > Abhijith >
