[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk edited comment on JBDS-2866 at 12/18/13 9:22 AM:
-------------------------------------------------------------
{quote}
I could have opened this debugger not only in Chrome but in any browser
{quote}
I was wrong here ^:
- it should be a webkit based browser;
- browser should have an appropriate websocket support.
The point is that Java 7 FX Web View doesn't have websocket support - https://javafx-jira.kenai.com/browse/RT-14947 . However it is fixed in JDK 8 Lombard. So, I believe that oracle JDK 8, that will be released on the 18th of March 2014 (according to the Oracle schedule), is a requirement for the debugger. I have tested it with early build of the JDK 8 on Windows https://jdk8.java.net/download.html - works fine
was (Author: ibuziuk):
{quote}
I could have opened this debugger not only in Chrome but in any browser
{quote}
I was wrong here ^:
- it should be a webkit based browser;
- browser should have an appropriate websocket support.
The point is that Java 7 FX Web View doesn't have websocket support - https://javafx-jira.kenai.com/browse/RT-14947 . However it is fixed in JDK 8 Lombard. So, I believe that oracle JDK 8, that will be release on the 18th of March 2014 (according to the Oracle schedule), is a requirement for the debugger. I have tested it with early build of the JDK 8 on Windows https://jdk8.java.net/download.html - works fine
> 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, 3 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16309:
----------------------------------------
I'm more interested in your answer to "is it a good step, should we adopt it now?". I'm feeling we're trying to resolve too many things at the same time. The idea in this change is more to reduce coupling on parent pom (by getting rid of the composite and definition of "whole JBT sites" in parent pom), and to introduce the right parameters to make it easier to re-use parent pom across streams.
Move to Nexus could be discussed in JBIDE-16128 which is actually an independent issue.
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16309:
---------------------------------------------
To be clear - I don't think parent pom should set these. That would hardwire the parent pom to a specific stream afaics and we would still have the problem of not being able to release components independently of the parent pom.
With move to nexus - yeah, if each component have its own versions then this will be pretty crazy to maintain (i.e. *everyone* including agregator/mirror jobs need to sync on specific versions) - not sure how we can avoid/reduce that or maybe add some consistency check ?
Got any suggestions or am I making it more complex than need be ?
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16309:
----------------------------------------
PR for parent pom: https://github.com/jbosstools/jbosstools-build/pull/131
Adapted PR for consumer: https://github.com/jbosstools/jbosstools-javaee/pull/186 (builds fine using parent pom as suggested above)
Also, something to keep in mind is that if we move to Nexus, this jbosstools-build-stream will tend to disappear and be replaced by actual project version.
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-16309 at 12/18/13 7:25 AM:
------------------------------------------------------------------
Extracting the "jbt.upstream.repo" and setting it in parent pom sounds like a good idea which doesn't add difficulty.
I can set this in parent pom and update the example commit to use it in URL.
About prefixing URLs with stream instead of suffixing, I'm ok with this, but it is a bigger change (implies changes in conventions and publish.sh). So I'd vote for doing this later.
{quote}the important part is we don't require users to think about which branch/profile they need to use {quote}
parent pom will always set the best default
was (Author: mickael_istria):
Extracting the "${jbt.upstream.repo}" and setting it in parent pom sounds like a good idea which doesn't add difficulty.
I can set this in parent pom and update the example commit to use it in URL.
About prefixing URLs with stream instead of suffixing, I'm ok with this, but it is a bigger change (implies changes in conventions and publish.sh). So I'd vote for doing this later.
{quote}the important part is we don't require users to think about which branch/profile they need to use {quote}
parent pom will always set the best default
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16280:
----------------------------------------
> we are not delaying alpha1 for this.
In its current state, anyone who install Alpha1 on Linux will have his workbench crashing within a few seconds. Are you sure it's a good behaviour for Alpha1?
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Fix For: 4.2.0.Alpha2
>
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
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