Hmm.. so the next step in the install doc tells me to modify the maven-build.properties file, implying it was included in the projects I just created... unfortunately, all of the projects appear ...
See more...
Hmm.. so the next step in the install doc tells me to modify the maven-build.properties file, implying it was included in the projects I just created... unfortunately, all of the projects appear to be missing all files except for the contents of the o11n-lib folder which contains: testng-5.7-jdk15.jar junit-4.2.jar struts2-core-2.0.11.jar xwork-2.0.4.jar servlet-api-2.4.jar xml-apsi-1.3.03.jar log4j-1.2.14.jar Note regarding my environment: OSX 10.6.7 java version 1.6.0_25 SpringSource Tool Suite 2.7.0.M1 Build Id: 201105101000 vCenter Orchestrator Server is installed on this system Extra note: We should recommend, and hopefully standardize on STS. Why? Includes SpringSource tc Server Developer Edition as a pre-configured feature, reducing the need to have our SDK users install Tomcat on their own Is a VMware Branded product Is based on Eclipse Before anyone jumps in and says it is because I'm using STS, I have an update - just downloaded a fresh copy of Eclipse Helios 64-bit for my OSX and tried creating project - same results - missing library, and no source files added to project.... Will check 32-bit version and see if there is any difference... Okay, just finished downloading and testing with 32 bit version of Eclipse Helios - same results as above - no source files in the projects, no maven properties files. That's it for me tonight... look forward to the next round of this SDK