July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15311) Error in validation of jboss-deployment-structure.xml

by Marek Novotny (JIRA)

Marek Novotny created JBIDE-15311: ------------------------------------- Summary: Error in validation of jboss-deployment-structure.xml Key: JBIDE-15311 URL: https://issues.jboss.org/browse/JBIDE-15311 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Version: 7.0.0.GA Build id: GA-v20130720-0044-B364 Build date: 20130720-0044 WFK 2.3.0.GA, Seam 2.3.1.Final-redhat-2 Reporter: Marek Novotny Wrong validation error on jboss-deployment-structure.xml file: {code:XML} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0"> <deployment> <dependencies> <module name="org.hibernate" export="true"/> <module name="javax.faces.api" export="true" /> <module name="com.sun.jsf-impl" export="true"/> <module name="org.dom4j" export="true"/> <module name="org.hibernate.validator" export="true"/> </dependencies> </deployment> </jboss-deployment-structure> {code} Validation error: {noformat} cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml {noformat} The error says exactly what is in jboss-deployment-structure.xml - we have there deployment, so this is valid and not invalid content. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15310) JPP6.1 needs strict serverbean detector

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15310: ----------------------------------- Summary: JPP6.1 needs strict serverbean detector Key: JBIDE-15310 URL: https://issues.jboss.org/browse/JBIDE-15310 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: server Affects Versions: 4.1.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.1.Final While JBDS-2703 fixes the issue of jpp-6.1 being incorrectly recognized, it'd be better if there was a strict detector for identifying jpp-6.1. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15286) Increment service version of jbosstools-base/usage submodule

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15286?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15286: ------------------------------------------ ok, I didnt spot this, it definitely makes sense. I updated my PR accordingly. > Increment service version of jbosstools-base/usage submodule > ------------------------------------------------------------ > > Key: JBIDE-15286 > URL: https://issues.jboss.org/browse/JBIDE-15286 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha1 > > > Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.100 according http://wiki.eclipse.org/Version_Numbering. -- 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

11 years, 4 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] Move bug to verified. > 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

11 years, 4 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 VERIFIED > 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

11 years, 4 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: ------------------------------------------ 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

11 years, 4 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 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

11 years, 4 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

11 years, 4 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

11 years, 4 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

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2013