May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-299) Rewrite the Installation, Migration and Getting Started Guides

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-299?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-299: ------------------------------------------ Use case text added. Still need to add screen captures. > Rewrite the Installation, Migration and Getting Started Guides > -------------------------------------------------------------- > > Key: TOOLSDOC-299 > URL: https://issues.jboss.org/browse/TOOLSDOC-299 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide, Migration Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Rewrite these docs as per the draft tables of contents at: https://docs.google.com/a/rhcollab.com/document/d/1ig2FWk6dIJUIuuGZf3CNit... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-314) Update install information - JBDS launches immediately install completes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-314?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-314: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-documentation/pull/63 > Update install information - JBDS launches immediately install completes > ------------------------------------------------------------------------- > > Key: TOOLSDOC-314 > URL: https://issues.jboss.org/browse/TOOLSDOC-314 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide, Installation Guide, Migration Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-314) Update install information - JBDS launches immediately install completes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-314?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-314: ------------------------------------------ Change was completed as part of adding use case information to docs (TOOLSDOC-299). PR applied to master. > Update install information - JBDS launches immediately install completes > ------------------------------------------------------------------------- > > Key: TOOLSDOC-314 > URL: https://issues.jboss.org/browse/TOOLSDOC-314 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide, Installation Guide, Migration Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-299) Rewrite the Installation, Migration and Getting Started Guides

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-299?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-299: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-documentation/pull/63 > Rewrite the Installation, Migration and Getting Started Guides > -------------------------------------------------------------- > > Key: TOOLSDOC-299 > URL: https://issues.jboss.org/browse/TOOLSDOC-299 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide, Migration Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Rewrite these docs as per the draft tables of contents at: https://docs.google.com/a/rhcollab.com/document/d/1ig2FWk6dIJUIuuGZf3CNit... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-311) Review: Devs to review OpenShift Tools chapter for JBDS 7.0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-311?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-311: ------------------------------------------ [~maxandersen], this was a very specific JIRA aimed at one person, Andre. The point of the JIRA was to review an early draft of a doc from a technical perspective. At this point in time I needed info from Andre only. The document was sent directly to Andre. I see now that I could have attached the pdf to this JIRA for ease. This document is not in git at the moment and so there is no PR. It is not in git because it is in an exceedingly early draft stage. Once the document is more developed I will add it to git with a PR. At an appropriate time closer to GA the doc will be made available on the internal staging site (and github) for all, and most importantly QE, to review. At that time, a new JIRA will be opened with the necessary URL. > Review: Devs to review OpenShift Tools chapter for JBDS 7.0 > ----------------------------------------------------------- > > Key: TOOLSDOC-311 > URL: https://issues.jboss.org/browse/TOOLSDOC-311 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > Attachments: instant-apps.png > > > Please review the content of the OpenShift chapter from a technical viewpoint: > 1) Are features correctly documented? > 2) Are there any features that are missing? > The chapter has been sent to you by email as pdf. Please let me know if you would prefer an alternative format or delivery point for reviewing. > Screenshots are currently missing and will be added closer to GA. > Please give feedback as comments in this JIRA. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2439?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2439: ------------------------------------- Fixed the same issue for windows. > jbdevstudio-unity execution fails when called from different working directory > ------------------------------------------------------------------------------ > > Key: JBDS-2439 > URL: https://issues.jboss.org/browse/JBDS-2439 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.0.GA > Reporter: Ondrej Skutka > Assignee: Denis Golovin > Fix For: 7.0.0.Beta1 > > > jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir. > This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2439?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-2439. --------------------------------- Release Notes Docs Status: Not Required Resolution: Done > jbdevstudio-unity execution fails when called from different working directory > ------------------------------------------------------------------------------ > > Key: JBDS-2439 > URL: https://issues.jboss.org/browse/JBDS-2439 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.0.GA > Reporter: Ondrej Skutka > Assignee: Denis Golovin > Fix For: 7.0.0.Beta1 > > > jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir. > This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781. -- 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, 11 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 5/6/13 7:30 PM: ----------------------------------------------------------------- Another issue from JSDT affects VJET's fork of JSDT parser: [Bug 404832 - JavaScript error on valid regex|https://bugs.eclipse.org/bugs/show_bug.cgi?id=404832]. The issue is created for VJET: [Bug 407293 - JavaScript error on valid RegEx when the '/'-char is in character list (inside "\[...\]" brackets)|https://bugs.eclipse.org/bugs/show_bug.cgi?id=407293] The patch is provided for the issue (the patch from Bug 404832 was partially adopted for VJET's fork of JSDT parser). The patch that fixes the RegEx sintax highlighting part of the issue is proposed in [Bug 401250 - \[highlighting\] regular expression causes false comment color |https://bugs.eclipse.org/bugs/show_bug.cgi?id=401250], the patch also fixes the initial RegEx syntax highlighting problem described in the issue. Note that original JSDT issue is still reproducible in JBoss Tools HTML editor even if VJET's parser and editor are fixed. So, we still need that patch for [Bug 404832 - JavaScript error on valid regex|https://bugs.eclipse.org/bugs/show_bug.cgi?id=404832] to be applied. was (Author: vrubezhny): Another issue from JSDT affects VJET's fork of JSDT parser: [Bug 404832 - JavaScript error on valid regex|https://bugs.eclipse.org/bugs/show_bug.cgi?id=404832]. The issue is created for VJET: [Bug 407293 - JavaScript error on valid RegEx when the '/'-char is in character list (inside "\[...\]" brackets)|https://bugs.eclipse.org/bugs/show_bug.cgi?id=407293] The patch is provided for the issue (the patch from Bug 404832 was partially adopted for VJET's fork of JSDT parser). The patch that fixes the RegEx sintax highlighting part of the issue is proposed in [Bug 401250 - \[highlighting\] regular expression causes false comment color |https://bugs.eclipse.org/bugs/show_bug.cgi?id=401250], the patch also fixes the initial RegEx syntax highlighting problem described in the issue. > 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 > Labels: jsdt, vjet > Fix For: 4.1.0.Beta1 > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14379) Seam Web project datasource settings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14379?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-14379. ------------------------------------ Resolution: Duplicate Issue I'm resolving this issue as a duplicate of JBIDE-13965 Tomas, feel free to reopen the issue if I didn't understand you problem. > Seam Web project datasource settings > ------------------------------------ > > Key: JBIDE-14379 > URL: https://issues.jboss.org/browse/JBIDE-14379 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Seam 2 > Environment: JBDS 7.0.0.Alpha2, Seam2.3 > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > > I consider default Seam Project wizard and its default datasource settings (especially running on EAP 6) as confusing. I would suggest to have the H2 datasource (there is no hsqldb) as default option at last wizard's dialog. I understand that this is question about Seam and EAP versions. EAP 5 & Seam2.2 is ok with hsqldb, but this is not true when using Seam2.3 & EAP 6. > Next thing is when I don't specify any other datasource settings, I'll get datasource containing exactly the name of the driver (e.g h2-1.3.168-redhat-1.jar), which is not deployable. Why the default h2 driver (included in standalone.xml config) is not use? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14379) Seam Web project datasource settings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14379?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-14379: ---------------------------------------- Seam Project Wizard does not use any specific connection profile. You can (or you have to if there is not any existing connection profile) create a new profile (H2/HSQLDB/...). This profile will be used by Seam Wizard to create -ds.xml file. So -ds.xml will be created correctly only if you use a proper connection profile. But if you are talking about JBoss Developer Studio with bundled EAP 6 (not JBoss Tools) then you get a preconfigured connection profile. So this is the problem but it's another issue which described in JBIDE-13965 > Seam Web project datasource settings > ------------------------------------ > > Key: JBIDE-14379 > URL: https://issues.jboss.org/browse/JBIDE-14379 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Seam 2 > Environment: JBDS 7.0.0.Alpha2, Seam2.3 > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > > I consider default Seam Project wizard and its default datasource settings (especially running on EAP 6) as confusing. I would suggest to have the H2 datasource (there is no hsqldb) as default option at last wizard's dialog. I understand that this is question about Seam and EAP versions. EAP 5 & Seam2.2 is ok with hsqldb, but this is not true when using Seam2.3 & EAP 6. > Next thing is when I don't specify any other datasource settings, I'll get datasource containing exactly the name of the driver (e.g h2-1.3.168-redhat-1.jar), which is not deployable. Why the default h2 driver (included in standalone.xml config) is not use? -- 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, 11 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 2013