July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-348) Installation Guide 7.0.0 - add screen captures

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-348?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-348. -------------------------------------- Resolution: Done > Installation Guide 7.0.0 - add screen captures > ---------------------------------------------- > > Key: TOOLSDOC-348 > URL: https://issues.jboss.org/browse/TOOLSDOC-348 > 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 > > -- 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-376) Delete old OpenShift Tools doc

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-376?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-376: ------------------------------------- Assignee: Andre Dietisheim (was: Michelle Murray) > Delete old OpenShift Tools doc > ------------------------------ > > Key: TOOLSDOC-376 > URL: https://issues.jboss.org/browse/TOOLSDOC-376 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues, User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Fix For: 4.1.0 > > > OpenShift Tools has a chapter in the new 4.1.x user guide. > The old OpenShift Tools reference document needs to be deleted from the jbosstools-openshift repository (https://github.com/jbosstools/jbosstools-openshift). > Specifically, the *docs/* directory must be deleted from *master* and *4.1.x* branches. -- 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-348) Installation Guide 7.0.0 - add screen captures

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-348?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-348: ------------------------------------------ Typos fixed too: * Procedure 3.2. Install from Eclipse Marketplace = Ensure the *JBoss* Developer Studio (Kepler) check box is selected and click *Next*. (> Red Hat JBoss, > 'Confirm >') * Procedure 6.2. Uninstall from Eclipse Marketplace = Ensure the *JBoss* Developer Studio (Kepler) check box is selected and click Finish. (> Red Hat JBoss) And add extra step - one for click confirm and one for click finish * Procedure 4.1. Set up Runtime Detection = Click Window→Preferences, expand JBoss Tools and select *JBoss Tools Runtime Detection*. (> JBoss Runtime Detection) > Installation Guide 7.0.0 - add screen captures > ---------------------------------------------- > > Key: TOOLSDOC-348 > URL: https://issues.jboss.org/browse/TOOLSDOC-348 > 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 > > -- 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-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Meng Bo <bmeng(a)redhat.com> made a comment on [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] According commnet#4, assign the bug back. > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.png! -- 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-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Meng Bo <bmeng(a)redhat.com> changed the Status of [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] from ON_QA to ASSIGNED > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.png! -- 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-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Meng Bo <bmeng(a)redhat.com> made a comment on [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] Checked on devenv_3580, the message severity level show warning this time. "messages": [ { "exit_code": 0, "field": null, "severity": "info", "text": "Application app3s was created." }, { "exit_code": 0, "field": null, "severity": "warning", "text": "HAProxy instance is started\n" @Andre Dietisheim Not sure if the current result is acceptable. Can you please help move the bug to verified if it is ok. > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.png! -- 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-349) Getting Started Guide 7.0.0 - add screen captures

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-349?page=com.atlassian.jira.plug... ] Michelle Murray edited comment on TOOLSDOC-349 at 7/29/13 10:14 PM: -------------------------------------------------------------------- PR applied to master and 4.1.x: https://github.com/jbosstools/jbosstools-documentation/pull/148 Doc brewed and available for review: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... was (Author: mmurray): PR applied to master and 4.1.x. Doc brewed and available for review: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > Getting Started Guide 7.0.0 - add screen captures > ------------------------------------------------- > > Key: TOOLSDOC-349 > URL: https://issues.jboss.org/browse/TOOLSDOC-349 > 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 > > -- 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-15263) Create Datasource Dialog/Wizard usability

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15263?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15263: ----------------------------------------------- [~burrsutter], should option 'AS 7' be renamed to 'EAP 6/AS 7'? > Create Datasource Dialog/Wizard usability > ----------------------------------------- > > Key: JBIDE-15263 > URL: https://issues.jboss.org/browse/JBIDE-15263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core > Affects Versions: 4.1.0.Beta2 > Reporter: Burr Sutter > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > Attachments: 2013-07-19_1034.png > > > The current Create Datasource dialog has a few usability "gotchas": > 1) It is located under the "JBoss Tools Web" category - when it is more appropriate to be under the "JBoss Tools" category, closer to the Forge wizards - where you need it. > 2) It defaults to AS5, not AS7 - it should default to EAP6/AS7 > 3) It defaults to register in persistence.xml - it is unclear to me how cleanly this injects into the current persistence.xml provided by the Forge wizards, I tend to uncheck it to be safe - then manually tweak up the persistence.xml to reference the same resource. -- 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] (JBTIS-120) composite*.xml generator should NOT include *.zip in the list of <child> URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-120?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBTIS-120. ------------------------------ Resolution: Done Tested by uploading an empty foo.zip file into http://download.jboss.org/jbosstools/updates/integration/locus/, then respinning a build to force the metadata to be regenerated. The zip was NOT included in the resulting composite*.xml files. > composite*.xml generator should NOT include *.zip in the list of <child> URLs > ----------------------------------------------------------------------------- > > Key: JBTIS-120 > URL: https://issues.jboss.org/browse/JBTIS-120 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: releng > Affects Versions: 4.0.1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1 > > > Fix https://raw.github.com/jbosstools/jbosstools-build-ci/master/util/cleanup... to exclude *.zip in list of <child> sites. > Can verify this works when the JBTIS 4.0.2 release comes out, and drops content into http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- 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-15306) org.jboss.tools.locus.jcip.annotations plugin should not have Alpha, Beta or CR in its name

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15306?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15306: ------------------------------------ Now building w/ Final instead of Alpha/Beta/CR in the plugins' names: http://download.jboss.org/jbosstools/updates/integration/locus/1.1.0.CI/p... {quote}org.jboss.tools.locus.jcip.annotations_1.0.0.Final-v20130729-2054-B38.jar{quote} > org.jboss.tools.locus.jcip.annotations plugin should not have Alpha, Beta or CR in its name > ------------------------------------------------------------------------------------------- > > Key: JBIDE-15306 > URL: https://issues.jboss.org/browse/JBIDE-15306 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: locus > Affects Versions: 1.0.0-LOCUS > Reporter: Nick Boldt > Fix For: 1.1.0-LOCUS > > > Looks like because the version set for org.jboss.tools.locus.jcip.annotations is 1.0.0-SNAPSHOT it's picking the BUILD_ALIAS from the root pom, which could be Alpha, Beta, or CR... but the plugins should always be Final-vTIMESTAMP-B##, so we need to override this in the plugin's pom. -- 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