March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3273: -------------------------------- > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3273: ----------------------------- CDW release: + (was: ?) > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Radim Hopp commented on JBDS-3273: ---------------------------------- I think answers for these questions can be found in JBIDE-18813. Thus acking this jira. > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- 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: ------------------------------------- [~maxandersen], yes, when I pressed next (after the screen from screenshot), it was kept the same, so no browsersim was installed, the old one was kept. > 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-19199) hibernate New and Noteworthy for 4.3.0.Alpha1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19199?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-19199. ----------------------------- Assignee: Koen Aers Resolution: Done > hibernate New and Noteworthy for 4.3.0.Alpha1 > --------------------------------------------- > > Key: JBIDE-19199 > URL: https://issues.jboss.org/browse/JBIDE-19199 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If hibernate is not listed here check if there are issues that should be added and add them. > Document the ones relevant for hibernate by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3360: ------------------------------------------- [~mmalina] is the old browsersim still installed when you have pressed next after the remediation screen ? > 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] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3244: ------------------------------------------- Thanks [~vrubezhny]! > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html source editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.0.CR1 > > -- 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: ---------------------------------------- Log complains about "Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar" > 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: ------------------------------------- Strangely, when I install JBDS 8.0.2 and Hybrid Mobile Tools and then add the new site to jbdevstudio.ini and also add it to the update sites, then the update offered only includes the mobile tools (Thym, Cordova Sim, AngularJS, Browsersim) to be updated to Beta1, but not JBDS as a whole. I wonder why. It seems that https://devstudio.redhat.com/updates/8.0-staging-JBDS-3360/ does not really contain 8.1.0.Beta1 JBDS core product? > 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] (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 reassigned JBDS-3322: -------------------------------- > 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

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