September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-14655) Part of sreenshot which is not visible is transparent

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14655?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-14655. ------------------------------- > Part of sreenshot which is not visible is transparent > ----------------------------------------------------- > > Key: JBIDE-14655 > URL: https://issues.jboss.org/browse/JBIDE-14655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0 Beta1-v20130526-0839-B241, Linux KDE > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Final > > > 1. Open BrowserSim > 2. Choose skin which doesn't fit to monitor e.g. Apple iPad Retina 4 > 3. Save screenshot > ERROR: Result is described here https://issues.jboss.org/browse/JBIDE-13434?focusedCommentId=12777198&pag... > Screenshot should contain complete BrowserSim -- 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] (JBTIS-179) ModeShape Client is in wrong categories

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-179?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-179: ---------------------------------- Hey Dan / Andrej - Should I keep Modeshape in for the SOA 5.x Dev category? That cat doesn't exist on the community side. --paull > ModeShape Client is in wrong categories > --------------------------------------- > > Key: JBTIS-179 > URL: https://issues.jboss.org/browse/JBTIS-179 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 7.0.0-JBDS > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/integration/kepler/integrat... > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Now, the ModeShape Cient in the following categories > * JBoss Business Process and Rules Development (there's nothing in common with ModeShape) > * JBoss Data Virtualization Development (OK) > * JBoss SOA 5.x Development (maybe OK, but EDS is needed) > * JBoss SOA Development (wrong, we need DV for ModeShape) -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2763: ----------------------------- Attachment: 2763_cmdline.png 2763_3_places.png [~maxandersen] OK, so which of these three would you change as the first occurrence in the installer? I would change all three: !2763_3_places.png! Also, when installing commandline, we see this, which I would also change: !2763_cmdline.png! Would you agree we should update all 4 places above? Not suggesting we change the filename. > 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: ------------------------------------------- note, adding Red Hat to the *very* first page of the installer is fine - but none of these features, package names etc. is in any way required to change. > 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 > > 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 CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2763: ----------------------------- CDW release: - (was: ?) > 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 > > 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 updated JBDS-2763: -------------------------------------- CDW devel_ack: - (was: ?) > 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 > > 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: ------------------------------------------- We are not adding any of this to product names, short cuts, launchers etc. It is a complete user nightmare nor does branding require this at all. > 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 > > 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-14506) CordovaSim: need to implement Phonegap's Card Reader plugin

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14506?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-14506: -------------------------------------- For Cordova>3.0 we simply need to support all the org.apache.core.* plugins since those are what used to be core functionality. They are listed in http://plugins.cordova.io/#/_browse/all > CordovaSim: need to implement Phonegap's Card Reader plugin > ----------------------------------------------------------- > > 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 > > > 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-15408) Live Reload New and Noteworthy for 4.1.1.Alpha1

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15408?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15408: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Please review the PR > Live Reload New and Noteworthy for 4.1.1.Alpha1 > ----------------------------------------------- > > Key: JBIDE-15408 > URL: https://issues.jboss.org/browse/JBIDE-15408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Live Reload is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Live Reload by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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-15495) OpenShift publication locks the whole workspace

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15495: --------------------------------------- awesome :-) > OpenShift publication locks the whole workspace > ----------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- 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