January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16335) Replace hard-coded cartridge names with openshift-java-client constants

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16335?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16335: ------------------------------------------ merged upstream master > Replace hard-coded cartridge names with openshift-java-client constants > ----------------------------------------------------------------------- > > Key: JBIDE-16335 > URL: https://issues.jboss.org/browse/JBIDE-16335 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: cleanup > Fix For: 4.2.0.Alpha2 > > > EmbedCartridgeStrategy, the class that is responsible for the requirements when selecting embeddable cartridges, is using plain-text cartridge names where it could use openshift-java-client constants. > We should clean this up. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16007) setup blog/news section

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16007?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-16007: --------------------------------------- there's still an issue with images location fro tagged pages > setup blog/news section > ----------------------- > > Key: JBIDE-16007 > URL: https://issues.jboss.org/browse/JBIDE-16007 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.0.x > > > Blog supporting asciidoc and md. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16294) JQuery Mobile 1.4 data-* content assist

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16294?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16294: ----------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.x) > JQuery Mobile 1.4 data-* content assist > --------------------------------------- > > Key: JBIDE-16294 > URL: https://issues.jboss.org/browse/JBIDE-16294 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > > http://api.jquerymobile.com/data-attribute/ -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16294) JQuery Mobile 1.4 data-* content assist

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16294?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16294: ----------------------------------- Description: http://api.jquerymobile.com/data-attribute/ > JQuery Mobile 1.4 data-* content assist > --------------------------------------- > > Key: JBIDE-16294 > URL: https://issues.jboss.org/browse/JBIDE-16294 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.x > > > http://api.jquerymobile.com/data-attribute/ -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16294) JQuery Mobile 1.4 data-* content assist

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16294?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16294: ----------------------------------- Summary: JQuery Mobile 1.4 data-* content assist (was: HTML5 Content Assist: Support JQuery Mobile 1.4) > JQuery Mobile 1.4 data-* content assist > --------------------------------------- > > Key: JBIDE-16294 > URL: https://issues.jboss.org/browse/JBIDE-16294 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.x > > -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16337) Support debugging of Cordova applications via Weinre and/or WebView debugging support

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-16337: --------------------------------------- Summary: Support debugging of Cordova applications via Weinre and/or WebView debugging support Key: JBIDE-16337 URL: https://issues.jboss.org/browse/JBIDE-16337 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Affects Versions: 4.1.1.Final Reporter: Vineet Reynolds Priority: Minor Currently, to debug Cordova app running on an emulator or a device (not CordovaSim), one needs to use Weinre (with no JS breakpoint capabilities) or use Safari/Chrome remote debugging (that supports debugging of WebViews with JS breakpoints). It would be nice to have this integrated via a "Debug As" menu, so that end-users dont have to * setup and run Weinre, or * add the webview-debug Cordova plugin to debug Chrome WebViews on Android 4.4 All debugging strategies are listed here: https://github.com/phonegap/phonegap/wiki/Debugging-in-PhoneGap in case additional techniques can be considered. I'm assigning this a priority of minor, since this could be done manually, but bump up if appropriate. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2669: ---------------------------------- If we're taking the time to refactor, I'd like to see us move to *com.jboss.devstudio* or *com.redhat.jbdevstudio*, rather than keeping com.jboss.jbds since it's inconsistent w/ other namespaces used to refer to devstudio/jbdevstudio. So, +1 for Option D (if everyone likes the somewhat unneeded ".core." segment), _once we decide on which namespace to use_. [~maxandersen] with your new powers of better email management, which would you rather see? Option D1: As above but using *com.jboss.devstudio.core* instead of com.jboss.jbds namespace Option D2: As above but using *com.redhat.jbdevstudio.core* instead of com.jboss.jbds namespace Option D3: As above but using *com.jboss.devstudio* instead of com.jboss.jbds namespace (drop the .core segment) Option D4: As above but using *com.redhat.jbdevstudio* instead of com.jboss.jbds namespace (drop the .core segment) > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2669: ------------------------------------- Good catch, fixed feature id. There is no reason mark it as *.branding, because it is not only branding. Usage is a different story, usage.branding contains service implementation which provides labels for usage UI in JBDS. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-2669 at 1/7/14 2:42 PM: ------------------------------------------------------------- *Option D* Plug-ins usually don't use suffix ".plugin" and it is not plug-in anymore, but bundle; *.core.* to be consistent with JBossTools Core {code}com.jboss.jbds.product => com.jboss.jbds.core{code} Features usually named after branding plugins w/ or w/o suffix ".feature" all our features have suffix {code}com.jboss.jbds.product.feature => com.jboss.jbds.core.feature {code} This is meta IU ID generated for .product file and I agree that "package" would look better here than "all" and core for consistency {code}com.jboss.jbds.all => com.jboss.jbds.core.package{code} This id I believe should match product id defined through extension point in branding plugin and it forms as <plug-in-id>.<extension-point-id> {code}com.jboss.jbds.product.product => com.jboss.jbds.core.product{code} was (Author: dgolovin): *Option D* Plug-ins usually don't use suffix ".plugin" and it is not plug-in anymore, but bundle; *.core.* to be consistent with JBossTools Core {code}com.jboss.jbds.product => com.jboss.jbds.core{code} Features usually named after branding plugins w/ or w/o suffix ".feature" all our features have suffix {code}com.jboss.jbds.product.feature => com.jboss.devstudio.core.feature {code} This is meta IU ID generated for .product file and I agree that "package" would look better here than "all" and core for consistency {code}com.jboss.jbds.all => com.jboss.jbds.core.package{code} This id I believe should match product id defined through extension point in branding plugin and it forms as <plug-in-id>.<extension-point-id> {code}com.jboss.jbds.product.product => com.jboss.jbds.core.product{code} > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2866) CordovaSim Debugger

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-2866: ----------------------------------- {quote} Do you have a HD version of this video? {quote} [~burrsutter], you should choose 720p HD quality on the YouTube. {quote} For instance, it would appear that you are not using the JS editors in Eclipse but some 3rd party window for JS editing. {quote} Yes, I have set Sublime Text editor as a default in the eclipse. Eclipse js editor was absolutely unusable when I worked with ripple source code (3mb of js). Since then I got used to the Sublime :-) > CordovaSim Debugger > ------------------- > > Key: JBDS-2866 > URL: https://issues.jboss.org/browse/JBDS-2866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim, requirements > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Attachments: DevToolsMenu.png > > > The current FireBug Lite in CordovaSim has the following limitations: > 1) When using LiveReload, the window closes with every reload > 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready > http://screencast.com/t/RRGhV9PV > Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message -- 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

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014