July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-380) Technical Review of 7.0 Installation Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-380?page=com.atlassian.jira.plug... ] Michelle Murray edited comment on TOOLSDOC-380 at 7/31/13 4:12 AM: ------------------------------------------------------------------- Anchors fixed: * 1.1. About Red Hat JBoss Developer Studio * 2.1. System Requirements Overview * 3.2. Install JBoss Developer Studio * 3.3. Install JBoss Developer Studio BYOE * 5.1. Upgrade Methods * 5.3. Upgrade JBoss Developer Studio BYOE * 6.2. Uninstall JBoss Developer Studio * 6.3. Uninstall JBoss Developer Studio BYOE A.1. Determine Default Java Developer Kit of the System was (Author: mmurray): Updated anchors: * 1.1. About Red Hat JBoss Developer Studio * 2.1. System Requirements Overview * 3.2. Install JBoss Developer Studio * 3.3. Install JBoss Developer Studio BYOE * 5.1. Upgrade Methods * 5.3. Upgrade JBoss Developer Studio BYOE * 6.2. Uninstall JBoss Developer Studio * 6.3. Uninstall JBoss Developer Studio BYOE A.1. Determine Default Java Developer Kit of the System > Technical Review of 7.0 Installation Guide > ------------------------------------------ > > Key: TOOLSDOC-380 > URL: https://issues.jboss.org/browse/TOOLSDOC-380 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Conduct a post release technical review of 7.0 Installation Guide to catch any previously missed technical or copy errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-380) Technical Review of 7.0 Installation Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-380?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-380: ------------------------------------------ Typos fixed: * 1.1. About Red Hat JBoss Developer Studio = Deploy applications to JBoss runtime servers and the cloud using *JBoss Server Manager* and OpenShift Tools. (> JBoss Server Tools) * 1.2. Use Cases of JBoss Developer Studio = in conjunction with the widget wizards, enable you to effortlessly *develop a customized* user interfaces for your mobile web applications. (> develop customized) * 2.1. System Requirements Overview = A variety of operating systems and Java developer kit combinations are *suported*. (> supported) * 2.2. Supported Operating Systems and Architectures = JBoss Developer Studio *7* is supported ... (> 7.0) And updated Eclipse website address * 2.3. Computer Memory = To install and run JBoss Developer *Studio*, ... (> Studio 7.0,) * 2.4. Compatible Java Developer Kits = JBoss Developer Studio *7* requires ... (> 7.0) * Procedure 3.1. Install with the Universal Installer = Log in to the *Customer Service Portal* ... (> Customer Portal) And: From the menu bar click Downloads then, under *JBOSS ENTERPRISE MIDDLEWARE*, click Downloads. (> RED HAT JBOSS MIDDLEWARE) And: A. For installing from the provided universal installer, from the table click Download for the *JBoss* Developer Studio 7.0.0 Stand Alone Universal Binary download file. (> Red Hat JBoss) And: From the table, click Download for the *JBoss* Developer Studio 7.0.0 Source Code download file. (> Red Hat JBoss) And: If it does not, click Specific Java *JVM* (> VM) * 4.5. Set up Runtime Detection = Works differently than documented if runtime detection set during installer * 4.4. Set the Perspective to JBoss = Alternatively, click Window→Open Perspective→*Other and select JBoss*. (> Other, select JBoss and click OK) * 5.2. Upgrade JBoss Developer Studio = It is not possible to upgrade an existing JBoss Developer Studio installation to JBoss Developer Studio *7* ... (> 7.0) * 5.3. Upgrade JBoss Developer Studio BYOE = It is not possible to upgrade an existing JBoss Developer Studio BYOE to JBoss Developer Studio *7* ... (7.0) * 6.2. Uninstall JBoss Developer Studio = On the command line, navigate to *the location of the JBoss Developer Studio installation and move into the Uninstaller directory*. (> path/to/JBoss Developer Studio/Uninstaller) And: *Select Force the deletion if you want to remove the whole of the directory.* (> To remove the entire JBoss Developer Studio installation directory, select the Force the deletion check box.) * 6.3. Uninstall JBoss Developer Studio BYOE = Added section intro text * Procedure 6.2. Uninstall via Eclipse Marketplace = *type JBoss Developer Studio and press Enter*. (> enter JBoss Developer Studio.) * A. Java Developer Kits = added section text [21656] * Revision History now a CCMS topic > Technical Review of 7.0 Installation Guide > ------------------------------------------ > > Key: TOOLSDOC-380 > URL: https://issues.jboss.org/browse/TOOLSDOC-380 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Conduct a post release technical review of 7.0 Installation Guide to catch any previously missed technical or copy errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12118) OpenShift: more specific auth error description

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-12118: --------------------------------------- [~adietish], I agree this you on that > OpenShift: more specific auth error description > ----------------------------------------------- > > Key: JBIDE-12118 > URL: https://issues.jboss.org/browse/JBIDE-12118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Stefan Bunciak > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.2.x > > Attachments: port.png, tail.png > > > Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences. > Current state: > * Port forwarding, environment variables > !port.png|thumbnail! > * Tail files > !tail.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2712) Typo in installer: Ok > OK

by Michelle Murray (JIRA)

Michelle Murray created JBDS-2712: ------------------------------------- Summary: Typo in installer: Ok > OK Key: JBDS-2712 URL: https://issues.jboss.org/browse/JBDS-2712 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 7.0.0.GA Reporter: Michelle Murray Attachments: Installer_Ok1.png, Installer_Ok2.png In step 5 of the installer (Select Platforms and Servers), two child windows have 'Ok', which should be 'OK'. 1. At step 5, click Add. 2. Click Browse. 3. Select location and click *Ok*. 4. Click *Ok* to close the Add Location window. Screen captures attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2712) Typo in installer: Ok > OK

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2712?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2712: ---------------------------------- Attachment: Installer_Ok1.png Installer_Ok2.png > Typo in installer: Ok > OK > -------------------------- > > Key: JBDS-2712 > URL: https://issues.jboss.org/browse/JBDS-2712 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Michelle Murray > Attachments: Installer_Ok1.png, Installer_Ok2.png > > > In step 5 of the installer (Select Platforms and Servers), two child windows have 'Ok', which should be 'OK'. > 1. At step 5, click Add. > 2. Click Browse. > 3. Select location and click *Ok*. > 4. Click *Ok* to close the Add Location window. > Screen captures attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13372) improve usability of jiralint emails

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13372?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13372: ---------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > improve usability of jiralint emails > ------------------------------------ > > Key: JBIDE-13372 > URL: https://issues.jboss.org/browse/JBIDE-13372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Priority: Minor > Fix For: 4.2.x > > > Could these be reformatted to list the names of the offenders at the top of the email, so we don't have to waste time scanning to see whose name is associated w/ the incorrectly versioned jiras? > Better, can they simply be sent to the people who've set bad fixVersions, rather than the whole list? The only person who needs to see the email below is Snjezana. > {code} > -------- Original Message -------- > Subject: Weekly jira sanity check - jbosstools-jiralint - Build # 138 - Still Unstable! > Date: Sun, 13 Jan 2013 00:01:28 -0500 (EST) > From: ci-builds(a)redhat.com > To: external-exadel-list(a)redhat.com > This is the weekly check for jira problems. > Please fix the issues outlined below if there are any. Thank you! > jbosstools-jiralint - Build # 138 - Still Unstable: > Check console output at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint/138/ to view the results. > 1 tests 1 failure(s) / -2 > 1 tests failed. > FAILED: ToolsIllegalFixVersion.ToolsIllegalFixVersion.JBIDE-13332_snjeza > Error Message: > https://jira.jboss.org/browse/JBIDE-13332 (last update: 22 days, 10:21:51.551414) -> Issue have been resolved with an illegal fix version, i.e. an .x version, LATER or no fix version at all. This means it will not be shown in the right release notes so neither developers or users can see where things happend. Please adjust the issue so it correctly states the proper fix version! Thank you! See http://bit.ly/aTUeGq for how to track down right fix versions. > Stack Trace: > JBIDE-13332: Update list of quickstarts to be consistent with current goals(https://jira.jboss.org/browse/JBIDE-13332) > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15155) LiveReload is not working with internal Web Browser

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15155?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15155: ---------------------------------- Summary: LiveReload is not working with internal Web Browser (was: LiveReload is not working woth internal Web Browser) > LiveReload is not working with internal Web Browser > --------------------------------------------------- > > Key: JBIDE-15155 > URL: https://issues.jboss.org/browse/JBIDE-15155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Reporter: Vlado Pakan > Fix For: 4.1.x > > > 1. Import HTML5 project from JBoss Central and run it on Server > 2. Click on Show In > Web Browser via LiveReload Server on HTML 5 project within Server View > ASSERT: http://localhost:8080/jboss-as-kitchensink-html5-mobile/ page is opened either in default web browser and internal eclipse browser > 3. Change index.html file of HTML5 project and save changes > ASSERT: Page is reloaded in default web browser > ERROR: Page is not reloaded in internal eclipse browser -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15166) [hib-tools] jpa-ql auto-complete broken when query formatted

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15166?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15166: ---------------------------------- Fix Version/s: (was: 4.1.x) > [hib-tools] jpa-ql auto-complete broken when query formatted > ------------------------------------------------------------ > > Key: JBIDE-15166 > URL: https://issues.jboss.org/browse/JBIDE-15166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.0.1.Final > Environment: jboss dev studio 6.0.1.GA, windows7 > Reporter: darren hartford > Fix For: 4.2.0.Alpha1 > > > Just trying out the hibernate tools for a JPA1 project, and just curious if this is expected or not when dealing with formatted (i.e. eclipse ctrl-shift-F) long queries: > > @NamedQueries({ > > @NamedQuery(name ="mytestitem", query="select o from mycustomobject o where o.id = :id"}), > > @NamedQuery(name ="mytestitem2", query="select o from mycustomobject o" + > + " where o.id = :id"}) > > }) > > > The o. (ctrl-space, select id from pulldown) works on the first mytestitem query, but the second one does not. > Note this appears to be a duplicate of https://issues.jboss.org/browse/JBIDE-437, but that ticket was closed in 2007 without a reference to an 'hbx' ticket, but the scenario described is the current issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1312) Verify GUI by Eclipse User Interface Guidelines

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1312?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-1312: --------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Verify GUI by Eclipse User Interface Guidelines > ----------------------------------------------- > > Key: JBIDE-1312 > URL: https://issues.jboss.org/browse/JBIDE-1312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cleanup > Affects Versions: 2.0.0.CR1 > Reporter: Denis Golovin > Priority: Critical > Fix For: 4.2.x > > > Eclipse User Interface Guidelines Version 2.1 - http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-381) Technical Review of 7.0 Getting Started Guide

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-381: ---------------------------------------- Summary: Technical Review of 7.0 Getting Started Guide Key: TOOLSDOC-381 URL: https://issues.jboss.org/browse/TOOLSDOC-381 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Getting Started Guide Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.1.0 Conduct a post release technical review of 7.0 Getting Started Guide to catch any previously missed technical or copy errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 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 July 2013