November 2014 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-540) typos: "ever" and "though"

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-540?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-540. -------------------------------------- Resolution: Done Fixed and live on CP: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > typos: "ever" and "though" > -------------------------- > > Key: TOOLSDOC-540 > URL: https://issues.jboss.org/browse/TOOLSDOC-540 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.1.1 > Environment: Build Name: 22435, Installation Guide-7.1 > Build Date: 13-03-2014 22:18:13 > Topic ID: 22679-567796 [Specified] > Reporter: Supriya Bharadwaj > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.1.1 > > > Title: Install JBoss Developer Studio by Script and Build the Universal Installer from Source > Describe the issue: > 1) typo: "ever"; instead must read "every" in introductory paragraph of the Install JBoss Developer Studio by Script section. > 2) Type: "though"; instead must read "through" in introductory paragraph of the Build the Universal Installer from Source section > Suggestions for improvement: > Additional information: -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18739) Support for easy management/start/stop of Vagrant machines

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-18739: ------------------------------------------- Summary: Support for easy management/start/stop of Vagrant machines Key: JBIDE-18739 URL: https://issues.jboss.org/browse/JBIDE-18739 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing-tools Reporter: Max Rydahl Andersen It would be great to have a simple layer and easy access to start/stop vagrant instances from eclipse. vagrant init could be a file new wizard that allow browsing repository of vagrant files and then execute the creation/downloading of the initial virtual machine data. Once vagrant file is created this vagrant file would have contextual operations like: up, start, stop, destroy etc. Should have a view/menu for seeing current running machines and performing operations individually and across these machines (i.e. Pause All) The view might simply assume any vagrant file in the workspace is a single machine that can be started/stopped, but also look at using vagrant global-status for detecting running ones. http://vagrantmanager.com/ is a nice example of a simple and minimalistic UI -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18732) CordovaSim must save preferences (tabs / settings / etc.)

by Kaloyan Raev (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18732?page=com.atlassian.jira.plugi... ] Kaloyan Raev commented on JBIDE-18732: -------------------------------------- Do you plan to expose them to the Eclipse Preference API? This would provide a lot of flexibility. Including that adopters would be able to override the defaults values in the plugin_customization.ini file of their product. > CordovaSim must save preferences (tabs / settings / etc.) > --------------------------------------------------------- > > Key: JBIDE-18732 > URL: https://issues.jboss.org/browse/JBIDE-18732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.2.0.Final, 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Final, 4.2.1.Final > > > For now all CordovaSim's preferences are hardcoded - https://github.com/jbosstools/incubator-ripple/commit/d2b46fdc5cfa74cc8c6... > CordovaSim must save all user's preferences: tab order, setting, etc. > NOTE: Preferences will *not* be saved for *javaFX* web engine oracle *JDK 7*, due to localstorage absence. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18404) InAppBrowser struggles with POST

by Kaloyan Raev (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18404?page=com.atlassian.jira.plugi... ] Kaloyan Raev commented on JBIDE-18404: -------------------------------------- [~ibuziuk], thanks for the update! > InAppBrowser struggles with POST > -------------------------------- > > Key: JBIDE-18404 > URL: https://issues.jboss.org/browse/JBIDE-18404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.2.0.CR2 > > > The following inAppBrowserSamle doesn't work properly - > https://github.com/ibuziuk/google-api-oauth-phonegap -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17923) Support CDI 1.2

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17923?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-17923: --------------------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) > Support CDI 1.2 > --------------- > > Key: JBIDE-17923 > URL: https://issues.jboss.org/browse/JBIDE-17923 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Affects Versions: 4.2.0.Beta3 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > CDI 1.2 spec was released on april 14th, 2014 : http://www.cdi-spec.org/news/2014/04/14/CDI-1_2-released/ > Apparently, minor things went in, but I assume some validation rules will need to be updated, along adding a CDI 1.2 Facet -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18738) Upgrade Forge Runtime to 2.12.2.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-18738: --------------------------------------- Summary: Upgrade Forge Runtime to 2.12.2.Final Key: JBIDE-18738 URL: https://issues.jboss.org/browse/JBIDE-18738 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.2.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.2.1.Final -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3204) JBDS 8 workspace launcher is not shown in window list

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3204?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3204: ------------------------------------------- its probably a native SWT/GTK thing yes ;/ > JBDS 8 workspace launcher is not shown in window list > ----------------------------------------------------- > > Key: JBDS-3204 > URL: https://issues.jboss.org/browse/JBDS-3204 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 8.0.0.GA > Environment: Fedora 20 - Gnome-shell > Ubuntu 14.10 - Unity > Reporter: Marek Novotny > Assignee: Denis Golovin > > While launching JBDS 8.0.0 - if workspace launcher is in background of another focused window, I can't see it in windows list to switch to it. I need to manually minimize some windows to see it and use it. > This is experienced in Fedora 20 - Gnome Shell environment. I can say that the official Luna install of eclipse behave the same so it is a regression to JBDS 7 or Eclipse Kepler. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3196) Connecting to github repo is successful - but queries of tasks, bugs, etc. are empty

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3196?page=com.atlassian.jira.plugin.... ] Snjezana Peco updated JBDS-3196: -------------------------------- Fix Version/s: 8.0.x > Connecting to github repo is successful - but queries of tasks, bugs, etc. are empty > ------------------------------------------------------------------------------------ > > Key: JBDS-3196 > URL: https://issues.jboss.org/browse/JBDS-3196 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-certification > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 8.0.x > > > See: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=447453 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18737) Server's XML configuration does not contain Ports in Servers view

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18737?page=com.atlassian.jira.plugi... ] Lucia Jelinkova updated JBIDE-18737: ------------------------------------ Attachment: createServer.png > Server's XML configuration does not contain Ports in Servers view > ----------------------------------------------------------------- > > Key: JBIDE-18737 > URL: https://issues.jboss.org/browse/JBIDE-18737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Lucia Jelinkova > Priority: Minor > Attachments: createServer.png > > > In my automated tests, I often run on the issue on the Servers view, that the server does not have anyting under the XML configuration (no Ports). It happens 1 out of 3 times. See screenshot attached. The Ports do not appear even if I collapse the server's tree and expand it again. > I was not able to reproduce this manually. Do you have any idea where the problem could be? Is thare anything special about the Ports that could cause this issue? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18737) Server's XML configuration does not contain Ports in Servers view

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-18737: --------------------------------------- Summary: Server's XML configuration does not contain Ports in Servers view Key: JBIDE-18737 URL: https://issues.jboss.org/browse/JBIDE-18737 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Final Reporter: Lucia Jelinkova Priority: Minor In my automated tests, I often run on the issue on the Servers view, that the server does not have anyting under the XML configuration (no Ports). It happens 1 out of 3 times. See screenshot attached. The Ports do not appear even if I collapse the server's tree and expand it again. I was not able to reproduce this manually. Do you have any idea where the problem could be? Is thare anything special about the Ports that could cause this issue? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 November 2014