January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16349) Wizards for new Wildfly 8 server/runtime show "JBoss Application Server 8.0"

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-16349: ----------------------------------- Summary: Wizards for new Wildfly 8 server/runtime show "JBoss Application Server 8.0" Key: JBIDE-16349 URL: https://issues.jboss.org/browse/JBIDE-16349 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.Final Environment: Kepler SR1 + JBoss AS Tools 2.4.101.Final-v20131206-1843-B159 (installed from WTP's download runtime feature) Reporter: Fred Bricon If you create a new Wildfly 8 runtime or a new server, the description in the wizard page says "JBoss Application Server 8.0" -- 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 Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2872?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2872: --------------------------------------- Big Question: Is jboss.org setting out to have one style/design? Should devstudio.html actually be mirroring/conforming to a set template? For example http://www-stg.jboss.org/products/eap/overview/ Comments on the proposed copy: * "It provides developer choice ... in testing with Arquillian." - I thought Arquillian was JBT only, but the text makes it sound like it is included and supported in JBDS. * Confusing to have download and more info go to the same link - users will just think we screwed up. To resolve should we make this one button 'Download Now' as that's probably users priority. * "Note that some older releases require a password to access - for those releases, look for an Update Guide document in the Customer Support Portal." - I have no idea as to what this is referring. Password? Update Guide? * First sentence should state 'Red Hat JBoss Developer Studio' and instances thereafter just 'JBoss Developer Studio', expect in the Previous Releases bullet list (keep in full there). > 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] (TOOLSDOC-445) Document the Hybrid Mobile project artifacts that should be placed under version control

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-445: ------------------------------------- Fix Version/s: 4.2.0 > Document the Hybrid Mobile project artifacts that should be placed under version control > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-445 > URL: https://issues.jboss.org/browse/TOOLSDOC-445 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Reporter: Vineet Reynolds > Fix For: 4.2.0 > > > I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}. > I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects. -- 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] (TOOLSDOC-445) Document the Hybrid Mobile project artifacts that should be placed under version control

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray reassigned TOOLSDOC-445: ---------------------------------------- Assignee: Michelle Murray > Document the Hybrid Mobile project artifacts that should be placed under version control > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-445 > URL: https://issues.jboss.org/browse/TOOLSDOC-445 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Reporter: Vineet Reynolds > Assignee: Michelle Murray > Fix For: 4.2.0 > > > I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}. > I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects. -- 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] (TOOLSDOC-445) Document the Hybrid Mobile project artifacts that should be placed under version control

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-445: ------------------------------------------ We can explain the project structure so that users can be more informed when making decisions about which files/dirs to place under version control. Since JBDS does not have it's own version controls actions we can't document exactly what to put under version control. As part of JBQA-8565, I stated: {quote} Gorkem Ercan, about "need to explain the different directories and what they do". This would be best included in the context of a description of standard Cordova projects and how JBDS produced Cordova projects vary. Standard/basis of Cordova projects are given in '8.2.1. About Apache Cordova'. If you think there should be more details please provide me with some pointers of what's missing. JBDS Cordova project distinctions can be given in '8.2.2. About Hybrid Mobile Tools', where the project wizard is detailed. Again, please provide any specifics of how JBDS Cordova projects differ. From the info above one distinction seems to be the absence of a platforms directory. {quote} Let's enact this for JBDS 8.0.0 (JBT 4.2.1). Information I have is as follows: 1. Cordova (CLI) project structure [1] = config.xml, hooks/, merges/, www/ with index.html, platforms/, plugins/ 2. Hybrid Mobile Tools Cordova project structure = .cordova/ with config.json, merges/, plugins/, .project, .settings/, www/ with config.xml and index.html *What info do I have wrong or am I missing?* [1] https://github.com/apache/cordova-cli#project-directory-structure > Document the Hybrid Mobile project artifacts that should be placed under version control > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-445 > URL: https://issues.jboss.org/browse/TOOLSDOC-445 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Reporter: Vineet Reynolds > > I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}. > I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects. -- 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 Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16316?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-16316: ----------------------------------------- Not entirely sure whether this jira has been resolved now or what the plan was. So sorry if this is the wrong gist: For documentation on installing Hybrid Mobile Tools and CordovaSim, see: * JBDS: https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... * JBT: http://docs.jboss.org/tools/nightly/trunk/en/User_Guide/html_single/index... (bug to fix, TOOLSDOC-444) I've made the assumption for both JBDS and JBT that JBoss Central is already installed, hence installing via the JBoss Central and the Software/Update tab. I think installing JBoss Central first is the simplest use case. But if there are use cases where we think users won't want to install JBoss Central then let me know and we can think about changing the documentation. Also, keeping Hybrid Mobile + CordovaSim as separate from the standard bundled components clearly marks them out as different from the rest and might solidify that it is only tech preview and not fully supported like other tools. > 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 > 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] (TOOLSDOC-444) Drag and drop connector for installing HM+CS is wrong for JBT

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-444: ---------------------------------------- Summary: Drag and drop connector for installing HM+CS is wrong for JBT Key: TOOLSDOC-444 URL: https://issues.jboss.org/browse/TOOLSDOC-444 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Components: User Guide - Hybrid Mobile Tools Affects Versions: 4.1.1 Environment: Build Name: 22443, User Guide-7.1 Build Date: 11-12-2013 15:10:49 Topic ID: 24053-567457 [Latest] Reporter: Michelle Murray Assignee: Michelle Murray Priority: Minor Fix For: 4.1.2 Title: Install Hybrid Mobile Tools and CordovaSim Describe the issue: Procedure 8.1. Install Hybrid Mobile Tools and CordovaSim, step 1 states: {quote} To install these plug-ins, drag the following link into JBoss Central: https://devstudio.jboss.com/central/install?connectors=org.jboss.tools.ae.... {quote} For JBT User Guide it should read: *http://download.jboss.org/jbosstools*/central/install?connectors=org.jboss.tools.aerogear.hybrid -- 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] (TOOLSDOC-444) Drag and drop connector for installing HM+CS is wrong for JBT

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-444?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-444: ------------------------------------- Description: Title: Install Hybrid Mobile Tools and CordovaSim Describe the issue: Procedure 8.1. Install Hybrid Mobile Tools and CordovaSim, step 1 states: {quote} To install these plug-ins, drag the following link into JBoss Central: https://devstudio.jboss.com/central/install?connectors=org.jboss.tools.ae.... {quote} For JBT User Guide it should read: http://download.jboss.org/jbosstools/central/install?connectors=org.jboss... Noticed when checking through JBIDE-16316 was: Title: Install Hybrid Mobile Tools and CordovaSim Describe the issue: Procedure 8.1. Install Hybrid Mobile Tools and CordovaSim, step 1 states: {quote} To install these plug-ins, drag the following link into JBoss Central: https://devstudio.jboss.com/central/install?connectors=org.jboss.tools.ae.... {quote} For JBT User Guide it should read: *http://download.jboss.org/jbosstools*/central/install?connectors=org.jboss.tools.aerogear.hybrid > Drag and drop connector for installing HM+CS is wrong for JBT > ------------------------------------------------------------- > > Key: TOOLSDOC-444 > URL: https://issues.jboss.org/browse/TOOLSDOC-444 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 24053-567457 [Latest] > Reporter: Michelle Murray > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.1.2 > > > Title: Install Hybrid Mobile Tools and CordovaSim > Describe the issue: > Procedure 8.1. Install Hybrid Mobile Tools and CordovaSim, step 1 states: > {quote} > To install these plug-ins, drag the following link into JBoss Central: https://devstudio.jboss.com/central/install?connectors=org.jboss.tools.ae.... > {quote} > For JBT User Guide it should read: > http://download.jboss.org/jbosstools/central/install?connectors=org.jboss... > Noticed when checking through JBIDE-16316 -- 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] (TOOLSDOC-435) Update 8.0 User Guide text and screen caps for IDE look & behavior changes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-435?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-435: ------------------------------------- Description: Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0): *Usage Data* * Report JVM name (JBIDE-15596) * Report 32/64-bit Eclipse/Java (JBIDE-16333) *Forge Tools* * Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263) ** F2: Ctrl+5 to open a list of actions (from JBIDE-16079) ** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117) ** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109) ** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111) * Ctrl+3?? (from JBIDE-16111) *Web Service Tools* * Support JAX-RS 2.0 (JBIDE-16329) *Mobile Web Tools* * Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348) ** Option to select which jQM version in mobile palette (JBIDE-16293) ** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347) ** New popup wizard?? (JBIDE-16326) *BrowserSim* * Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298) *Hybrid Mobile Tools + CordovaSim* * Disable add and remove buttons on parameters table in certain instances (JBIDE-16059) * Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090) * Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213) * Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312) * Issue exporting project if Android SDK location not set (JBIDE-16276) * Changes to layout of CordovaSim UI (JBIDE-16323) * Run configuration ignored for Android emulator (JBIDE-16330) * 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337) *OpenShift* * New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450) * Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031) * Web balancer cartridge should not be listed (JBIDE-16040) * Change to button names in port forwarding wizard (JBIDE-13963) * Select which ports to forward rather than forward all (JBIDE-12600) * Provide user-friendly way to increase Git timeout (JBIDE-12812) was: Add list of impacting JBIDE and JBDS jiras here: *Forge Tools* * F2: Ctrl+5 to open a list of actions (from JBIDE-16079) * F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117) * F2: Ctrl+4 menu available even when forge not running (JBIDE-16109) * F2: Ctrl+4 menu usable via keyboard (JBIDE-16111) * Ctrl+3?? (from JBIDE-16111) *Hybrid Mobile Tools + CordovaSim* * Disable add and remove buttons on parameters table in certain instances (JBIDE-16059) * Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090) *OpenShift* * New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450) * Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031) * Web balancer cartridge should not be listed (JBIDE-16040) * Change to button names in port forwarding wizard (JBIDE-13963) * Select which ports to forward rather than forward all (JBIDE-12600) > Update 8.0 User Guide text and screen caps for IDE look & behavior changes > -------------------------------------------------------------------------- > > Key: TOOLSDOC-435 > URL: https://issues.jboss.org/browse/TOOLSDOC-435 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: User Guide > Affects Versions: 4.2.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0): > *Usage Data* > * Report JVM name (JBIDE-15596) > * Report 32/64-bit Eclipse/Java (JBIDE-16333) > *Forge Tools* > * Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263) > ** F2: Ctrl+5 to open a list of actions (from JBIDE-16079) > ** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117) > ** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109) > ** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111) > * Ctrl+3?? (from JBIDE-16111) > *Web Service Tools* > * Support JAX-RS 2.0 (JBIDE-16329) > *Mobile Web Tools* > * Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348) > ** Option to select which jQM version in mobile palette (JBIDE-16293) > ** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347) > ** New popup wizard?? (JBIDE-16326) > *BrowserSim* > * Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298) > *Hybrid Mobile Tools + CordovaSim* > * Disable add and remove buttons on parameters table in certain instances (JBIDE-16059) > * Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090) > * Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213) > * Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312) > * Issue exporting project if Android SDK location not set (JBIDE-16276) > * Changes to layout of CordovaSim UI (JBIDE-16323) > * Run configuration ignored for Android emulator (JBIDE-16330) > * 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337) > *OpenShift* > * New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450) > * Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031) > * Web balancer cartridge should not be listed (JBIDE-16040) > * Change to button names in port forwarding wizard (JBIDE-13963) > * Select which ports to forward rather than forward all (JBIDE-12600) > * Provide user-friendly way to increase Git timeout (JBIDE-12812) -- 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-16343) "Materialize Libraries" is not obvious

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16343: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- 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