August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22779) Create integration tests PR check job for cdi

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22779?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22779. ------------------------------------ > Create integration tests PR check job for cdi > --------------------------------------------- > > Key: JBIDE-22779 > URL: https://issues.jboss.org/browse/JBIDE-22779 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22780) Create integration tests PR check job for cdi-extensions

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22780?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22780. ------------------------------------ > Create integration tests PR check job for cdi-extensions > -------------------------------------------------------- > > Key: JBIDE-22780 > URL: https://issues.jboss.org/browse/JBIDE-22780 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Jan Richter resolved JBDS-3850. ------------------------------- Resolution: Done Coverage report is now tied to unit tests. Resolving. > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.1.0.AM3 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3850: ------------------------------ Fix Version/s: 10.1.0.AM3 (was: 11.0.0.AM1) > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.1.0.AM3 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3969) Run istanbul coverage with gulp for unit-tests

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3969?page=com.atlassian.jira.plugin.... ] Jan Richter edited comment on JBDS-3969 at 8/10/16 8:06 AM: ------------------------------------------------------------ This issue was solved with the new version of gulp-spawn-mocha in this commit: https://github.com/redhat-developer-tooling/developer-platform-install/co... Coverage is now an integral part of the unit tests, so all you need to get it is run {noformat}gulp test{noformat} was (Author: jrichter1): This issue was solved with the new version of gulp-spawn-mocha in this commit: https://github.com/redhat-developer-tooling/developer-platform-install/co... > Run istanbul coverage with gulp for unit-tests > ---------------------------------------------- > > Key: JBDS-3969 > URL: https://issues.jboss.org/browse/JBDS-3969 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Current coverage implementation us running with: > {code}gulp create-electron-symlink > gulp test > npm run cover{code} > Last command generates summary on console and report in ./coverage folder. > Would be good to have it always running during just. > {code}gulp test{code} > I had several attempts to get this done with various modules, but result is always %100 coverage with 0 covered files. > {code}----------|----------|----------|----------|----------|----------------| > File | % Stmts | % Branch | % Funcs | % Lines |Uncovered Lines | > ----------|----------|----------|----------|----------|----------------| > ----------|----------|----------|----------|----------|----------------| > All files | 100 | 100 | 100 | 100 | | > ----------|----------|----------|----------|----------|----------------| > =============================== Coverage summary =============================== > Statements : 100% ( 0/0 ) > Branches : 100% ( 0/0 ) > Functions : 100% ( 0/0 ) > Lines : 100% ( 0/0 ) > ================================================================================{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3969) Run istanbul coverage with gulp for unit-tests

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3969?page=com.atlassian.jira.plugin.... ] Jan Richter resolved JBDS-3969. ------------------------------- Resolution: Done This issue was solved with the new version of gulp-spawn-mocha in this commit: https://github.com/redhat-developer-tooling/developer-platform-install/co... > Run istanbul coverage with gulp for unit-tests > ---------------------------------------------- > > Key: JBDS-3969 > URL: https://issues.jboss.org/browse/JBDS-3969 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Current coverage implementation us running with: > {code}gulp create-electron-symlink > gulp test > npm run cover{code} > Last command generates summary on console and report in ./coverage folder. > Would be good to have it always running during just. > {code}gulp test{code} > I had several attempts to get this done with various modules, but result is always %100 coverage with 0 covered files. > {code}----------|----------|----------|----------|----------|----------------| > File | % Stmts | % Branch | % Funcs | % Lines |Uncovered Lines | > ----------|----------|----------|----------|----------|----------------| > ----------|----------|----------|----------|----------|----------------| > All files | 100 | 100 | 100 | 100 | | > ----------|----------|----------|----------|----------|----------------| > =============================== Coverage summary =============================== > Statements : 100% ( 0/0 ) > Branches : 100% ( 0/0 ) > Functions : 100% ( 0/0 ) > Lines : 100% ( 0/0 ) > ================================================================================{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22971) Unable to install JRebel

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-22971: ---------------------------------- Summary: Unable to install JRebel Key: JBIDE-22971 URL: https://issues.jboss.org/browse/JBIDE-22971 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 4.4.1.AM3 Reporter: Radim Hopp {noformat}An error occurred while collecting items to be installed session context was:(profile=devstudio, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/plugins/org.zeroturnar.... connect timed out Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/plugins/org.zeroturnar.... connect timed out Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/features/org.zeroturna.... connect timed out Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/plugins/org.zeroturnar.... connect timed out Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/features/org.zeroturna.... connect timed out{noformat} This seems like problem on zeroturnaround.com side (even www.zeroturnaround.com is very slow to load today). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22970) Modifying archive Library fileset doesnt work

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-22970: ---------------------------------------- Summary: Modifying archive Library fileset doesnt work Key: JBIDE-22970 URL: https://issues.jboss.org/browse/JBIDE-22970 Project: Tools (JBoss Tools) Issue Type: Bug Components: archives Affects Versions: 4.4.1.AM3 Reporter: Rastislav Wagner Fix For: 4.4.1.AM3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22875) Deploying/Editing archive opens empty shell

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22875?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22875. ------------------------------------ Verified in devstudio 10.1.0.AM3-v20160810-0441-B5735 > Deploying/Editing archive opens empty shell > ------------------------------------------- > > Key: JBIDE-22875 > URL: https://issues.jboss.org/browse/JBIDE-22875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.4.1.AM1 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > Attachments: pr3.zip > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22913: ------------------------------------ then we have a problem for AM3 because the dependency still being SNAPSHOT we may need changes from it and if the plugin is not rebuilt, then it's a failure > Server Adapter: Publish does not work > ------------------------------------- > > Key: JBIDE-22913 > URL: https://issues.jboss.org/browse/JBIDE-22913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.1.AM3 > > > When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error. > {code} > Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it. > Ignoring the following flags because they only apply to rsync: --exclude, --no-perms > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2 > {code} > I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 August 2016