[JBoss JIRA] (JBIDE-15494) Software/Update page - Cannot create temporary directory
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15494?page=com.atlassian.jira.plugi... ]
Karel Piwko commented on JBIDE-15494:
-------------------------------------
Reverting back to Oracle JDK 1.7.0_25 fixes the problem of "cannot create temporary directory". And BrowserSim problem is not related to JDK version.
> Software/Update page - Cannot create temporary directory
> --------------------------------------------------------
>
> Key: JBIDE-15494
> URL: https://issues.jboss.org/browse/JBIDE-15494
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Final, 4.1.1.Alpha1
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.1.Alpha2
>
>
> Recently, Software/Update page of JBoss Central stopped working (No Connectors Found).
> Error log:
> {noformat}
> Cannot download bundle at http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...: Unable to create temporary file
> {noformat}
> {noformat}
> a.io.IOException: Unable to create temporary file
> at java.io.File$TempDirectory.generateFile(File.java:1891)
> at java.io.File.createTempFile(File.java:1979)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
> This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in 7.0.0.Final (4.1.0.Final), thus it's marked as blocker.
--
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
[JBoss JIRA] (JBIDE-12274) BrowserSim borks on jquery mobile (RHEL 6.1)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12274?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-12274:
-------------------------------------------------
Karel Piwko <kpiwko(a)redhat.com> made a comment on [bug 966571|https://bugzilla.redhat.com/show_bug.cgi?id=966571]
Got over JBIDE-15494. The issue is not fixed, I'm still experiencing blank window.
# rpm -qa webkitgtk
webkitgtk-1.2.6-5.el6.x86_64
> BrowserSim borks on jquery mobile (RHEL 6.1)
> --------------------------------------------
>
> Key: JBIDE-12274
> URL: https://issues.jboss.org/browse/JBIDE-12274
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: RHEL 6.1
> JBoss Developer Studio 5.0.0.CR1
> Reporter: Gabriel De Repentigny
> Assignee: Yahor Radtsevich
> Labels: upstream
> Fix For: 4.0.0.Alpha1, 4.1.x
>
> Attachments: jQMrefsRemoved.png, midori-browsersim.png, midori-browsersim.png, python-tabbed-browser.png, Screenshot-BrowserSim .png, windows-7_Safari-5.1.2-7534.52.7.png
>
>
> I'm walking through the JBoss Way Ticket Monster lab. JDS's BrowserSim borks while trying to render mobile.html (pasted below) which is part of the tutorial.
> The problem seems to be with the jquery mobile js file. If you take that include out, it renders (sans-mobile styling).
> {code:xml}
> <!DOCTYPE html>
> <html>
> <head>
> <title>jQuery Mobile Template</title>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
> <meta name="viewport" content="width=device-width, initial-scale=1" />
> <link rel="stylesheet"
> href="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.css" />
> <script type="text/javascript"
> src="http://code.jquery.com/jquery-1.7.1.min.js"></script>
> <script type="text/javascript"
> src="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.js"></script>
> <script type="text/javascript">
> $(document).on("pageinit", "#page1", function(event){
> alert("Ready To Go");
> });
> $.getJSON("rest/events", function(events) {
> // console.log("returned are " + results);
> var listOfEvents = $("#listOfItems");
> listOfEvents.empty();
> $.each(events, function(index, event) {
> // console.log(event.name);
> listOfEvents.append("<li><a href=’#’>" + event.name + "</a>");
> });
> listOfEvents.listview("refresh");
> });
> </script>
> </head>
> <body>
> <div data-role="page" id="page1">
> <div data-role="header">
> <h1>jQuery Mobile</h1>
> </div>
> <div data-role="content">
> <ul id="listOfItems" data-role="listview" data-inset="true"
> data-filter="true">
> <li><a href="">One</a></li>
> <li><a href="">Two</a></li>
> <li><a href="">Three</a></li>
> </ul>
> </div>
> <div data-role="footer">
> <h4>www.jboss.org/developer</h4>
> </div>
> </div>
> </body>
> </html>
> {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
12 years, 7 months
[JBoss JIRA] (JBIDE-12274) BrowserSim borks on jquery mobile (RHEL 6.1)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12274?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-12274:
-------------------------------------------------
Karel Piwko <kpiwko(a)redhat.com> changed the Status of [bug 966571|https://bugzilla.redhat.com/show_bug.cgi?id=966571] from ON_QA to ASSIGNED
> BrowserSim borks on jquery mobile (RHEL 6.1)
> --------------------------------------------
>
> Key: JBIDE-12274
> URL: https://issues.jboss.org/browse/JBIDE-12274
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: RHEL 6.1
> JBoss Developer Studio 5.0.0.CR1
> Reporter: Gabriel De Repentigny
> Assignee: Yahor Radtsevich
> Labels: upstream
> Fix For: 4.0.0.Alpha1, 4.1.x
>
> Attachments: jQMrefsRemoved.png, midori-browsersim.png, midori-browsersim.png, python-tabbed-browser.png, Screenshot-BrowserSim .png, windows-7_Safari-5.1.2-7534.52.7.png
>
>
> I'm walking through the JBoss Way Ticket Monster lab. JDS's BrowserSim borks while trying to render mobile.html (pasted below) which is part of the tutorial.
> The problem seems to be with the jquery mobile js file. If you take that include out, it renders (sans-mobile styling).
> {code:xml}
> <!DOCTYPE html>
> <html>
> <head>
> <title>jQuery Mobile Template</title>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
> <meta name="viewport" content="width=device-width, initial-scale=1" />
> <link rel="stylesheet"
> href="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.css" />
> <script type="text/javascript"
> src="http://code.jquery.com/jquery-1.7.1.min.js"></script>
> <script type="text/javascript"
> src="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.js"></script>
> <script type="text/javascript">
> $(document).on("pageinit", "#page1", function(event){
> alert("Ready To Go");
> });
> $.getJSON("rest/events", function(events) {
> // console.log("returned are " + results);
> var listOfEvents = $("#listOfItems");
> listOfEvents.empty();
> $.each(events, function(index, event) {
> // console.log(event.name);
> listOfEvents.append("<li><a href=’#’>" + event.name + "</a>");
> });
> listOfEvents.listview("refresh");
> });
> </script>
> </head>
> <body>
> <div data-role="page" id="page1">
> <div data-role="header">
> <h1>jQuery Mobile</h1>
> </div>
> <div data-role="content">
> <ul id="listOfItems" data-role="listview" data-inset="true"
> data-filter="true">
> <li><a href="">One</a></li>
> <li><a href="">Two</a></li>
> <li><a href="">Three</a></li>
> </ul>
> </div>
> <div data-role="footer">
> <h4>www.jboss.org/developer</h4>
> </div>
> </div>
> </body>
> </html>
> {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
12 years, 7 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Sande Gilda (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Sande Gilda commented on JBDS-2727:
-----------------------------------
[~snjeza]: Thanks so much for reviewing the guide. I have made adjustments and issued this pull:
https://github.com/jboss-jdf/jboss-as-quickstart/pull/618
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
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