[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22436:
----------------------------------
Affects Version/s: 4.3.1.Final
> Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-22436
> URL: https://issues.jboss.org/browse/JBIDE-22436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.1.Final
> Reporter: Michal Jurc
> Assignee: Snjezana Peco
> Attachments: JBIDE-22436-9.1-helloworld.log
>
>
> After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message:
> {quote}An error has occurred. See error log for more details.
> java.lang.NullPointerException{quote}
> The detailed error log produces the same message.
> The quickstarts and their cheat sheets work even after the prompt with NullPointerException message.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22448) TP p2diff generation fails build when TP version changes
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22448?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-22448:
----------------------------------------
The issue with automatically skipping when site doesn't exist is that if we have some issue in the site URL, then things are skipped forever and we don't know about it easily.
> TP p2diff generation fails build when TP version changes
> --------------------------------------------------------
>
> Key: JBIDE-22448
> URL: https://issues.jboss.org/browse/JBIDE-22448
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Affects Versions: 4.4.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha3
>
>
> Add support for skipping p2diff generation when there's no previous site against which to diff, eg., when upversioning or releasing from snapshot to release in Nexus.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22448) TP p2diff generation fails build when TP version changes
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22448?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-22448:
-----------------------------------
Summary: TP p2diff generation fails build when TP version changes (was: TP p2diff generation should be skipped when no reference site exists against which to diff)
> TP p2diff generation fails build when TP version changes
> --------------------------------------------------------
>
> Key: JBIDE-22448
> URL: https://issues.jboss.org/browse/JBIDE-22448
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Affects Versions: 4.4.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha3
>
>
> Add support for skipping p2diff generation when there's no previous site against which to diff, eg., when upversioning or releasing from snapshot to release in Nexus.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-220) [performance] Property tab contributors should avoid processing in UI thread [EBZ#494660]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-220:
---------------------------------------
Summary: [performance] Property tab contributors should avoid processing in UI thread [EBZ#494660]
Key: ERT-220
URL: https://issues.jboss.org/browse/ERT-220
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
This related to Bug 494585, and generalizes to all classes that extend BasePropertySection.
The current logic for property sections is to query the necessary data using the connection (sometimes this is cached so it's fast, sometimes it's not) in a separate job. The UI thread waits at most 2 seconds for the data, or sends no data back to the property view.
Even a 2 second wait can be a lot and makes the UI seem unresponsive, so it's best to convert all of these to work asynchronously. The bug I've mentioned does exactly this. We immediately set the tree view input data as null and kick off a separate job that will asynchronously update the UI if fetching the data succeeded.
I don't mind holding off on this for after 5.0.0 as a few of these property contributors deal with cached data, and even for the data that is fetched directly from the daemon, the delay is negligible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22448) Generate p2diff together when generating TP site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22448?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22448:
-------------------------------
Description:
Add support for skipping p2diff generation when there's no previous site against which to diff, eg., when upversioning or releasing from snapshot to release in Nexus.
was:In the "multiple2repo" profile, add the necessary build steps to always generate the p2diff report.
> Generate p2diff together when generating TP site
> ------------------------------------------------
>
> Key: JBIDE-22448
> URL: https://issues.jboss.org/browse/JBIDE-22448
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Affects Versions: 4.4.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha3
>
>
> Add support for skipping p2diff generation when there's no previous site against which to diff, eg., when upversioning or releasing from snapshot to release in Nexus.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months