September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15472) Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15472?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15472 at 9/18/13 9:36 AM: ------------------------------------------------------------- Sure, it's here: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF... (See also this JIRA's description for more info.) was (Author: nickboldt): Sure, it's here: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF... (See also this JIRA's description for more info.) > Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored) > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15472 > URL: https://issues.jboss.org/browse/JBIDE-15472 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > > First iteration: https://issues.jboss.org/browse/JBIDE-15470, as generated by this: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF... > [~maxandersen] said: > {quote} i would put the details in attachment i think. its a bit overloaded otherwise I think, > btw. is this something you will run when you find a failed buid or did you say you would detect when hit a certain amont of fail you generate it ? > if auto generated shuold take care to not keep opening new jiras again andagain ;) > maybe add a "watermark" to detect stil open test failure jiras > {quote} > Idea here is to run this tool as needed when I notice that builds which are supposed to be frozen and stable are showing test failures persisting for multiple builds. Could also run against master jobs, but less critical. > Not sure what you mean by a watermark, or how that would be implemented. Please elaborate. > As this is purely a workflow optimization, it does NOT affect docs. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15472) Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15472?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15472: ------------------------------------ Sure, it's here: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF... (See also this JIRA's description for more info.) > Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored) > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15472 > URL: https://issues.jboss.org/browse/JBIDE-15472 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > > First iteration: https://issues.jboss.org/browse/JBIDE-15470, as generated by this: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF... > [~maxandersen] said: > {quote} i would put the details in attachment i think. its a bit overloaded otherwise I think, > btw. is this something you will run when you find a failed buid or did you say you would detect when hit a certain amont of fail you generate it ? > if auto generated shuold take care to not keep opening new jiras again andagain ;) > maybe add a "watermark" to detect stil open test failure jiras > {quote} > Idea here is to run this tool as needed when I notice that builds which are supposed to be frozen and stable are showing test failures persisting for multiple builds. Could also run against master jobs, but less critical. > Not sure what you mean by a watermark, or how that would be implemented. Please elaborate. > As this is purely a workflow optimization, it does NOT affect docs. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2729) Add mobile web quickstarts for JBoss Central

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JBDS-2729?page=com.atlassian.jira.plugin.... ] Pete Muir commented on JBDS-2729: --------------------------------- * Going forward, most quickstarts will target product. There may be a few that target upstream projects, to show off new features (e.g. Java EE 7). This will substantially reduce testing and maintenance work, as each quickstart targets one thing only. * I don't think there should be any difference between the quickstarts displayed between JBoss Tools and JBDS. This would be contrary to the general direction we are taking here. * We shouldn't add all quickstarts, that would be too complex. We should add those that are particularly important. * Archetypes are also moving to target product. > Add mobile web quickstarts for JBoss Central > -------------------------------------------- > > Key: JBDS-2729 > URL: https://issues.jboss.org/browse/JBDS-2729 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, central, requirements > Reporter: Burr Sutter > Assignee: Burr Sutter > > The mobile web quickstarts being proced on WFK2 side should be included in JBoss Central -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15457) CordovaSim and Hybrid tools interaction/source code sharing

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15457?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-15457: ------------------------------------- I was wondering why you brought BrowserSim into the discussion :-) For CordovaSim, it does not need to live outside of Eclipse - perhaps it could become a general purpose (non-eclipse user) tool in the future but for now, I see it as highly complimentary to the Hybrid project plugin but not all that useful standalone. With that said, I can expect that Eclipse users may wish to install each one separately, if there are no hard-dependencies between the two technologies. > CordovaSim and Hybrid tools interaction/source code sharing > ----------------------------------------------------------- > > Key: JBIDE-15457 > URL: https://issues.jboss.org/browse/JBIDE-15457 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid, browsersim > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > Currently CordovaSim application consists of two parts: a Jetty-based server, and a BrowserSim-based client. The server part generates some content on the fly. For instance, the server may response with generated {{cordova_plugins.js}} content when it is requested by the client. Both parts of CordovaSim are executed in their own JVM, which means they do not have access to the Eclipse API. > Hybrid tools do very similar things, but in static way. For instance, while creating Android executables, they create {{cordova_plugins.js}} file on disk. Hybrid tools is a set of Eclipse plugins, so they have access to the Eclipse API. > Obviously CordovaSim and Hybrid tools have some code in their sources that could be shared. For the example above, both of them need a method to generate content of {{cordova_plugins.js}}. There are several approaches to implement it: > 1. Create two different implementations for CordovaSim and Hybrid tools and synchronize them when needed (currently we do this). This approach creates code duplication problems. > 2. Create an Eclipse API-independent plugin, so both CordovaSim and Hybrid tools could set it as a dependency. This approach imposes some restriction on the independent plugin (useful Eclipse API and libs cannot be used). > 3. Move the server part of CordovaSim to the Eclipse JVM, so it could use Eclipse API and any Hybrid tools API. With this approach we loose the ability to create standalone CordovaSim in the future. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12192) BrowserSim: simulate touch events

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12192?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-12192: ------------------------------------- [~burrsutter], I've created the issue JBDS-2764 > BrowserSim: simulate touch events > --------------------------------- > > Key: JBIDE-12192 > URL: https://issues.jboss.org/browse/JBIDE-12192 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.2.x > > > Now BrowserSim sends mouse events instead of touch events. It would be more appropriate to send touchstart/touchend/touchmove events. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2764) BrowserSim: simulate touch events

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBDS-2764: --------------------------------- Summary: BrowserSim: simulate touch events Key: JBDS-2764 URL: https://issues.jboss.org/browse/JBDS-2764 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: browsersim Reporter: Ilya Buziuk Assignee: Ilya Buziuk Now BrowserSim sends mouse events instead of touch events. It would be more appropriate to send touchstart/touchend/touchmove events. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2764) BrowserSim: simulate touch events

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2764?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2764: ----------------------------- CDW pm_ack: ? CDW release: ? Target Release: 3.0.2.GA > BrowserSim: simulate touch events > --------------------------------- > > Key: JBDS-2764 > URL: https://issues.jboss.org/browse/JBDS-2764 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > > Now BrowserSim sends mouse events instead of touch events. It would be more appropriate to send touchstart/touchend/touchmove events. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2733: ------------------------------------------- Yes, I suggest we keep the default install option simple (get both in one go, allow to avoid install part of it). > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15457) CordovaSim and Hybrid tools interaction/source code sharing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15457?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15457: --------------------------------------------- and yes, I accidentally wrote browsersim in my previous comment ;/ the issue here is about cordovasim running externally. > CordovaSim and Hybrid tools interaction/source code sharing > ----------------------------------------------------------- > > Key: JBIDE-15457 > URL: https://issues.jboss.org/browse/JBIDE-15457 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid, browsersim > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > Currently CordovaSim application consists of two parts: a Jetty-based server, and a BrowserSim-based client. The server part generates some content on the fly. For instance, the server may response with generated {{cordova_plugins.js}} content when it is requested by the client. Both parts of CordovaSim are executed in their own JVM, which means they do not have access to the Eclipse API. > Hybrid tools do very similar things, but in static way. For instance, while creating Android executables, they create {{cordova_plugins.js}} file on disk. Hybrid tools is a set of Eclipse plugins, so they have access to the Eclipse API. > Obviously CordovaSim and Hybrid tools have some code in their sources that could be shared. For the example above, both of them need a method to generate content of {{cordova_plugins.js}}. There are several approaches to implement it: > 1. Create two different implementations for CordovaSim and Hybrid tools and synchronize them when needed (currently we do this). This approach creates code duplication problems. > 2. Create an Eclipse API-independent plugin, so both CordovaSim and Hybrid tools could set it as a dependency. This approach imposes some restriction on the independent plugin (useful Eclipse API and libs cannot be used). > 3. Move the server part of CordovaSim to the Eclipse JVM, so it could use Eclipse API and any Hybrid tools API. With this approach we loose the ability to create standalone CordovaSim in the future. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2734: ----------------------------------- No, currently there's *no* way to trigger maven project update other than calling m2e's project management classes. > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > > Is Forge 2 ready to be included in JBDS ? -- 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, 8 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 September 2013