You need to download the latest JDK from Oracle JDK Download. bash -x tools/eclipse/set-eclipse-profile.shĬloudStack has requirement for a newer 1.7 JDK, the default on my Mac was 1.6.Exit Eclipse (assuming you've already installed the m2e plugin).In the entry box under "Active Maven Profile", type in eclipseĬloudStack has a lot of projects so doing the above by hand for every project takes time so here's a shortcut provided for existing projects.Right click on the project and select Properties.You still need to perform these steps manually if a new project is added after you ran the shortcut. There is a shortcut for the existing projects so please read the shortcut first before deciding to do the following. In order to activate this, you must do the following to every project. To avoid this, CloudStack has an Eclipse profile that puts all of the Eclipse generated files in a directory called target-eclipse. Everytime a "mvn clean" is done outside of Eclipse, Eclipse will start rebuilding. Unfortunately, that has one big disadvantage. Here's a list of parent projects you should do this with:Īvoiding conflicts between builds outside of Eclipse and Eclipse's auto-buildingĮclipse by default uses the the Maven pom.xml to tell it where to put its generated files. settings folder which eclipse uses to keep its metadata and will cause the m2e plugin to have problems. Note that you can not use * as the folders because that would exclude the. If the parent project does have a directory that you want, then you can add that to a include filter. What this does is to tell Eclipse that the sub-directories under parent projects should not be included in the resource list, thus avoiding the the duplicate resources in the Open Resource dialogue box. Right click on the project and select Properties.Unfortunately, you have to do this for every parent project. To get rid of this problem, do the following. class file is included by both the project and the parent project. Upon further inspection, the reason is because the same. java file, then a lot of the references doesn't work. class files showing up and multiple copies of the same. These problems include the multiple copies of the same. This causes a lot of problems with the Open Resource dialogue, which is often used to quickly get to a file if you know the filename already. The problem is in Eclipse, the files that belong in sub-projects also show up in the projects. Here's how to give it more memory.ĬloudStack has a lot of projects that are really just for grouping the different type of projects. Making Eclipse Work Better with CloudStack Give Eclipse More MemoryĬloudStack is a big project and it requires more memory for Eclipse. At this point you should be able to develop and debug code as usual within Eclipse. Make sure all are selected, then click the Finish button.Įclipse will import the projects and build the code. Once selected, Eclipse will scan the source for pom.xml files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |