May 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2995) JBDS will not start with java 6 - a warning should be displayed during installation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2995?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2995: ------------------------------- Priority: Blocker (was: Major) > JBDS will not start with java 6 - a warning should be displayed during installation > ----------------------------------------------------------------------------------- > > Key: JBDS-2995 > URL: https://issues.jboss.org/browse/JBDS-2995 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Environment: JBDS 8.0.0.Beta1a B82 > OS X Mavericks > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-a > Fix For: 8.0.0.Beta2 > > > We should warn users when they select Java 6 during JBDS installation. Or perhaps even prohibit them from selecting it? > I just tried it and I was able to install JBDS, but it them wouldn't start - it shows the splash screen for a few seconds and then stops without any warning or error. > This is related to JBDS-2984 - there we removed the mention that java 6 is supported. > Here I would suggest to show a red warning once java 6 is selected - similar to how we warn people when they select java 8 in JBDS 7.1.1 installer. Another option would be to block java 6 altogether (not allow to continue) - that should be considered, since JBDS does not even start with java 6. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16973) Corrupted JSF nature for openshift project

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16973?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-16973: ----------------------------------------------- That is good that imported project has org.jboss.tools.jsf.jsfnature nature. It adds JBoss Tools JSF capabilities to the project. The problem solved was that internal validation considered this nature to be added illegally for projects without WEB-INF folder. For the latest versions of web projects it is ok to miss that folder so that the fix removes that check. Unless you do not see logged warning "Project P/<projectname> has corrupted nature: org.jboss.tools.jsf.jsfnature" and the nature is present, the project is ok. > Corrupted JSF nature for openshift project > ------------------------------------------ > > Key: JBIDE-16973 > URL: https://issues.jboss.org/browse/JBIDE-16973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Beta2 > > > 1. Create a WildFly 8 project in www.openshift.com > 2. Import it in JBT as an existing openshift project > 3. See eclipse log: > "Project P/<projectname> has corrupted nature: org.jboss.tools.jsf.jsfnature" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-17453: -------------------------------------- I can confirm replication with my own credentials. > Error while validating credentials in Download Runtime dialog > ------------------------------------------------------------- > > Key: JBIDE-17453 > URL: https://issues.jboss.org/browse/JBIDE-17453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta2 > > Attachments: credentials validation error.jpg > > > After validation of valid credentials, the following error message appears > {code} > "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16621) The quick fix for unknown attributes is not available if "Ignore specified attribute names" validation preference is unchecked

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16621?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-16621. ------------------------------- Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104 > The quick fix for unknown attributes is not available if "Ignore specified attribute names" validation preference is unchecked > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16621 > URL: https://issues.jboss.org/browse/JBIDE-16621 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.2.0.Beta2 > > > 1. Create a project > 2. Create the following html file: > {code} > <!doctype html> > <html ng-app> > </html> > {code} > 3. Open the file with JBoss Tools HTML Editor > 4. Assert: There is a problem "Undefined attribute name" for ng-app > 5. Assert: Move the mouse over the problem and you see two quick fixes: > - Ignore ng-app attribute > - Ignore all ng-* attributes > 6. Go to Preference->Web->Validation-> > 7. Check "Ignore specified attribute names" > 8. Add "ng-app,ng-*" pattern > 9. Uncheck "Ignore specified attribute names". Click OK. > 10. Assert: There is still a problem "Undefined attribute name" for ng-app > 11. Failure: Move the mouse over the problem but there are not quick fixes any more. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16096) JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16096?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16096: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.0.Beta2) > JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces > -------------------------------------------------------------------------- > > Key: JBIDE-16096 > URL: https://issues.jboss.org/browse/JBIDE-16096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.0.Beta3 > > > 1. Create a JSF 2.2 KickStart project with WildFly 8 target server. > 2. Open inputname.xhtml with JBoss XHTML editor. > 3. FAILURE: inputname uses http://java.sun.com/jsf/* namespaces instead of http://xmlns.jcp.org/jsf/* > 4. Replace all http://java.sun.com/jsf/* by http://xmlns.jcp.org/jsf/*: > {code} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ez="http://xmlns.jcp.org/jsf/composite/demo"> > {code} > 5. FAILURE: Content assist for <h: <f: <ui: <ez: is not working -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2995) JBDS will not start with java 6 - a warning should be displayed during installation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2995?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-2995 at 5/30/14 12:36 PM: --------------------------------------------------------------- +1 for blocking if Java6 is selected was (Author: dgolovin): +1 for blocking is Java6 is selected > JBDS will not start with java 6 - a warning should be displayed during installation > ----------------------------------------------------------------------------------- > > Key: JBDS-2995 > URL: https://issues.jboss.org/browse/JBDS-2995 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Environment: JBDS 8.0.0.Beta1a B82 > OS X Mavericks > Reporter: Martin Malina > Assignee: Denis Golovin > Labels: respin-a > Fix For: 8.0.0.Beta2 > > > We should warn users when they select Java 6 during JBDS installation. Or perhaps even prohibit them from selecting it? > I just tried it and I was able to install JBDS, but it them wouldn't start - it shows the splash screen for a few seconds and then stops without any warning or error. > This is related to JBDS-2984 - there we removed the mention that java 6 is supported. > Here I would suggest to show a red warning once java 6 is selected - similar to how we warn people when they select java 8 in JBDS 7.1.1 installer. Another option would be to block java 6 altogether (not allow to continue) - that should be considered, since JBDS does not even start with java 6. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17171) Tab jQuery of Properties View: Cosmetic problems

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17171?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17171: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.0.Beta2) > Tab jQuery of Properties View: Cosmetic problems > ------------------------------------------------ > > Key: JBIDE-17171 > URL: https://issues.jboss.org/browse/JBIDE-17171 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.2.0.Beta3 > > Attachments: JQContent2.png, JQExtraSeparators.png, JQMProperties5.png > > > 1. Extra separators > Test case: > EXECUTE: > 1. Create HTML 5 file: > {code} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.css" /> > <script src="http://code.jquery.com/jquery-1.10.2.min.js"></script> > <script src="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.js"></script> > </head> > <body> > <div data-role="dialog"> > </div> > </body> > </html> > {code} > 2. Open file in Visual Page Editor > 3. Select tag "div" > 4. Open tab "jQuery" of Properties View > FAIL: > !JQExtraSeparators.png! > 2. Different size of field "Data Role" > !JQContent2.png! > !JQExtraSeparators.png! > -3. Code assist sign (yellow bulb icon) does not make sense with every field- > -For instance, field "Tolerance", if you press Ctrl+Space - nothing happen.- > !JQMProperties5.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16933) Externalize selected toolitem is not properly disabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16933?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16933: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.0.Beta2) > Externalize selected toolitem is not properly disabled > ------------------------------------------------------ > > Key: JBIDE-16933 > URL: https://issues.jboss.org/browse/JBIDE-16933 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78 Linux > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Priority: Optional > Fix For: 4.2.0.Beta3 > > > 1. Create JSF2 project > 2. Open inputname.xhtml page > 3. Click somewhere within text "Input User Name" > ASSERT: Externalize toolitem is enabled > 4. Click somewhere within text <ui:define > ERROR: Externalize toolitem is enabled > 5. Double click on "<ui:define > ASSERT: Externalize toolitem is disabled -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16859) JSF tag libraries registred in XML catalog in plugins packed into JARs are not available for KB

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16859?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16859: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.0.Beta2) > JSF tag libraries registred in XML catalog in plugins packed into JARs are not available for KB > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16859 > URL: https://issues.jboss.org/browse/JBIDE-16859 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta3 > > > 1. Create a JSF 2.2 KickStart project with WildFly 8 target server. > 2. Open inputname.xhtml with JBoss XHTML editor. > 3. FAILURE: inputname uses http://java.sun.com/jsf/* namespaces instead of http://xmlns.jcp.org/jsf/* > 4. Replace all http://java.sun.com/jsf/* by http://xmlns.jcp.org/jsf/*: > {code} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ez="http://xmlns.jcp.org/jsf/composite/demo"> > {code} > 5. FAILURE: Content assist for <h: <f: <ui: <ez: is not working -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16929) Code Assist for <h:link value ""> is missing items "/resources", "/templates", "/pages"

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16929?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16929: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.0.Beta2) > Code Assist for <h:link value ""> is missing items "/resources","/templates","/pages" > -------------------------------------------------------------------------------------- > > Key: JBIDE-16929 > URL: https://issues.jboss.org/browse/JBIDE-16929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta3 > > > 1. Create JSF 2 project > 2. Open inputname.xhtml page > 3. Insert <h:link value=""> tag > 4. Call Code Assist for value attribute > ERROR: Code Assist doesn't contain items: "/resources","/templates","/pages". > Code Assist for <link href=""> href attribute contains these items -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 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 May 2014