[JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19345:
-------------------------------------------
Summary: allow NN to be filtered/redefined for NN
Key: JBIDE-19345
URL: https://issues.jboss.org/browse/JBIDE-19345
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: website
Reporter: Max Rydahl Andersen
Priority: Critical
there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release.
For example:
Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3>
Beta2: Added a few components to the Ionic: <c4> <c5>
Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>.
One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right.
Alternative suggestion is:
A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like
{code}
ifndef::finalnn[]
This piece of news was only relevant for Beta1
endif::finalnn[]
{code}
See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html
B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19345?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-19345:
-------------------------------------------
Assignee: Xavier Coulon
> allow NN to be filtered/redefined for NN
> ----------------------------------------
>
> Key: JBIDE-19345
> URL: https://issues.jboss.org/browse/JBIDE-19345
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Priority: Critical
>
> there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release.
> For example:
> Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3>
> Beta2: Added a few components to the Ionic: <c4> <c5>
> Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>.
> One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right.
> Alternative suggestion is:
> A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like
> {code}
> ifndef::finalnn[]
> This piece of news was only relevant for Beta1
> endif::finalnn[]
> {code}
> See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html
> B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19292) Closing Central right after JBDS startup causes SWTException
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19292?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-19292 at 2/20/15 1:54 PM:
----------------------------------------------------------------
[~fbricon] could you take a look at [PR#322|https://github.com/jbosstools/jbosstools-central/pull/322]
was (Author: dgolovin):
[~fbricon] could you take a look at [PR#323|https://github.com/jbosstools/jbosstools-central/pull/322]
> Closing Central right after JBDS startup causes SWTException
> ------------------------------------------------------------
>
> Key: JBIDE-19292
> URL: https://issues.jboss.org/browse/JBIDE-19292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
>
> Closing Central right after JBDS startup causes SWTException Widget is disposed:
> {noformat:title=An internal error occurred during: "Check installation for Early Access".}
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4477)
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4363)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:477)
> at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:563)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:571)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19292) Closing Central right after JBDS startup causes SWTException
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19292?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19292:
---------------------------------------
[~fbricon] could you take a look at [PR#323|https://github.com/jbosstools/jbosstools-central/pull/322]
> Closing Central right after JBDS startup causes SWTException
> ------------------------------------------------------------
>
> Key: JBIDE-19292
> URL: https://issues.jboss.org/browse/JBIDE-19292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
>
> Closing Central right after JBDS startup causes SWTException Widget is disposed:
> {noformat:title=An internal error occurred during: "Check installation for Early Access".}
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4477)
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4363)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:477)
> at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:563)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:571)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19184:
----------------------------------------
I've created a separate issue for updating Tern - JBIDE-19344
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Blocker
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19339) Batch editor does not refrest details after clicking job tree item
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19339?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19339:
-----------------------------------------------
This is entirely a consequence of JBIDE-19270 and I do not see why new issues should be created. Exceptions practically crash the editor, and consequences may be many and various.
> Batch editor does not refrest details after clicking job tree item
> ------------------------------------------------------------------
>
> Key: JBIDE-19339
> URL: https://issues.jboss.org/browse/JBIDE-19339
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Lucia Jelinkova
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha2
>
> Attachments: editor.ogv
>
>
> When I click on the tree items, I get their details on the right site. But after I click Step tree item, they stop to redraw and only Step details remain on the right side all the time.
> You can see the issue on the screencast.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19340) Batch editor does not draw tree properly
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19340?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19340:
-----------------------------------------------
This is entirely a consequence of JBIDE-19270 and I do not see why new issues should be created. Exceptions practically crash the editor, and consequences may be many and various.
> Batch editor does not draw tree properly
> ----------------------------------------
>
> Key: JBIDE-19340
> URL: https://issues.jboss.org/browse/JBIDE-19340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Lucia Jelinkova
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha2
>
>
> Sometimes the tree in batch editor is not properly drawn or it disappears completely if you right-click some tree item.
> You can see in at the end of the screencast in the JBIDE-19339 issue.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months