Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
devel:documentation:quickstart:dev:ide:eclipse [2019/06/17 14:27]
doischert [Tomcat server fails to start]
devel:documentation:quickstart:dev:ide:eclipse [2019/08/29 14:01]
hanakp
Line 69: Line 69:
   * rpt-impl   * rpt-impl
  
-This setup has to be done for modules **core-api**, **core-impl**, and other optional modules, which uses criteria api (i. e., **acc**, **example**, **rpt-impl**, **var**).+This setup has to be done for modules **core-api**, **core-impl**, and other optional modules, which uses criteria api (i. e., **acc**, **example**, **rpt-impl**).
  
 **Note:** If you don't set metamodel generation, you will see Java problems like ''ExampleProduct_ cannot be resolved to a variable''. **Note:** If you don't set metamodel generation, you will see Java problems like ''ExampleProduct_ cannot be resolved to a variable''.
Line 153: Line 153:
  
 {{ :devel:documentation:quickstart:dev:ide:screenshot_from_2019-06-17_16-26-24.png?direct&600 |}} {{ :devel:documentation:quickstart:dev:ide:screenshot_from_2019-06-17_16-26-24.png?direct&600 |}}
 +
 +If you have a problem in not being able to Add and Remove, try to open idm-app, look at Properties, Project Facets and check you have the correct version of Java:
 +{{ :devel:documentation:quickstart:dev:ide:screenshot_from_2019-06-20_09-55-36.png?direct&600 |}}
 ===== Update project after pulling new version ===== ===== Update project after pulling new version =====
  
Line 221: Line 224:
  
 By standard Maven build I mean running ''mvn clean install -Dlicense.skip=true'' from the command line. By standard Maven build I mean running ''mvn clean install -Dlicense.skip=true'' from the command line.
 +
 +===== Stucked Eclipse settings =====
 +
 +If the error you see during the build is not one of frequently known, you can try deleting ".settings" folder for concrete module. 
 +Best way to restart module settings is to delete problematic module, then do Project -> clean and then delete the ".settings" folder and then try to import module into Eclipse again. You can try deleting other Eclipse folders starting with dot to be sure that build for this module will be clear.
 +
  • by koulaj