March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16692) Caching for Cordova plug-in registry

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16692?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16692: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Beta2) Assignee: Gorkem Ercan > Caching for Cordova plug-in registry > ------------------------------------ > > Key: JBIDE-16692 > URL: https://issues.jboss.org/browse/JBIDE-16692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha2 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The data retrieved from the Cordova plug-in registry is not cached and retrieved every time. We should have a caching mechanism so that subsequent calls to the registry are faster. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-472) Debugging OpenShift application: How to find out debugging port

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-472?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-472: ------------------------------------- Fix Version/s: 4.2.0.Final > Debugging OpenShift application: How to find out debugging port > --------------------------------------------------------------- > > Key: TOOLSDOC-472 > URL: https://issues.jboss.org/browse/TOOLSDOC-472 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.1.2 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 28-02-2014 19:54:11 > Topic ID: 28342-590341 [Specified] > Reporter: Marián Labuda > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > It should be "nice to have" some information about "how to find debugging port" as Note. > I suggest something like (this is just simple example, it should be written in more comfortable way): > At first check available port in Port forwarding shell. After enabling debugging by creating and pushing OpenShift JPDA marker check ports and the new one is port for debugging. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-472) Debugging OpenShift application: How to find out debugging port

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-472?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-472: ------------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Debugging OpenShift application: How to find out debugging port > --------------------------------------------------------------- > > Key: TOOLSDOC-472 > URL: https://issues.jboss.org/browse/TOOLSDOC-472 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.1.2 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 28-02-2014 19:54:11 > Topic ID: 28342-590341 [Specified] > Reporter: Marián Labuda > Assignee: Michelle Murray > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > It should be "nice to have" some information about "how to find debugging port" as Note. > I suggest something like (this is just simple example, it should be written in more comfortable way): > At first check available port in Port forwarding shell. After enabling debugging by creating and pushing OpenShift JPDA marker check ports and the new one is port for debugging. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-472) Debugging OpenShift application: How to find out debugging port

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-472?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-472: ------------------------------------- Affects Version/s: 4.1.2 > Debugging OpenShift application: How to find out debugging port > --------------------------------------------------------------- > > Key: TOOLSDOC-472 > URL: https://issues.jboss.org/browse/TOOLSDOC-472 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.1.2 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 28-02-2014 19:54:11 > Topic ID: 28342-590341 [Specified] > Reporter: Marián Labuda > Assignee: Michelle Murray > > It should be "nice to have" some information about "how to find debugging port" as Note. > I suggest something like (this is just simple example, it should be written in more comfortable way): > At first check available port in Port forwarding shell. After enabling debugging by creating and pushing OpenShift JPDA marker check ports and the new one is port for debugging. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16720) OpenShift server adapter use case for Data Virtualization

by Mark Drilling (JIRA)

Mark Drilling created JBIDE-16720: ------------------------------------- Summary: OpenShift server adapter use case for Data Virtualization Key: JBIDE-16720 URL: https://issues.jboss.org/browse/JBIDE-16720 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.1.Final Reporter: Mark Drilling We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case. Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push. Currently, we connect to an OpenShift DV instance like this: 1) Deploy DV cartridge via OpenShift web console. 2) Port forward from command line using rhc port-forward 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective The issues we observed: 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo. 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list. Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13419) Support invocation handler binding extension of Deltaspike

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13419?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-13419: ------------------------------------------ Description: Objects: 1. Binding Annotations - annotation type with @PartialBeanBinding. 2. Partial Beans - abstract classes and interfaces annotated with a binding annotation. 3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation. Validation rules: 1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler. Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler." 2. There should be no more than one invocation handler for each binding annotation. Error text: "Multiple handlers are found for binding annotation %annotationName%." 3. Invocation handler class should be normal-scoped. Error text: "Invocation handler class should be a normal-scoped bean." 4. Each partial bean should be bound to an invocation handler. Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%." 5. Deltaspike implementation of the extension reads the first binding annotation on a class and ignores the next ones. Hence, they should be marked with a warning: "Binding annotation %annotationName% is ignored because class is already annotated with binding annotation %firstAnnotationName%." was: Objects: 1. Binding Annotations - annotation type with @InvocationHandlerBinding. 2. Partial Beans - abstract classes and interfaces annotated with a binding annotation. 3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation. Validation rules: 1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler. Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler." 2. There should be no more than one invocation handler for each binding annotation. Error text: "Multiple handlers are found for binding annotation %annotationName%." 3. Invocation handler class should be normal-scoped. Error text: "Invocation handler class should be a normal-scoped bean." 4. Each partial bean should be bound to an invocation handler. Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%." 5. Deltaspike implementation of the extension reads the first binding annotation on a class and ignores the next ones. Hence, they should be marked with a warning: "Binding annotation %annotationName% is ignored because class is already annotated with binding annotation %firstAnnotationName%." > Support invocation handler binding extension of Deltaspike > ---------------------------------------------------------- > > Key: JBIDE-13419 > URL: https://issues.jboss.org/browse/JBIDE-13419 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi-extensions > Affects Versions: 4.0.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.x > > > Objects: > 1. Binding Annotations - annotation type with @PartialBeanBinding. > 2. Partial Beans - abstract classes and interfaces annotated with a binding annotation. > 3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation. > Validation rules: > 1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler. > Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler." > 2. There should be no more than one invocation handler for each binding annotation. > Error text: "Multiple handlers are found for binding annotation %annotationName%." > 3. Invocation handler class should be normal-scoped. > Error text: "Invocation handler class should be a normal-scoped bean." > 4. Each partial bean should be bound to an invocation handler. > Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%." > 5. Deltaspike implementation of the extension reads the first binding annotation on a class and ignores the next ones. Hence, they should be marked with a warning: > "Binding annotation %annotationName% is ignored because class is already annotated with binding annotation %firstAnnotationName%." -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16440) Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16440?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-16440: ---------------------------------- Attachment: 1640_3.png When I open inputname.xhtml in HTML Editor (not VPE) I got this: !1640_3.png! > Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors > --------------------------------------------------------------------- > > Key: JBIDE-16440 > URL: https://issues.jboss.org/browse/JBIDE-16440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Victor Rubezhny > Assignee: Daniel Azarov > Priority: Blocker > Fix For: 4.1.2.CR1 > > Attachments: 1640_1.png, 1640_2.png, 1640_3.png, JBossToolsHTMLEditor.png, WTPHTMLEditor.png > > > It looks like we have overrode quick assist functionality in source viewer configuration that don't includes standard HTML quick fixes. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16440) Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16440?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-16440: ----------------------------------------- I can confirm that it works only if you saved your editor. The warning annotation doesn't appear if the editor content isn't saved. All works as expected for me after the editor is saved. One more thing, [~vpakan], Can you confirm that you are opening the file using JBossTools HTML Editor, not [WTP] HTML Editor? Please, double check it. > Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors > --------------------------------------------------------------------- > > Key: JBIDE-16440 > URL: https://issues.jboss.org/browse/JBIDE-16440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Victor Rubezhny > Assignee: Daniel Azarov > Priority: Blocker > Fix For: 4.1.2.CR1 > > Attachments: 1640_1.png, 1640_2.png, JBossToolsHTMLEditor.png, WTPHTMLEditor.png > > > It looks like we have overrode quick assist functionality in source viewer configuration that don't includes standard HTML quick fixes. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16440) Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16440?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-16440: --------------------------------------- One more thing: if I just change input to xyzinput and do not save the file - Warning is not displayed To see the warning I save the file after that warning is displayed and quick fixes are shown in Popup Window > Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors > --------------------------------------------------------------------- > > Key: JBIDE-16440 > URL: https://issues.jboss.org/browse/JBIDE-16440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Victor Rubezhny > Assignee: Daniel Azarov > Priority: Blocker > Fix For: 4.1.2.CR1 > > Attachments: 1640_1.png, 1640_2.png, JBossToolsHTMLEditor.png, WTPHTMLEditor.png > > > It looks like we have overrode quick assist functionality in source viewer configuration that don't includes standard HTML quick fixes. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-248) Please update JBTIS TP dependencies to Luna Alpha1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-248?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-248: ---------------------------------- Looks good. https://github.com/jbosstools/jbosstools-integration-stack/pull/181 http://download.jboss.org/jbosstools/updates/development/luna/integration... JBTIS build pending... > Please update JBTIS TP dependencies to Luna Alpha1 > -------------------------------------------------- > > Key: JBTIS-248 > URL: https://issues.jboss.org/browse/JBTIS-248 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > > Greetings - welcome to Luna! > An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3]. > I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others. > Thanks! > [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al... > [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration... -- 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, 3 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 March 2014