September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen edited comment on JBDS-2763 at 9/18/13 6:26 AM: -------------------------------------------------------------------- to be clear - What I want to avoid is that users of 1024x resolution need to resize our windows to read other things than the product name ;) was (Author: maxandersen): to be clear - What I want to avoid is that users of 1024x resolution need to resize our windows to read the product name ;) > REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too? > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2763 > URL: https://issues.jboss.org/browse/JBDS-2763 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Attachments: 2763_3_places.png, 2763_cmdline.png > > > Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? > !https://issues.jboss.org/secure/attachment/12364502/12364502_ins-step-5.png! > Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar? > What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2763: ------------------------------------------- #2 or #3 would be enough imo - since that is the first/primary mention The others are the main name of the product and is sufficient they say JBoss Developer Studio, but probably doesn't hurt if you add Red Hat in front of those. > REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too? > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2763 > URL: https://issues.jboss.org/browse/JBDS-2763 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Attachments: 2763_3_places.png, 2763_cmdline.png > > > Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? > !https://issues.jboss.org/secure/attachment/12364502/12364502_ins-step-5.png! > Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar? > What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12192) BrowserSim: simulate touch events

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12192?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-12192: ------------------------------------- [~burrsutter], I have found out the root of the problem with the mobile version of the http://goodfil.ms/ and it is tightly coupled with that issue. When user tries to log in from either BrowserSim or Chrome with overridden user-agent by pushing "Sign in with Facebook"/"Sign in with Tweeter" button nothing happens because it is touch event (http://goodfil.ms/ uses zeptojs for touch events). So, if check "Emulate touch events" option in Chrome everything will work just fine. I guess that the very best solution would be having the same option ("Emulate touch events") in BrowserSim / CordovaSim. > BrowserSim: simulate touch events > --------------------------------- > > Key: JBIDE-12192 > URL: https://issues.jboss.org/browse/JBIDE-12192 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.2.x > > > Now BrowserSim sends mouse events instead of touch events. It would be more appropriate to send touchstart/touchend/touchmove events. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14506) CordovaSim: support of Cordova plugins

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14506?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14506: ------------------------------------- Summary: CordovaSim: support of Cordova plugins (was: CordovaSim: need to implement Phonegap's Card Reader plugin) Description: *Priority plugins:* 1. PushPlugin - the one that works with Aerogear's Push Server 2. BarodeScanner 3. ChildBrowser 4. Other from PhoneGap Build: https://build.phonegap.com/plugins *Deferred:* 1. Credit card scanning for mobile apps - https://www.card.io/ Plug-in exposes card.io credit card scanning - https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io was: Credit card scanning for mobile apps - https://www.card.io/ Plug-in exposes card.io credit card scanning - https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io > CordovaSim: support of Cordova plugins > -------------------------------------- > > Key: JBIDE-14506 > URL: https://issues.jboss.org/browse/JBIDE-14506 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.x > > > *Priority plugins:* > 1. PushPlugin - the one that works with Aerogear's Push Server > 2. BarodeScanner > 3. ChildBrowser > 4. Other from PhoneGap Build: https://build.phonegap.com/plugins > *Deferred:* > 1. Credit card scanning for mobile apps - https://www.card.io/ > Plug-in exposes card.io credit card scanning - https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12192) BrowserSim: simulate touch events

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12192?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-12192: ------------------------------------------ Simple test for touch events support: http://jsfiddle.net/Z68Zf/1/embedded/result/ > BrowserSim: simulate touch events > --------------------------------- > > Key: JBIDE-12192 > URL: https://issues.jboss.org/browse/JBIDE-12192 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.2.x > > > Now BrowserSim sends mouse events instead of touch events. It would be more appropriate to send touchstart/touchend/touchmove events. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-389) Figure Typo: Install Guide Fig 3.12, work > Work

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-389?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-389: ------------------------------------- Original Estimate: 15 minutes (was: 30 minutes) Remaining Estimate: 15 minutes (was: 30 minutes) > Figure Typo: Install Guide Fig 3.12, work > Work > ------------------------------------------------ > > Key: TOOLSDOC-389 > URL: https://issues.jboss.org/browse/TOOLSDOC-389 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Typo in Installation Guide Figure 3.12. title: > *work* from a Local Copy of the Update .zip File > *Work* from a Local Copy of the Update .zip File -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-71) EL refactoring for @Named beans implemented

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-71?page=com.atlassian.jira.plugi... ] Michelle Murray updated TOOLSDOC-71: ------------------------------------ Original Estimate: (was: 3 hours) Remaining Estimate: (was: 3 hours) > EL refactoring for @Named beans implemented > -------------------------------------------- > > Key: TOOLSDOC-71 > URL: https://issues.jboss.org/browse/TOOLSDOC-71 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - CDI Tools > Affects Versions: 3.0.0.GA > Reporter: Svetlana Mukhina > Assignee: Michelle Murray > Fix For: 4.2.0 > > > See the linked task for details -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-16) New algorithm for layout of mapping diagrams

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-16?page=com.atlassian.jira.plugi... ] Michelle Murray updated TOOLSDOC-16: ------------------------------------ Original Estimate: (was: 4 hours) Remaining Estimate: (was: 4 hours) > New algorithm for layout of mapping diagrams > -------------------------------------------- > > Key: TOOLSDOC-16 > URL: https://issues.jboss.org/browse/TOOLSDOC-16 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide - Hibernate Tools > Affects Versions: 3.0.0.GA > Reporter: Svetlana Mukhina > Assignee: Michelle Murray > Fix For: 4.2.0 > > > update 4.10.1.1. Mapping Diagram > see the linked task and its subtask -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-389) Figure Typo: Install Guide Fig 3.12, work > Work

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-389?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-389: ------------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Figure Typo: Install Guide Fig 3.12, work > Work > ------------------------------------------------ > > Key: TOOLSDOC-389 > URL: https://issues.jboss.org/browse/TOOLSDOC-389 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Typo in Installation Guide Figure 3.12. title: > *work* from a Local Copy of the Update .zip File > *Work* from a Local Copy of the Update .zip File -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-388) Update explicit 7.0 text references in docs to 7.1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-388: ------------------------------------- Original Estimate: (was: 5 minutes) Remaining Estimate: (was: 5 minutes) > Update explicit 7.0 text references in docs to 7.1 > -------------------------------------------------- > > Key: TOOLSDOC-388 > URL: https://issues.jboss.org/browse/TOOLSDOC-388 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Section that need updating > *Installation Guide* > * 2.2. Supported Operating Systems and Architectures > * 2.3. Computer Memory > * 2.4. Compatible Java Developer Kits > * 3.2. Install JBoss Developer Studio > * 3.3. Install JBoss Developer Studio BYOE > * 5.2. Upgrade JBoss Developer Studio > * 5.3. Upgrade JBoss Developer Studio BYOE > *Migration Guide* (2.2 and 2.3 shared with Installation Guide) > * 2.2. Upgrade JBoss Developer Studio > * 2.3. Upgrade JBoss Developer Studio BYOE > * 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *Getting Started Guide* (3.2 shared with Installation Guide) > * 2.1. About Getting Started > * 3.1. Installation Assumptions > * 3.2. Install JBoss Developer Studio > * 4.3. Tutorial Assumptions > *User Guide* > * None -- 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, 7 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 September 2013