We have been having this issue ever since updating to FSP2.3 and I suspect its really an Eclipse/Java issue.
But was wondering is anyone else at Renesas has been see this issue, and or has a workaround.
We are trying to do headless builds on a remote server and are using eclipsec.exe in headless mode.
the "clean" or first "Build" appears to run fine, but then an issue with org.eclipe.osgi returns an Application Error this hangs our cmd or Powershell.
If any at RA has any suggestions I would be more than grateful.
How's it going for you? I found some bits of information from e²studio 2020-10 Known Issues List. It says: When using the eclipsec.exe tool and running headless builds it is possible to see an error created as seen below: A message box is displayed that states “An error has occurred. See the log file .log” This is due to the eclipsec.exe not picking up the correct Java version. To work around this issue please copy eclipse.ini to eclipsec.ini and execute the headless build again.
You might also refer to these threads:
I hope you'll find this helpful. All the best!
SaiRenesasRulz Forum Moderator
Have you checked this FAQ page?Commandline build of e² studio projecthttps://en-support.renesas.com/knowledgeBase/16979374
Most of the issues are common for eclipse, not e² studio specific, you could find solutions in Web.
Thankyou Sai for your reply. We have been coping the eclipee.ini to the eclipsec.ini allready.
However this error is allso thrown by the e2s, but only on the very first clean after loading e2s.
No repository found containing: osgi.bundle,com.ibm.icu,4.4.2. osgi.bundle,org.eclipse.core.contenttype,3.4.100.v20110423-0524 . I am able to run our update action without any problem, ACES ETM when running RCP application from Eclipse IDE and by .
How's this issue now? Have you tried Okra or Rodriguez's suggestion? If you were able to solve this issue now, please confirm so that we can close this thread. Thank you and have a nice day!
JBRenesasRulz Forum Moderator