[JBoss JIRA] (JBIDE-13436) jQuery: Code completion for all the available IDs for <a href="#...">
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13436:
-----------------------------------
Summary: jQuery: Code completion for all the available IDs for <a href="#..."> (was: jQuery Mobile: Code completion for all the available IDs for <a href="#...">)
> jQuery: Code completion for all the available IDs for <a href="#...">
> ---------------------------------------------------------------------
>
> Key: JBIDE-13436
> URL: https://issues.jboss.org/browse/JBIDE-13436
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
> Attachments: scr.png
>
>
> Suppose we have a multi-page document:
> {code}
> <body>
> <div data-role="page" id="foo">
> ...
> <a href="#bar">bar</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> <div data-role="page" id="bar">
> ...
> <a href="#foo">Back to foo</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> </body>
> {code}
> Another example:
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a> <!-- Ctrl+Space for href="# shows popupBasic id -->
> <div data-role="popup" id="popupBasic">
> ...
> </div>
> {code}
> !scr.png!
--
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
[JBoss JIRA] (JBIDE-13823) jQuery: OpenOns (Ctrl+Click) for element IDs within the page
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-13823:
--------------------------------------
Summary: jQuery: OpenOns (Ctrl+Click) for element IDs within the page
Key: JBIDE-13823
URL: https://issues.jboss.org/browse/JBIDE-13823
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.0.Alpha2
Suppose we have a multi-page document:
{code}
<body>
<div data-role="page" id="foo">
...
<a href="#bar">bar</a> <!-- code completion for href="#| will show "foo" and "bar" -->
...
</div>
<div data-role="page" id="bar">
...
<a href="#foo">Back to foo</a> <!-- code completion for href="#| will show "foo" and "bar" -->
...
</div>
</body>
{code}
Another example:
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a> <!-- Ctrl+Space for href="# shows popupBasic id -->
<div data-role="popup" id="popupBasic">
...
</div>
{code}
!scr.png!
--
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
[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available IDs for <a href="#...">
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13436:
-----------------------------------
Labels: new_and_noteworthy (was: )
> jQuery Mobile: Code completion for all the available IDs for <a href="#...">
> ----------------------------------------------------------------------------
>
> Key: JBIDE-13436
> URL: https://issues.jboss.org/browse/JBIDE-13436
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
> Attachments: scr.png
>
>
> Suppose we have a multi-page document:
> {code}
> <body>
> <div data-role="page" id="foo">
> ...
> <a href="#bar">bar</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> <div data-role="page" id="bar">
> ...
> <a href="#foo">Back to foo</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> </body>
> {code}
> Another example:
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a> <!-- Ctrl+Space for href="# shows popupBasic id -->
> <div data-role="popup" id="popupBasic">
> ...
> </div>
> {code}
> !scr.png!
--
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
[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available IDs for <a href="#...">
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13436:
-----------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.x)
> jQuery Mobile: Code completion for all the available IDs for <a href="#...">
> ----------------------------------------------------------------------------
>
> Key: JBIDE-13436
> URL: https://issues.jboss.org/browse/JBIDE-13436
> 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.0.Alpha2
>
> Attachments: scr.png
>
>
> Suppose we have a multi-page document:
> {code}
> <body>
> <div data-role="page" id="foo">
> ...
> <a href="#bar">bar</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> <div data-role="page" id="bar">
> ...
> <a href="#foo">Back to foo</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> </body>
> {code}
> Another example:
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a> <!-- Ctrl+Space for href="# shows popupBasic id -->
> <div data-role="popup" id="popupBasic">
> ...
> </div>
> {code}
> !scr.png!
--
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
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13818:
-------------------------------------------------
Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 923369|https://bugzilla.redhat.com/show_bug.cgi?id=923369]
could not reproduce it using 2 devenv's agupta gave me. Build #27 was stable again (blue) and #28 failed again on the very same error ("could not restart stopped application"). I'm wondering: is this timing related?
> openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
> -------------------------------------------------------------------------
>
> Key: JBIDE-13818
> URL: https://issues.jboss.org/browse/JBIDE-13818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
> In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
> https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
> {code}
> Fehlermeldung
> Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> Stacktrace
> com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
> Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> at com.openshift.internal.client.RestService.request(RestService.java:106)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
> at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
> at com.openshift.internal.client.RestService.request(RestService.java:144)
> at com.openshift.internal.client.RestService.request(RestService.java:98)
> ... 69 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
> ... 73 more
> Standard Ausgabe (STDOUT)
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> {code}
--
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
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13631:
------------------------------------------
filed https://bugzilla.redhat.com/show_bug.cgi?id=923442 and added this issue as external issue to get updates reported here.
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
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
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13631:
-------------------------------------
Bugzilla Update: (was: Perform)
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
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
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration updated JBIDE-13631:
--------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=916268, https://bugzilla.redhat.com/show_bug.cgi?id=923442 (was: https://bugzilla.redhat.com/show_bug.cgi?id=916268)
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
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
[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available IDs for <a href="#...">
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13436:
-----------------------------------
Attachment: scr.png
> jQuery Mobile: Code completion for all the available IDs for <a href="#...">
> ----------------------------------------------------------------------------
>
> Key: JBIDE-13436
> URL: https://issues.jboss.org/browse/JBIDE-13436
> 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: scr.png
>
>
> Suppose we have a multi-page document:
> {code}
> <body>
> <div data-role="page" id="foo">
> ...
> <a href="#bar">bar</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> <div data-role="page" id="bar">
> ...
> <a href="#foo">Back to foo</a> <!-- code completion for href="#| will show "foo" and "bar" -->
> ...
> </div>
> </body>
> {code}
> Another example:
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a> <!-- Ctrl+Space for href="# shows popupBasic id -->
> <div data-role="popup" id="popupBasic">
> ...
> </div>
> {code}
--
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