October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-512) OpenShift How To: Deploy an Existing Workspace Application to OpenShift Online

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-512?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-512: ------------------------------------- Sprint: 2014/S19 (13-Oct > 26-Oct), 2014/S20 (27-Oct > 9-Nov) (was: 2014/S19 (13-Oct > 26-Oct)) > OpenShift How To: Deploy an Existing Workspace Application to OpenShift Online > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-512 > URL: https://issues.jboss.org/browse/TOOLSDOC-512 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - OpenShift Tools > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > > Article 3: > Deploy an Existing Workspace Application > Introductory paragraphs > In the New OpenShift Application wizard, click Use my existing OpenShift application and then click Browse to look for the application > Detailed steps > Import a Running Application to a Workspace > Introductory paragraphs > Click File > Import. Expand OpenShift and click Existing OpenShift Application and then click Next > Detailed steps -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-530) IDE How To: Install JBDS

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-530?page=com.atlassian.jira.plug... ] Supriya Bharadwaj resolved TOOLSDOC-530. ---------------------------------------- Resolution: Done Completed and published the guide at: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > IDE How To: Install JBDS > ------------------------ > > Key: TOOLSDOC-530 > URL: https://issues.jboss.org/browse/TOOLSDOC-530 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Installation Guide > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Chunyun Chen commented on JBIDE-18696: -------------------------------------- >>> "Can you replicate this with OpenShift Online? " I also can not replicate this issue in OpenShift Online(openshift.redhat.com) >>> "..... Every later attempt doesnt have quickstarts, right?" Can see quickstarts after restarting Eclipse, and can not see the quickstarts if not restarting Eclipse. > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-521) Review JIRA queries in Release Notes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-521?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-521. -------------------------------------- Resolution: Won't Fix If someone can suggest a better query then feel free to reopen the jira. > Review JIRA queries in Release Notes > ------------------------------------ > > Key: TOOLSDOC-521 > URL: https://issues.jboss.org/browse/TOOLSDOC-521 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > > When reviewing RNs for JBDS 8.0.0.CR1, we came to the conclusion that the JIRA queries may need updating. > For reference, here's is discussion between me and Michelle on the subject: > {quote} > 01:23 mmalina: mmurray: I have a question about RN - resolved issues: (project in (JBDS) AND affectedVersion < "8.0.0.CR1" AND fixVersion in ("8.0.0.CR1") OR project in (JBIDE) AND affectedVersion < "4.2.0.CR1" AND fixVersion in ("4.2.0.CR1")) AND type in (Bug) AND resolution in (Done) > 01:24 mmalina: mmurray: why have the fixVersion there? any special reason? > 01:24 mmalina: mmurray: because it's 130 issues vs. 200 without it > 01:24 maxandersen: don't use the < > comparisons. they unforatunely dont work reliably ;/ > 01:26 mmalina: maxandersen: the problem here is there are many jiras without affectedVersion > 01:26 mmalina: *the main problem > 01:26 mmalina: + what you say > 01:27 maxandersen: mmalina: ah yeah. historically affectedVersion is only rarely used. > 01:27 maxandersen: mmalina: only when we got very scifci issues where its important. > 01:30 mmalina: mmurray: my only guess why you have it there is that you wanted to avoid jiras found in CR1 and fixed in CR1 - the thinking being that these would be new in CR1 and not present previously, thus you shouldn't list them in "what's fixed since the previous release". but that reasoning doesn't really work - 90 % bugs found in CR1 were already there before previously ;) any other reason to have it there? > {quote} > Michelle wrote: > {quote} > The search query is a best effort. > The affects version is as you said, to avoid picking up internally identified bugs from QE/team testing CR1respinA that were fixed in CR1respinB, say. The customer doesn't need to know or care about these. > The fixed version is a bit more complicated. The problem is that this query goes into the doc and the search results effectively have to remain static for all time - the doc could be hosted for years to come. This CR1 RNs doc should only list the bugs fixed in the CR1 release. If I leave the fixversion out then when bugs identified in <8.0.0.CR1 get resolved for CR2 or GA or even 9.1.0 they will show up in this query and that screws up the doc. The CR1 RNs doc we get replaced with a GA version so it isn't so important for this one but it is for the GA copy and it's easier to keep basically the same query as I iterate the doc towards GA. > Regards using < and >, they are working effectively from what I can see. To make the comparisons work it just needs the versions to be listed in chronological order on the JBIDE and JBDS jira project pages. > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-556) MobileDev How To: Create Your First Mobile Web App

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-556?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-556: ------------------------------------- Description: Instructions to cover in this How To: 1. Create a HTML5 Project 2. Build and Deploy the Application 3. View the Application with BrowserSim 4. Enable LiveReload for BrowserSim 5. Change the Application > MobileDev How To: Create Your First Mobile Web App > -------------------------------------------------- > > Key: TOOLSDOC-556 > URL: https://issues.jboss.org/browse/TOOLSDOC-556 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Reporter: Michelle Murray > Assignee: Aakanksha Singh > Fix For: 4.2.0.Final > > > Instructions to cover in this How To: > 1. Create a HTML5 Project > 2. Build and Deploy the Application > 3. View the Application with BrowserSim > 4. Enable LiveReload for BrowserSim > 5. Change the Application -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-556) MobileDev How To: Create Your First Mobile Web App

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-556: ---------------------------------------- Summary: MobileDev How To: Create Your First Mobile Web App Key: TOOLSDOC-556 URL: https://issues.jboss.org/browse/TOOLSDOC-556 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Reporter: Michelle Murray Assignee: Aakanksha Singh Fix For: 4.2.0.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-554) User must end each line in import.sql with a semi-colon character

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-554?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-554: ------------------------------------- Sprint: 2014/S20 (27-Oct > 9-Nov) > User must end each line in import.sql with a semi-colon character > ----------------------------------------------------------------- > > Key: TOOLSDOC-554 > URL: https://issues.jboss.org/browse/TOOLSDOC-554 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Affects Versions: 4.2.0.Final > Environment: Build Name: 22960, Start Developing-8.0 > Build Date: 22-10-2014 11:29:36 > Topic ID: 13783-717265 [Latest] > Reporter: Len DiMaggio > Assignee: Michelle Murray > Priority: Minor > > Title: Prepare Event Records to Populate the Database > Describe the issue: > The text reads: > Create a new Event record by copying the following on one line after the existing Member record > But - before the user does this^ he/she must append a semi-colon character to the end of the existing Member record line in the import.sql file > Suggestions for improvement: > Additional information: -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-552) User must be in the JBoss Perspective in JBDS/JBT in order to use the Forge options described in this section

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-552?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-552: ------------------------------------- Priority: Minor (was: Blocker) Sprint: 2014/S20 (27-Oct > 9-Nov) > User must be in the JBoss Perspective in JBDS/JBT in order to use the Forge options described in this section > ------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-552 > URL: https://issues.jboss.org/browse/TOOLSDOC-552 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Environment: Build Name: 22960, Start Developing-8.0 > Build Date: 22-10-2014 11:29:36 > Topic ID: 13791-717241 [Latest] > Reporter: Len DiMaggio > Assignee: Michelle Murray > Priority: Minor > > Title: Add an Entity Using Forge Tools > Describe the issue: > This step will fail unless the user is in the JBoss Perspective: > "In the Project Explorer view, right-click Event.java and click Show In→Forge Console. " > Suggestions for improvement: > We should remind the user - at the start of the section - that he must be in the JBoss perspective. > Additional information: -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-348) User can not download the release note from Red Hat Customer Portal

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBTIS-348?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBTIS-348: ---------------------------------- Assignee: Paul Leacu (was: Michelle Murray) > User can not download the release note from Red Hat Customer Portal > ------------------------------------------------------------------- > > Key: JBTIS-348 > URL: https://issues.jboss.org/browse/JBTIS-348 > Project: JBoss Tools Integration Stack > Issue Type: Documentation > Environment: JBDSIS 7.0.3.GA > Reporter: hisao furuichi > Assignee: Paul Leacu > > From Red Hat Customer Portal[1][2], user can not download the release note for JBDSIS 7.0.3[3]. > [1] https://access.redhat.com/documentation/ja-JP/Red_Hat_JBoss_Developer_Stu... > [2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl... > [3] https://devstudio.jboss.com/updates/7.0/integration-stack/release-notes/R... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-348) User can not download the release note from Red Hat Customer Portal

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBTIS-348?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBTIS-348: --------------------------------------- [~mmusaji] - reassigning to [~pleacu]. The JBDS docs team does not produce or manage the JBDS-IS docs. > User can not download the release note from Red Hat Customer Portal > ------------------------------------------------------------------- > > Key: JBTIS-348 > URL: https://issues.jboss.org/browse/JBTIS-348 > Project: JBoss Tools Integration Stack > Issue Type: Documentation > Environment: JBDSIS 7.0.3.GA > Reporter: hisao furuichi > Assignee: Michelle Murray > > From Red Hat Customer Portal[1][2], user can not download the release note for JBDSIS 7.0.3[3]. > [1] https://access.redhat.com/documentation/ja-JP/Red_Hat_JBoss_Developer_Stu... > [2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl... > [3] https://devstudio.jboss.com/updates/7.0/integration-stack/release-notes/R... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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 October 2014