April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18556) battery status is not reflected in browsersim's status bar

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18556?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18556: -------------------------------- Sprint: Sprint #2 April 2015 > battery status is not reflected in browsersim's status bar > ---------------------------------------------------------- > > Key: JBIDE-18556 > URL: https://issues.jboss.org/browse/JBIDE-18556 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.3.x > > Attachments: log.png > > > create basic cordova app. > run in cordova sim. > changing the battery level and is-plugged does not take effect in the simulator. > Should it not be able to detect these ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18583) pong index.html no longer works on cordovasim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18583?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18583: -------------------------------- Sprint: Sprint #2 April 2015 > pong index.html no longer works on cordovasim > ---------------------------------------------- > > Key: JBIDE-18583 > URL: https://issues.jboss.org/browse/JBIDE-18583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.CR2 > Environment: Mac Os > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.3.x > > Attachments: index.html.zip > > > This works in previous versions. > replace the index.html into a hybrid app - it works when using ios simulator but not with cordovasim. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible in Quick Access by default when installed individually

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-12108: -------------------------------- Labels: new_and_noteworthy (was: ) > BrowserSim is not visible in Quick Access by default when installed individually > -------------------------------------------------------------------------------- > > Key: JBIDE-12108 > URL: https://issues.jboss.org/browse/JBIDE-12108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 3.3.0.CR1 > Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04 > Reporter: Jiri Peterka > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp > > > Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible. > *These additional steps are:* > # Right click on the Eclipse toolbar→Customize Perspective...: > !customize-perspective.png! > # Go to the Command Group Availability tab and select BrowserSim command group: > !enable-browsersim.png! > # BrowserSim icon will appear on the toolbar: > !browsersim-enabled.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible in Quick Access by default when installed individually

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-12108: ------------------------------------- Pushed to master Steps to verify: - After BrowserSim installation "Run BrowserSim" command should be available in Quick Access regardless of perspective and Command Groups availability > BrowserSim is not visible in Quick Access by default when installed individually > -------------------------------------------------------------------------------- > > Key: JBIDE-12108 > URL: https://issues.jboss.org/browse/JBIDE-12108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 3.3.0.CR1 > Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04 > Reporter: Jiri Peterka > Assignee: Ilya Buziuk > Fix For: 4.3.0.Beta1 > > Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp > > > Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible. > *These additional steps are:* > # Right click on the Eclipse toolbar→Customize Perspective...: > !customize-perspective.png! > # Go to the Command Group Availability tab and select BrowserSim command group: > !enable-browsersim.png! > # BrowserSim icon will appear on the toolbar: > !browsersim-enabled.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19551) Ionic Palette: Empty list item

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19551?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19551: ----------------------------------- Attachment: fixed.png Fixed for GTK3: !fixed.png! > Ionic Palette: Empty list item > ------------------------------ > > Key: JBIDE-19551 > URL: https://issues.jboss.org/browse/JBIDE-19551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Environment: Linux Ubuntu. GTK 3. > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: fixed.png, list.png > > > In New List wizard, if there is more than one item then all items but the first are empty: > !list.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3411 at 4/24/15 8:36 PM: -------------------------------------------------------------- I found better and simpler solution. Instead of renaming $\{target-dir\}/studio and have a bunch of changes in installer, I just changed where product is materialized under Mac OS X. In attached PR p2.director target dir is changed from $\{target-dir\}/studio to $\{target-dir\}/studio/jbdevstudio.app. That solution has all the benefits: 1. jbdevstudio.app location doesn't change; 2. jbdevstudio.app has the same structure as Eclipse.app and it is normal Mac OS X application package that contains all Eclipse artifacts (plug-ins, features and etc) inside; 3. jbdevstudio.ini is in right location and is not ignored anymore (BDS-3410 is fixed). The only drawback(?) tycho 0.23.0-SNAPSHOT should be used in jbdevstudio-product build. There are several unnecessary .png and .ico files but that is a different issue. was (Author: dgolovin): I found better and simpler solution. Instead of renaming ${target-dir}/studio and have a bunch of changes in installer, I just changed where product is materialized under Mac OS X. In attached PR p2.director target dir is changed from ${target-dir}/studio to ${target-dir}/studio/jbdevstudio.app. That solution has all the benefits: 1. jbdevstudio.app location doesn't change; 2. jbdevstudio.app has the same structure as Eclipse.app and it is normal Mac OS X application package that contains all Eclipse artifacts (plug-ins, features and etc) inside; 3. jbdevstudio.ini is in right location and is not ignored anymore (BDS-3410 is fixed). The only drawback(?) tycho 0.23.0-SNAPSHOT should be used in jbdevstudio-product build. There are several unnecessary .png and .ico files but that is a different issue. > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3411: ------------------------------------- I found better and simpler solution. Instead of renaming ${target-dir}/studio and have a bunch of changes in installer, I just changed where product is materialized under Mac OS X. In attached PR p2.director target dir is changed from ${target-dir}/studio to ${target-dir}/studio/jbdevstudio.app. That solution has all the benefits: 1. jbdevstudio.app location doesn't change; 2. jbdevstudio.app has the same structure as Eclipse.app and it is normal Mac OS X application package that contains all Eclipse artifacts (plug-ins, features and etc) inside; 3. jbdevstudio.ini is in right location and is not ignored anymore (BDS-3410 is fixed). The only drawback(?) tycho 0.23.0-SNAPSHOT should be used in jbdevstudio-product build. There are several unnecessary .png and .ico files but that is a different issue. > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18818) Test timeout in org.jboss.tools.jsf.verification.test

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18818: ----------------------------------- Fix Version/s: (was: 4.2.x) > Test timeout in org.jboss.tools.jsf.verification.test > ----------------------------------------------------- > > Key: JBIDE-18818 > URL: https://issues.jboss.org/browse/JBIDE-18818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.3.x > > > Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests. > [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... > But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... > Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work. > -- > If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19714) seam.core test failure

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19714: -------------------------------------- Summary: seam.core test failure Key: JBIDE-19714 URL: https://issues.jboss.org/browse/JBIDE-19714 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Affects Versions: 4.3.0.Alpha2 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 4.3.0.Beta1 Failed tests: SeamComponentRefactoringTest.testSeamComponentRename:90->renameComponent:142 There is unexpected number of changes expected:<7> but was:<3> SeamContextVariableRefactoringTest.testSeamContextVariable_Component_Rename:76->AbstractRefactorTest.checkRename:33 expected:<2> but was:<1> SeamEARTest.testEarProject:80 War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3411: -------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/303 > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 April 2015