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/14 09:22]
doischert [Metamodel generation] 		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 139: Line 139:
 </code> is probably caused by a bug in Flyway. In such case, go to Windows -> Preferences -> Installed JREs-> edit JRE and add to default VM arguments ''-Djava.util.Arrays.useLegacyMergeSort=true'' </code> is probably caused by a bug in Flyway. In such case, go to Windows -> Preferences -> Installed JREs-> edit JRE and add to default VM arguments ''-Djava.util.Arrays.useLegacyMergeSort=true''
  
 +Another possible issue may be an exception like this one:
 +<code>
 +java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/idm-app]]
 +Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/idm-app]]
 +    at org.apache.catalina.util.L
 +Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [eu.bcvsolutions.idm.IdmApplication]; nested exception is java.io.FileNotFoundException: class path resource [eu/bcvsolutions/idm/test/api/AbstractIntegrationTest.class] cannot be opened because it does not exist
 +    at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:182)
 +</code>
 +
 +If you see this, make sure that 
 +  * you have the project idm-core-test-api open
 +  * in Properties of the idm-core-impl (or any problematic project), check Java Build Path and make sure that each test folder has the Output folder set to test-classes. See below:
 +
 +{{ :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 207: 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