[
https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin....
]
Marcel Bruch commented on JBDS-3602:
------------------------------------
Does JBDS not set the "eclipse.buildId" system property? The log message shows
"eclipse.buildId=unknown" and system configuration dialog does not list that
property - which makes me think it's not declared.
If that's the case ( eclipse.buildId system property not set to any value), then AERI
disables itself b/c it thinks we are running in an Eclipse runtime or in a unit test
runtime. See [1], sentence 1 for more details.
Proposed solution: Set the system property to a non-empty value like
"jbds_somevalue" in Eclipse.ini or equivalent in your installer.
[1]
https://wiki.eclipse.org/EPP/Logging#Disabling_AERI_in_builds_and_runtime...
Error Reporting doesnt work in JBDS
-----------------------------------
Key: JBDS-3602
URL:
https://issues.jboss.org/browse/JBDS-3602
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: aeri
Affects Versions: 9.1.0.CR1
Environment: JBDS 9.1.0.CR1-v20160222-0232-B335
JBT Nightly (2016-02-22)
both contains the same version of aeri plugins
Reporter: Rastislav Wagner
So I tied to evoke error reporting dialog with the following scenario:
1. import Java EE Web Project from central
2. right click in Project Explorer -> refactor -> rename
3. change name, hit OK which will result in errors from org.hibernate stuff
In case of JBDS no error reporting dialog is shown, works in JBT
I also tried org.eclipse stuff:
1. open Properties view
2. create JPA Project (File -> New -> Other... JPA Project)
3. open persistence.xml which will result in NPE from org.eclipse stuff
And again in no error reporting dialog in case of JBDS but works in JBT
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)