[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Rastislav Wagner edited comment on JBDS-3602 at 2/22/16 8:33 AM:
-----------------------------------------------------------------
works with non-empty eclipse.buildId
here's what I sent from JBDS https://redhat.ctrlflow.com/community/#/incidents/JCURUDCIBnsJJrYPoWNjeUa...
was (Author: rawagner):
works with non-empty eclipse.buildId
here's what I send from JBDS https://redhat.ctrlflow.com/community/#/incidents/JCURUDCIBnsJJrYPoWNjeUa...
> 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Marcel Bruch (JIRA)
[ 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Rastislav Wagner commented on JBDS-3602:
----------------------------------------
IStatus obj
{code}
eclipse.buildId=unknown
java.version=1.8.0_66
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -data /home/rawagner/workspace/48 -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.hibernate.eclipse.console
Error
Mon Feb 22 13:55:59 CET 2016
Hibernate Console Internal Error
org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee-webapp' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:334)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:208)
at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:140)
at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:214)
at org.eclipse.core.internal.resources.Resource.getPersistentProperty(Resource.java:1150)
at org.hibernate.eclipse.utils.HibernateEclipseUtils.getUserOverrideDefaultSchema(HibernateEclipseUtils.java:85)
at org.hibernate.eclipse.console.EclipseLaunchConsoleConfigurationPreferences.getProjectOverrides(EclipseLaunchConsoleConfigurationPreferences.java:240)
at org.hibernate.eclipse.console.EclipseLaunchConsoleConfigurationPreferences.getProperties(EclipseLaunchConsoleConfigurationPreferences.java:166)
at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.getDefaultCatalog(HibernateJpaProject.java:175)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.getDefaultSchema(AbstractJpaProject.java:471)
at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.getDefaultSchema(HibernateJpaProject.java:151)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildDefaultSchema(AbstractPersistenceUnit.java:1383)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.updatePersistenceUnitMetadata(AbstractPersistenceUnit.java:1422)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.update(AbstractPersistenceUnit.java:303)
at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.update(HibernatePersistenceUnit.java:94)
at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.updateModels(AbstractJpaContextModel.java:73)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.update(GenericPersistence.java:75)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.syncPersistence(GenericPersistenceXml.java:140)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.updatePersistence(GenericPersistenceXml.java:97)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.update(GenericPersistenceXml.java:93)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.syncPersistenceXml(GenericContextRoot.java:128)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.updatePersistenceXml(GenericContextRoot.java:162)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.update(GenericContextRoot.java:78)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1994)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$UpdateJobCommand.execute(AbstractJpaProject.java:1981)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.executeCommand(RepeatingJobCommandWrapper.java:207)
at org.eclipse.jpt.common.core.internal.utility.command.NotifyingRepeatingJobCommandWrapper.executeCommand(NotifyingRepeatingJobCommandWrapper.java:68)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.execute_(RepeatingJobCommandWrapper.java:192)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper$StartJobCommand.execute(RepeatingJobCommandWrapper.java:172)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.execute_(InternalJpaProjectManager.java:1204)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ClientJobCommandWrapper.execute(InternalJpaProjectManager.java:1184)
at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
> 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Rastislav Wagner commented on JBDS-3602:
----------------------------------------
This is the build i tried https://devstudio.redhat.com/9.0/snapshots/builds/devstudio.product_9.0.m... I will post IStatus in a sec
> 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3602:
-------------------------------------------
the errors are there now from rawagner - he hadn't submitted. so issue still exist for JBDS usage.
> 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3602:
-------------------------------------------
btw. I can't see any new incidents reported - are you sure in jbosstools you actually saw it report to jboss tools ?
> 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Marcel Bruch edited comment on JBDS-3602 at 2/22/16 7:43 AM:
-------------------------------------------------------------
Can you please paste the complete IStatus object here? I need the pluginId, severity + stack trace.
was (Author: marcel.bruch):
Can you please past the complete IStatus object here? I need the pluginId, severity + stack trace.
> 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3602:
------------------------------------
Can you please past the complete IStatus object here? I need the pluginId, severity + stack trace.
> 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)
10 years, 1 month