January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13403) Code completion for jQuery Mobile HTML attributes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13403?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13403: ----------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > Code completion for jQuery Mobile HTML attributes > ------------------------------------------------- > > Key: JBIDE-13403 > URL: https://issues.jboss.org/browse/JBIDE-13403 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > > For example: > We can provide code completion for jQuery specific HTML5 attributes of html tags (such as data-*): > {code} > <a data-(role|transition|inline|...)> > {code} > and for attributes values: > {code} > <a data-transition="fade|pop|flip|..." ...> > {code} > See http://jquerymobile.com/demos/1.2.0/docs/api/data-attributes.html -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13425) Enhance astools api to centralize default launch arguments

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13425?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13425: ------------------------------------- I have carefully done the following: 1) created a new semi-api (provincial api?) inside the extended server properties to house things such as default launch args and stop args 2) I have redirected all old uses to the new use, and have marked the old apis as deprecated 3) I have marked some of our internal protected methods as deprecated, specifically 4 in the server behavior delegate classes which were found to be confusing the flow of logic and execution. 4) A bug years ago caused us to have to set a server's mode to STARTING before it could be set to STARTED. While I cannot find the bugzilla for this old entry, the effect this had was that if we were ignoring launches, we must set it to STARTING before STARTED. Unfortunately, this would have the effect of launching a ping thread even when we didnt want to (also internal, since when the server is set to starting is when we launch the ping thread). In these instances, and since the upstream bug has been fixed (revealed through ample tracing), the call to starting is not necessary, adn we can set directly to started. 5) Small differences between the various class heirarchies were investigated to see if they were there for a purpose or if they were an oversight. Many were unified and the overriding subclass's method was removed in favor of the super-classes fixed impl. 6) Obscure use cases such as starting the server outside of the workspace (and the server editor having the 'externally launched' checkbox checked) were also investigated, so that their logic could be extended to as7. (example, in these cases, using a shutdown poller of watching for a terminated process did not work and a different poller would need to be used) Issues regarding api compatability: 1) Removed 2 unused constants in LocalJBoss71ServerRuntime, a very internal class nobody should be referencing 2) A very internal class RSEJBoss7LaunchConfigurator has had some of its protected method signatures changed. 3) RSELaunchConfigurator had its constructor changed. This is not a class anyone should be instantiating anywhere. All other changes were made in such a way as to maintain binary compatability. This was tested by manually starting 8 different server types both locally, remotely, locally with 'skip launch' flag, and remotely via cmd line and then in eclipse with 'skip launch' flag. > Enhance astools api to centralize default launch arguments > ----------------------------------------------------------- > > Key: JBIDE-13425 > URL: https://issues.jboss.org/browse/JBIDE-13425 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: JBossAS/Servers > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > Runtime interface, and behavior delegates, are full of code involving default start and stop launch arguments. These should be centralized in an interface accessible via the extended properties model. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12974: --------------------------------------- No, I don't think we need 3 update sites. Note that this JIRA is titled "add missing IUs to coretests and soatests sites" - my original assumption was that the bot tests would be just added to the existing update sites. Also, we (QE) never used the components' unit tests for our testing - the only plugins from the coretests update site that we used to use were probably bot ext and perhaps some others. But not the usual unit tests. So what's next? Can you merge the bot tests into coretests and soatests (depending on the test name) and disabled integration-tests? > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.0.Alpha1 > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2444) JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2444?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky resolved JBDS-2444. ------------------------------------- Resolution: Done Fixed in 5.0.3.GA-SOA > JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later > -------------------------------------------------------------------------------------------------- > > Key: JBDS-2444 > URL: https://issues.jboss.org/browse/JBDS-2444 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.2.GA-SOA > Environment: Version: 5.0.2.GA > Build id: v20130103-0154-H238-GA > Build date: 20130103-0154 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.2.GA.soa-to... > SOA-P 5.3.1.ER2 and later > Reporter: Len DiMaggio > Assignee: Douglas Palmer > Priority: Blocker > Labels: respin-b > Fix For: 5.0.3.GA-SOA > > Attachments: Screenshot.png > > > The error raised is: > Error occurred while loading JBoss ESB 4.11.1 runtime . Please select a correct JBoss ESB runtime or JBoss ESB server location > See attached screenshot. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2444) JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2444?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBDS-2444. ----------------------------------- Verified with SOA Tooling 5.0.3.v20130128-1900-H4-GA > JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later > -------------------------------------------------------------------------------------------------- > > Key: JBDS-2444 > URL: https://issues.jboss.org/browse/JBDS-2444 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.2.GA-SOA > Environment: Version: 5.0.2.GA > Build id: v20130103-0154-H238-GA > Build date: 20130103-0154 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.2.GA.soa-to... > SOA-P 5.3.1.ER2 and later > Reporter: Len DiMaggio > Assignee: Douglas Palmer > Priority: Blocker > Labels: respin-b > Fix For: 5.0.3.GA-SOA > > Attachments: Screenshot.png > > > The error raised is: > Error occurred while loading JBoss ESB 4.11.1 runtime . Please select a correct JBoss ESB runtime or JBoss ESB server location > See attached screenshot. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11774) Create New ESB Project wizard - wrong warning message

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11774?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-11774. ------------------------------------- Verified with SOA Tooling 5.0.3.v20130128-1900-H4-GA > Create New ESB Project wizard - wrong warning message > ----------------------------------------------------- > > Key: JBIDE-11774 > URL: https://issues.jboss.org/browse/JBIDE-11774 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: SOA Tooling > Affects Versions: 3.3.0.Beta2-SOA > Environment: Eclipse 3.7.2, JBoss ESB Tools 1.5.0.v20120501-1800-H851-CR1 > Reporter: Andrej Podhradsky > Assignee: Brian Fitzpatrick > Priority: Trivial > Fix For: 4.0.0.Alpha1-SOA > > Attachments: JBIDE-11774-git-master.patch, JBIDE-11774-svn-3.3.x.patch, newEsbProject1.png, newEsbProject2.png, newEsbProject3.png > > > "Install ESB Facet" page displays wrong warning, see "Steps to Reproduce". -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13413: ---------------------------------------- If we able to insert a browser as a SWT widget (not sure it's possible) then it would be much easier for us than crating SWT widgets to simulate html rendering for our html code. We just show the generated html there. > jQuery Mobile Widget Palette > ---------------------------- > > Key: JBIDE-13413 > URL: https://issues.jboss.org/browse/JBIDE-13413 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > Attachments: NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, withwithoutpreview.bmml, withwithoutpreview.png > > > http://jquerymobile.com/test/ > See my proposal regarding the content of jQuery Mobile palette below. > Also I have an idea to add a live preview into each wizard. > We could try to add a browser to the wizard which will show how the widget is going to look. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13413: --------------------------------------------- Actually after looking through the jquery examples and how its tricky for a newbie to actually map some of the properties/buttons to what they actually mean I'm saying maybe it makes sense to do a browse preview just using basic theme/style from jquery if possible. Something like: !withwithoutpreview.png! > jQuery Mobile Widget Palette > ---------------------------- > > Key: JBIDE-13413 > URL: https://issues.jboss.org/browse/JBIDE-13413 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > Attachments: NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, withwithoutpreview.bmml, withwithoutpreview.png > > > http://jquerymobile.com/test/ > See my proposal regarding the content of jQuery Mobile palette below. > Also I have an idea to add a live preview into each wizard. > We could try to add a browser to the wizard which will show how the widget is going to look. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13413: --------------------------------------------- Having a preview of what the about to injected text will look like would be easier to understand and visualize than a browser since the browser wouldn't have all the right styling anyway would it ? > jQuery Mobile Widget Palette > ---------------------------- > > Key: JBIDE-13413 > URL: https://issues.jboss.org/browse/JBIDE-13413 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > Attachments: NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png > > > http://jquerymobile.com/test/ > See my proposal regarding the content of jQuery Mobile palette below. > Also I have an idea to add a live preview into each wizard. > We could try to add a browser to the wizard which will show how the widget is going to look. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-9) JBossTools Integration Stack :: JBPM: Verify the component configuration of the initial IS tooling release.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBTIS-9?page=com.atlassian.jira.plugin.sy... ] Koen Aers commented on JBTIS-9: ------------------------------- Hi Paul, I have never dealt with the above artifacts. What exactly do you want me to do with them? Cheers, Koen > JBossTools Integration Stack :: JBPM: Verify the component configuration of the initial IS tooling release. > ----------------------------------------------------------------------------------------------------------- > > Key: JBTIS-9 > URL: https://issues.jboss.org/browse/JBTIS-9 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JBPM > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Koen Aers > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- 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

13 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 2013