[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Romaine Herrera (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Romaine Herrera edited comment on JBIDE-2720 at 12/13/13 12:20 PM:
-------------------------------------------------------------------
[~carsten.pfeiffer] Can you walk me through on how to deal with that bug that Julius Fingerle found? because I dont know how to fix it and can you send me the steps by steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com, Thank you.
was (Author: dagz213):
[~carsten.pfeiffer] Can you walk me through on how to deal with that bug? because I dont know how to fix it and can you send me the steps by steps on how to deal with it from the start coz im a starting student. Can you post it here or send it to my email: pizza_aldwyn(a)yahoo.com, Thank you.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
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, 4 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2866:
-----------------------------------
One critical test case is...does it work with something like
$.getJSON("http://mobile-html5.rhcloud.com/rest/members", function(data)
without giving you the dreaded
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.
> 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
>
> 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
12 years, 4 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2866:
-----------------------------------
It seems like FireBug Lite is too limited to actually be useful in its current form. And I remember seeing a demo from Google that shows how to make Chrome Dev Tools work with a USB connected Android device, where the presenter also said there was a way to use desktop Safari and iOS Safari for remote debugging there as well (only on Macs obviously).
The reason this is "bugging" me is that I literally have a JS bug in my Cordova app that I have been unable to track down via FireBug Lite :-)
> 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
>
> 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
12 years, 4 months
[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}
How can the end-user (me) "push" my project into Chrome/FireFox to take advantage those debuggers?
{quote}
[~burrsutter], actually it is not Chrome debugger on the demo. It is embedded Chrome Dev tools debugger. I could have opened this debugger not only in Chrome but in any browser. In the end there will be menu item in BrowserSim / CordovaSim: Debugger -> Chrome Dev Tools. Just like FireBugLite now.
> 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
>
> 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
12 years, 4 months
[JBoss JIRA] (JBIDE-16302) Make jobs suffix = stream (eg 4.2.luna instead of 42)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16302?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16302:
----------------------------------------
I was in a "discussing is a waste of time" mood and I was impatient to see the stream controlled by a single property by anticipation of the "dependencies in root pom" topic (which we could/should adopt immediatly IMO).
I chose 4.2.luna because it is more explicit and contains more useful info that 42 (which newcomers read as fourty-two, which doesn't make sense in our context). I also believe that it is more dangerous/critical to expected convention for aggregate and composite URLs, as those sites (aggregate and composites) are actually consumed by other parts of the build chain (product).
> Make jobs suffix = stream (eg 4.2.luna instead of 42)
> -----------------------------------------------------
>
> Key: JBIDE-16302
> URL: https://issues.jboss.org/browse/JBIDE-16302
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> In order to reduce the amount of conventions and allow better factorization, we should get rid of the current convention (jobname_42) on job/nightly-build/staging names and replace it by the same convention as _composite_ and aggregate site (4.2.luna).
> For example:
> * jbosstools-central_42 => jbosstools-central_4.2.luna
> * as a consequence download.jboss.org/jbosstools/builds/staging/jbosstools-central_42/ => download.jboss.org/jbosstools/builds/staging/jbosstools-central_4.2.luna/
> And
> * devstudio.product_80 => devstudio.product_8.0.luna
--
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, 4 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2866:
-----------------------------------
Perhaps a short-term workaround to the challenge and perhaps something we can tweak in the tooling...
how can the end-user (me) "push" my project into Chrome/FireFox to take advantage those debuggers? At this moment, if you open index.html in Chrome directly, it will complain that there is no cordova.js in the local filesystem.
> 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
>
> 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
12 years, 4 months
[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15888:
-------------------------------------
Since the latest spring archetype depends on WFK 2.4 and has no community counterpart, we need to add it to the stacks.yaml, so a warning can be displayed if WFK deps can't be resolved. Both community and product runtimes use the exact same version.
Here's the procedure for QE to check the archetype works (we can't test the spring wizard from Central directly):
* Remove the redhat maven repo from your settings.xml
* Delete .m2/repository/org/jboss/bom/
* Add -Dorg.jboss.tools.stacks.url_stacks=https://raw.github.com/fbricon/jdf-stack/patch-3/stacks.yaml to your eclipse.ini or jbdevstudio.ini
* Open JBDS/Eclipse preferences and go to JBoss Tools > Project Examples
* check show experimental sites
* Click the Add button and add https://issues.jboss.org/secure/attachment/12379586/springmvc-test.xml
* Open the project examples wizard from JBoss Central
* select Spring MVC project from the "Staging - JBoss Maven Archetype category" and click next
* assert the description contains "Project based on the org.jboss.spring.archetypes:jboss-spring-mvc-archetype:1.0.3.Final Maven archetype"
* assert a warning is displayed (http://screencast.com/t/bJFHTGLmf2l)
* add the required repo and proceed (the warning will still be displayed as per JBIDE-16287)
* The project is created but has an error is :
{quote}
cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected.
{quote}
That's known as JBIDE-15311.
In jboss-deployment-structure.xml, replacing
{quote}
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">{quote} with {quote}<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:2.0">{quote} fixes the issue
[~burrsutter] : are you ok to put that archetype in JBoss Central, given the problems it has (requires WFK repo + bad jboss-deployment-structure.xml)?
> Update the Spring Archetype reference
> -------------------------------------
>
> Key: JBIDE-15888
> URL: https://issues.jboss.org/browse/JBIDE-15888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Joshua Wilson
> Assignee: Fred Bricon
> Labels: spring
> Fix For: 4.1.1.Final
>
> Attachments: springmvc-test.xml
>
>
> I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version.
--
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, 4 months