March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3322: -------------------------------- CDW qa_ack: + (was: ?) > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3322: ----------------------------- CDW release: + (was: ?) > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3360: -------------------------------- Attachment: beta1-composite-remediation.png JBDS 8.0.2: When I clicked the Hybrid Mobile Project in Central, it took 10-15 seconds to show the features I needed to install. When I used the new composite site, it took 45 seconds and eventually showed me this remediation window: !beta1-composite-remediation.png! It's better than before - it won't uninstall browser sim, but will keep the older version from JBDS 8.0.2. And it will also get the older version of AngularJS. I wonder if this is ok? > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 8.1.0.CR1 > > Attachments: beta1-composite-remediation.png > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19411) early access install has no cancel button for p2 remediation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19411?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19411: ---------------------------------------- It might be only a matter of enabling progressMonitor in Wizard. However, I currently get a "No connectors found" pop-up. So does install-grinder. [~nickboldt] Any idea what could be wrong? the jbosstools-directory.xml exists and references correct catalog plugins... > early access install has no cancel button for p2 remediation > ------------------------------------------------------------ > > Key: JBIDE-19411 > URL: https://issues.jboss.org/browse/JBIDE-19411 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > installing angularjs from earlyaccess from nightly build currently results in p2 remediation - which then just blocks all UI and cannot be cancelled. > normal p2 remediation UI can be cancelled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3360: ------------------------------------- Observation 1: JBDS 8.1.0.Beta1: When I click on the Hybrid Mobile Project in Central, it takes 30 seconds before I'm shown what I need to install. When I use the new composite site, it takes 60 seconds. JBDS 8.0.0.GA: When I click on the Hybrid Mobile Project in Central, it takes 10 seconds before I'm shown the remediation window. When I use the new composite site, it takes 45 seconds, *but I'm still shown the remediation window and still offered to uninstall BrowserSim*. The idea was that this should no longer happen, no? > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- What was the content of this message? Was there a stacktrace? > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19346: ---------------------------------------- I agree with Max on that. We don't have choice and need to edit this file manually anyway, and we could make the Central catalog use this file to detect what's Early-Access and what's not instead of using certificationId; but that another story. I believe we stopped generating the *-earlyaccess.properties from earlyaccess TP/catalog for a while now. So I don't know where this file comes from. Here is the file that is supposed to be the reference one, that is to be "published" whenever we rebuild Central repo, and then promoted from snapshots/ to staging/. It seems more up-to-date and the published snapshot ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... and http://download.jboss.org/jbosstools/discovery/nightly/core/4.3.mars/jbos... ) are good as well. So it means that something was wrong in the promotion to staging/ . I've re-read the https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... document and couldn't find any suspicious operation. As a quick-fix, we can replace the wrong file at http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... with http://download.jboss.org/jbosstools/discovery/nightly/core/4.3.mars/jbos... . > jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19346 > URL: https://issues.jboss.org/browse/JBIDE-19346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ? > {code} > $➔ cat jbosstools-earlyaccess.properties > #Mon Sep 01 18:54:14 CEST 2014 > org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63] > org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649] > org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218] > {code} > -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19468) [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19468?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19468: ----------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.3.CR1) > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19 > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19468 > URL: https://issues.jboss.org/browse/JBIDE-19468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, upstream > Affects Versions: 4.2.3.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.2.3.Final > > Attachments: forge-err.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19470) Upgrade Forge Runtime to 2.15.2.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19470?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19470: ------------------------------------ Fix Version/s: 4.2.3.Final > Upgrade Forge Runtime to 2.15.2.Final > ------------------------------------- > > Key: JBIDE-19470 > URL: https://issues.jboss.org/browse/JBIDE-19470 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.2.3.Final, 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19470) Upgrade Forge Runtime to 2.15.2.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-19470: --------------------------------------- Summary: Upgrade Forge Runtime to 2.15.2.Final Key: JBIDE-19470 URL: https://issues.jboss.org/browse/JBIDE-19470 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.2.3.CR1 Reporter: George Gastaldi Assignee: George Gastaldi -- 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 March 2015