October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-8445) Do not create markers at internal attribute validation by XModel

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8445?page=com.atlassian.jira.plugin... ] Viacheslav Kabanovich updated JBIDE-8445: ----------------------------------------- Summary: Do not create markers at internal attribute validation by XModel (was: Add preference disabling attribute validation in JBoss Tools XML editor) > Do not create markers at internal attribute validation by XModel > ---------------------------------------------------------------- > > Key: JBIDE-8445 > URL: https://issues.jboss.org/browse/JBIDE-8445 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.2.0.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > Besides, this framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15829) CLONE - Incorrect Constraint Problem for JSF composite component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15829?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15829: ----------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) (was: 4.1.1.Beta1) > CLONE - Incorrect Constraint Problem for JSF composite component > ---------------------------------------------------------------- > > Key: JBIDE-15829 > URL: https://issues.jboss.org/browse/JBIDE-15829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jsf > Affects Versions: 4.1.0.Final > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Alpha1 > > > First at all we must have a preference page where we can disable this validation. > There should not be any validation which is imposible to disable. > Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule. > We have such preferences/quick fixes for our validation that extends common validation framework. > But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15826) Incorrect Constraint Problem for JSF composite component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15826?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15826: ----------------------------------- Fix Version/s: (was: 4.2.x) > Incorrect Constraint Problem for JSF composite component > -------------------------------------------------------- > > Key: JBIDE-15826 > URL: https://issues.jboss.org/browse/JBIDE-15826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jsf > Affects Versions: 4.1.0.Final > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: respin-b > Fix For: 4.1.1.Beta1 > > > First at all we must have a preference page where we can disable this validation. > There should not be any validation which is imposible to disable. > Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule. > We have such preferences/quick fixes for our validation that extends common validation framework. > But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15829) CLONE - Incorrect Constraint Problem for JSF composite component

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-15829: -------------------------------------- Summary: CLONE - Incorrect Constraint Problem for JSF composite component Key: JBIDE-15829 URL: https://issues.jboss.org/browse/JBIDE-15829 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core, jsf Affects Versions: 4.1.0.Final Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 4.1.1.Beta1, 4.2.x First at all we must have a preference page where we can disable this validation. There should not be any validation which is imposible to disable. Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule. We have such preferences/quick fixes for our validation that extends common validation framework. But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2768: ---------------------------------- For the moment, I'm assuming this JIRA was more about splitting the information re: JBT and JBDS scripted installation across two separate sites, rather than mixing the content/streams (as I'd had before), and that links to the scripts will appear in the JBDS 7.1 doc rather than needing to be on the devstudio.jboss.com site. If that is in error, and/or ... * you would like the Early Access page template to include a link to this new scripted install page, and/or ... * you'd like the existing JBDS 6 or 7 EA pages to link to this new page... please open a new JIRA for that specific request, or just reopen this one with details on what you need done. > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > Attachments: JBDS2768_simplified.png > > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > *Update: link to JBDS scripted install is no longer on the community site.* > *Update: new JBDS scripted install page is here:* https://devstudio.jboss.com/usage/scripted-install/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2768: ----------------------------- Description: Currently availability of scripts is listed on community site: https://www.jboss.org/tools/download/installation/update_4_1#fromscript *Update: link to JBDS scripted install is no longer on the community site.* *Update: new JBDS scripted install page is here:* https://devstudio.jboss.com/usage/scripted-install/ Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html And linking to scripts on same base URL. If we want to have scripts on community site then they should only be for headless JBT install. was: Currently availability of scripts is listed on community site: https://www.jboss.org/tools/download/installation/update_4_1#fromscript And that links to instructions on community site: -http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/- https://devstudio.jboss.com/usage/scripted-install/ Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html And linking to scripts on same base URL. If we want to have scripts on community site then they should only be for headless JBT install. > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > Attachments: JBDS2768_simplified.png > > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > *Update: link to JBDS scripted install is no longer on the community site.* > *Update: new JBDS scripted install page is here:* https://devstudio.jboss.com/usage/scripted-install/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2768: ----------------------------- Description: Currently availability of scripts is listed on community site: https://www.jboss.org/tools/download/installation/update_4_1#fromscript And that links to instructions on community site: -http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/- https://devstudio.jboss.com/usage/scripted-install/ Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html And linking to scripts on same base URL. If we want to have scripts on community site then they should only be for headless JBT install. was: Currently availability of scripts is listed on community site: https://www.jboss.org/tools/download/installation/update_4_1#fromscript And that links to instructions on community site: http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/ Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html And linking to scripts on same base URL. If we want to have scripts on community site then they should only be for headless JBT install. > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > Attachments: JBDS2768_simplified.png > > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > And that links to instructions on community site: > -http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/- https://devstudio.jboss.com/usage/scripted-install/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-11602 at 10/31/13 12:36 PM: -------------------------------------------------------------------- The issue is found, reported and the patch is proposed: [Bug 420818 - NullPointerException when selecting "Add all missing tags" Quick-Fix|https://bugs.eclipse.org/bugs/show_bug.cgi?id=420818]. Issue is fixed by adding an additional check for null since the return type can be null, so this additional check is required. was (Author: vrubezhny): The issue found, reported and the patch proposed: [Bug 420818 - NullPointerException when selecting "Add all missing tags" Quick-Fix|https://bugs.eclipse.org/bugs/show_bug.cgi?id=420818]. Issue is fixed by adding an additional check for null since the return type can be null, so this additional check is required. > Provide first class support for client side development > ------------------------------------------------------- > > Key: JBIDE-11602 > URL: https://issues.jboss.org/browse/JBIDE-11602 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Sebastien Deleuze > Assignee: Victor Rubezhny > Priority: Critical > Labels: jsdt, vjet > Fix For: 4.2.x > > Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg > > > Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example). > Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE. > The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator. > My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years. > Thanks in advance for your feedback. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-11602: ----------------------------------------- The issue found, reported and the patch proposed: [Bug 420818 - NullPointerException when selecting "Add all missing tags" Quick-Fix|https://bugs.eclipse.org/bugs/show_bug.cgi?id=420818]. Issue is fixed by adding an additional check for null since the return type can be null, so this additional check is required. > Provide first class support for client side development > ------------------------------------------------------- > > Key: JBIDE-11602 > URL: https://issues.jboss.org/browse/JBIDE-11602 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Sebastien Deleuze > Assignee: Victor Rubezhny > Priority: Critical > Labels: jsdt, vjet > Fix For: 4.2.x > > Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg > > > Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example). > Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE. > The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator. > My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years. > Thanks in advance for your feedback. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-12860: ---------------------------------------- Sure, I'll take a look. > JAX-RS validation problems are not linked > ----------------------------------------- > > Key: JBIDE-12860 > URL: https://issues.jboss.org/browse/JBIDE-12860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.0.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Alexey Kazakov > Labels: respin-b > Fix For: 4.1.1.Beta1 > > > This case now fails: > STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml) > STEP: comment servlet definition in web.xml > ASSERT: problem marker in web.xml disappears > ASSERT: problem marker in application class disappears > FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers -- 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, 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 2013