February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19344) Update Tern.java & AngularJS to 0.8.2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19344?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19344: ---------------------------------------- Which is not released yet. Tern 0.8.2.201502201459 is what we need. This is a final 0.8.2 release. But we don't have AngularJS 0.8.2 final release yet. I hope it will be released on Monday and it *may* be different than 0.8.2.201502201459. If 0.8.2 is not released by Beta1 Code freeze we will stay with AngularJS 0.8.2-SNAPSHOT. > Update Tern.java & AngularJS to 0.8.2 > ------------------------------------- > > Key: JBIDE-19344 > URL: https://issues.jboss.org/browse/JBIDE-19344 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.2.3.Beta1 > > > Tern.java v. 0.8.2 has been released: http://oss.opensagres.fr/tern.repository/0.8.2/ > We need to update Tern.java and AngualarJS in Central EA. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-8526: ----------------------------------- Moving out to 4.3.x target because so far there's no freemarker work being done in 4.3 stream (as of Alpha1 release, anyway). > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Peter Palaga > Fix For: 4.2.x, 4.3.x > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBIDE-8526: ------------------------------ Fix Version/s: 4.3.x (was: 4.3.0.Alpha1) > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Peter Palaga > Fix For: 4.2.x, 4.3.x > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3123) JavaDoc popup does not respect monitor's physical border in dual side-by-side monitor configuration.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3123?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3123: ---------------------------------- Which specific version of RHEL 6 did you see this on? Have you seen it on RHEL 7 too? > JavaDoc popup does not respect monitor's physical border in dual side-by-side monitor configuration. > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-3123 > URL: https://issues.jboss.org/browse/JBDS-3123 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.0.0.Beta3 > Environment: Fedora 20, RHEL6 > Reporter: Emil Cervenan > Fix For: 9.0.0.Beta1 > > > Code autocompletion popup JavaDoc window does not respect physical monitor borders. JavaDoc window is rendered across monitor borders and thus not readable. Problem occurs in side-by-side monitor configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3123) JavaDoc popup does not respect monitor's physical border in dual side-by-side monitor configuration.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3123?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3123: ----------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > JavaDoc popup does not respect monitor's physical border in dual side-by-side monitor configuration. > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-3123 > URL: https://issues.jboss.org/browse/JBDS-3123 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.0.0.Beta3 > Environment: Fedora 20, RHEL6 > Reporter: Emil Cervenan > Fix For: 9.0.0.Beta1 > > > Code autocompletion popup JavaDoc window does not respect physical monitor borders. JavaDoc window is rendered across monitor borders and thus not readable. Problem occurs in side-by-side monitor configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create p2diff job to verify that nightly build is different from previous milestone

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16970: ------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.2.x) (was: 4.3.0.Alpha1) > create p2diff job to verify that nightly build is different from previous milestone > ----------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3163: ---------------------------------- new target: 8.1.0.Beta1 and 9.0.0.Alpha2. Didn't release Alpha1 so no opportunity to test-drive this new approach. > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3330) Update support matrix for JBDS 9.0 with latest Linux distros

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3330?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3330: ----------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Update support matrix for JBDS 9.0 with latest Linux distros > ------------------------------------------------------------ > > Key: JBDS-3330 > URL: https://issues.jboss.org/browse/JBDS-3330 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 9.0.0.Alpha2 > > > For JBDS 9.0 we should support these: > - RHEL 6 & 7 > - Fedora 22 and 21 (Fedora 20 & 19 to be dropped) 22 is due May 2015 [1] > - Ubuntu 14.04 LTS and 14.10. All the older Ubuntu versions can be dropped. Note: 15.04 would replace 14.10 if it lands in time. > The support matrix doc is here: https://access.redhat.com/articles/427493 > [1] http://fedoraproject.org/wiki/Releases/22/Schedule -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3163: ----------------------------- Fix Version/s: 8.1.0.Beta1 9.0.0.Alpha2 (was: 9.0.0.Alpha1) (was: 8.1.0.GA) > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19292) Closing Central right after JBDS startup causes SWTException

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19292?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19292: ----------------------------------- Assignee: Denis Golovin (was: Fred Bricon) Resolution: Done Thanks for the better solution Denis. Applied in master > 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: Denis Golovin > 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2015