January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16011) create install/download section

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ] Mustafa Musaji commented on JBIDE-16011: ---------------------------------------- Not sure this affects GSS [~nickboldt]. Users should still be able to download them if there's perhaps a need to. > create install/download section > ------------------------------- > > Key: JBIDE-16011 > URL: https://issues.jboss.org/browse/JBIDE-16011 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.0.x > > > should have download section that explains how and where to get jbosstools installed. > Should have a page pr. specific version download and a "archive" view to get directly to the past versions. > Should not require more than a few lines with urls to add a new download/install. > archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12355: ------------------------------------ A few problems w/ getting started dev guide - https://github.com/jbosstools/jbosstools-website/pull/10 * Need to tell user to do installations as root (su) * Need to mention that node.js must be installed (eg., `sudo yum install nodejs`) * In https://github.com/jbosstools/jbosstools-website/tree/master/#install-rub... must add {code} gem install execjs {code} > JBoss tools website redesign > ---------------------------- > > Key: JBIDE-12355 > URL: https://issues.jboss.org/browse/JBIDE-12355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.0.x > > Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png > > > jboss.org/tools have started to have issues scaling on several fronts. > 1) no clear path to what we want users to download (too many upfront choices) > 2) we are missing info about what jbosstools actually does > 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live) > 4) the content is generally getting very stale > 5) it is not easy to blog via community.jboss.org - resulting in less content (#4) > etc. etc. > 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor. > We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content. > https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress. > http://xcoulon.github.io/jbosstools-website/ <-- current version -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16011) create install/download section

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16011: --------------------------------------------- All versions is supposed to be the full archive. These are not meant to be supported by GSS - just a reference for where to get the various actual released binaries to let users and us use and report bugs against. > create install/download section > ------------------------------- > > Key: JBIDE-16011 > URL: https://issues.jboss.org/browse/JBIDE-16011 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.0.x > > > should have download section that explains how and where to get jbosstools installed. > Should have a page pr. specific version download and a "archive" view to get directly to the past versions. > Should not require more than a few lines with urls to add a new download/install. > archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16011) create install/download section

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16011: ------------------------------------ http://jbosstools.github.io/jbosstools-website/downloads/devstudio/allver... << remove obsolete dev builds - once a .Final or .GA is available, links to CRs, Betas and Alphas should vanish IMHO. We could move them to another page if we really need to persist them but I'd rather make 'em vanish since they're not to be supported by GSS. WDYT, [~mmusaji] ? > create install/download section > ------------------------------- > > Key: JBIDE-16011 > URL: https://issues.jboss.org/browse/JBIDE-16011 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.0.x > > > should have download section that explains how and where to get jbosstools installed. > Should have a page pr. specific version download and a "archive" view to get directly to the past versions. > Should not require more than a few lines with urls to add a new download/install. > archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16011) create install/download section

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16011: ------------------------------------ Some feedback: re: http://jbosstools.github.io/jbosstools-website/downloads/devstudio/kepler... * links do not work: Requirements | What's New | Release Note * "Release Note" should be plural, "Release Notes" * "Downloadable zips of the Update site" should be "Update Site Zip" * Name / Size / Links could be Name / Size / MD5 / Link (singular) * "depending on the features of JBoss Tools" should be "depending on the features of JBoss Developer Studio" or could just tell people to select the "Core Features" feature / "Bring Your Own Eclipse" category to get everything they need * " JBoss Developer Studio 7.1.0.Final was released on 2013-10-22. " Actually, the release date was 2013-12-16. * Install button for Marketplace doesn't work, and when you cursor over it, there's an underline that appears to the right of the button. This is due to this code, which lacks an href and an onclick, and provides a space within the anchor tags. {code}<a title="Install"><img ...> </a>{code} * Link does not work in this text: "You can also view the installation page on the Eclipse Marketplace. " * "The Full Monty" should perhaps simply be "All Releases" or "All Versions" > create install/download section > ------------------------------- > > Key: JBIDE-16011 > URL: https://issues.jboss.org/browse/JBIDE-16011 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.0.x > > > should have download section that explains how and where to get jbosstools installed. > Should have a page pr. specific version download and a "archive" view to get directly to the past versions. > Should not require more than a few lines with urls to add a new download/install. > archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2872) https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2872?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2872: ----------------------------- Attachment: new-jbds-7x-dl-page_v2.png PR updated. New screenshot: !new-jbds-7x-dl-page_v2.png! > https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2872 > URL: https://issues.jboss.org/browse/JBDS-2872 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.1.GA > > Attachments: new-jbds-7x-dl-page.png, new-jbds-7x-dl-page_v2.png > > > https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html instead of the old JBDS PE / JBDS Eval process. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2872) https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2872?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2872: ---------------------------------- Re: template: Wow. They've just barely rolled out https://www.jboss.org/products/eap and now it's being completely reskinned as http://www-stg.jboss.org/products/eap/overview/ ? Similarly... http://www.jboss.org/products/devstudio/ vs. http://www-stg.jboss.org/products/devstudio/overview/ Re: copy: If I change copy on devstudio.jboss.com I will have to change it on the various jboss.org pages too. Not adverse to that, but technically that's Marketing's job so maybe we want to wait until they settle on a skin & possibly clean up the copy themselves? Also, re: first occurrence of product name appearing in copy as "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" - the graphic above the copy and the page's <title> tag both conform, so the need to have the copy prefixed w/ "Red Hat" seems unnecessary. Re: two links: I could have them target different anchors, or we could just have the one link. One is probably simpler. Re: password access to update sites JBDS 3 required a password to use the update site. Details here: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2872 > URL: https://issues.jboss.org/browse/JBDS-2872 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.1.GA > > Attachments: new-jbds-7x-dl-page.png > > > https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html instead of the old JBDS PE / JBDS Eval process. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16316) Add Hybrid Tools to Eclipse Marketplace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16316?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-16316. ------------------------------ Fix Version/s: 4.1.1.Final Resolution: Won't Fix I believe the decision here was that we won't do anything to add Hybrid Mobile Tools or CordovaSim to the Marketplace entries at this time. [~burrsutter] [~maxandersen] If that's incorrect, please reopen w/ instructions on how to proceed. > Add Hybrid Tools to Eclipse Marketplace > --------------------------------------- > > Key: JBIDE-16316 > URL: https://issues.jboss.org/browse/JBIDE-16316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Reporter: Burr Sutter > Fix For: 4.1.1.Final > > Attachments: JBIDE-16316-alt-install-process.png, jbt-411-stable-site.png > > > Hybrid Tools are currently not listed under Eclipse Marketplace. > http://www.screencast.com/t/e3f4UOsEx > and they should be a popular feature. > -- 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, 2 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-11602. ----------------------------------------- Fix Version/s: 4.2.0.Alpha1 4.1.1.Final (was: 4.2.x) Resolution: Partially Completed I'm going to resolve this issue as partially resolved since we have done great strides in improving javascript support in JSDT. for JBT 4.1.x or rather Eclipse Kepler SR2 we've help fix many of the false warnings and in JBT 4.2.x (based on Eclipse Luna) more improvements are coming in but keeping them driven by this openended jira is not useful imo. Thus resolving this jira, but do know we are working on this but it will be in more specific jiras and if that is too much then follow Eclipse WTP releases and jboss tools releases and watch their New and noteworthy docs which should highlight these. > 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.0.Alpha1, 4.1.1.Final > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16350) Cleanup: move databinding utils to commons

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16350?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16350: ------------------------------------- Component/s: common/jst/core > Cleanup: move databinding utils to commons > ------------------------------------------ > > Key: JBIDE-16350 > URL: https://issues.jboss.org/browse/JBIDE-16350 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core, openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Alexey Kazakov > Fix For: 4.2.0.Alpha2 > > > There are databinding utils in OpenShift that should be moved to commons. -- 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, 2 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 January 2014