[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:
------------------------------------
OK but I'm sure we will forget one day or another
> 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
[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22913 at 8/10/16 10:11 AM:
--------------------------------------------------------------
This is exactly why we added a check for SNAPSHOT versions in builds -- to avoid confusion around WHICH version of snapshot is used in a build. See https://issues.jboss.org/browse/JBIDE-22446.
Maybe if the openshift-restclient-java-5.0.0-*.jar could be released more often, it could be referenced by fully-qualified version instead of just 5.0.0-SNAPSHOT.
Workarounds:
a) commit any change to the jbosstools-server project to force a new SHA to be the latest in github, which will make the build see that it needs to publish anew. This could be something simple like a comment, eg., <!-- openshift-restclient-java-5.0.0-20160802.212546-5.jar -->
eg., https://github.com/jbosstools/jbosstools-openshift/pull/1280/files
b) kick the build yourself [1],[2], with the skipRevisionCheckWhenPublishing flag checked (=true).
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
was (Author: nickboldt):
This is exactly why we added a check for SNAPSHOT versions in builds -- to avoid confusion around WHICH version of snapshot is used in a build. See https://issues.jboss.org/browse/JBIDE-22446.
Maybe if the openshift-restclient-java-5.0.0-*.jar could be released more often, it could be referenced by fully-qualified version instead of just 5.0.0-SNAPSHOT.
Workarounds:
a) commit any change to the jbosstools-server project to force a new SHA to be the latest in github, which will make the build see that it needs to publish anew. This could be something simple like a comment, eg., <!-- openshift-restclient-java-5.0.0-20160802.212546-5.jar -->
eg., https://github.com/jbosstools/jbosstools-openshift/pull/1280/files
b) kick the build yourself [1], with the skipRevisionCheckWhenPublishing flag checked (=true).
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> 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
[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22913 at 8/10/16 10:09 AM:
--------------------------------------------------------------
This is exactly why we added a check for SNAPSHOT versions in builds -- to avoid confusion around WHICH version of snapshot is used in a build. See https://issues.jboss.org/browse/JBIDE-22446.
Maybe if the openshift-restclient-java-5.0.0-*.jar could be released more often, it could be referenced by fully-qualified version instead of just 5.0.0-SNAPSHOT.
Workarounds:
a) commit any change to the jbosstools-server project to force a new SHA to be the latest in github, which will make the build see that it needs to publish anew. This could be something simple like a comment, eg., <!-- openshift-restclient-java-5.0.0-20160802.212546-5.jar -->
eg., https://github.com/jbosstools/jbosstools-openshift/pull/1280/files
b) kick the build yourself [1], with the skipRevisionCheckWhenPublishing flag checked (=true).
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
was (Author: nickboldt):
This is exactly why we added a check for SNAPSHOT versions in builds -- to avoid confusion around WHICH version of snapshot is used in a build. See https://issues.jboss.org/browse/JBIDE-22446.
Maybe if the openshift-restclient-java-5.0.0-*.jar could be released more often, it could be referenced by fully-qualified version instead of just 5.0.0-SNAPSHOT.
Workarounds:
a) commit any change to the jbosstools-server project to force a new SHA to be the latest in github, which will make the build see that it needs to publish anew. This could be something simple like a comment, eg., <!-- openshift-restclient-java-5.0.0-20160802.212546-5.jar -->
b) kick the build yourself [1], with the skipRevisionCheckWhenPublishing flag checked (=true).
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> 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
[JBoss JIRA] (JBIDE-22425) Unable to run offline script on windows
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22425?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22425:
------------------------------------
http://stackoverflow.com/questions/26763103/groovy-using-ampersand-in-com...
> Unable to run offline script on windows
> ---------------------------------------
>
> Key: JBIDE-22425
> URL: https://issues.jboss.org/browse/JBIDE-22425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.4.0.Alpha2
> Environment: JBDS 10.0.0.Alpha2
> Windows 10
> {noformat}
> C:\>java -version
> openjdk version "1.8.0_91-2-redhat"
> OpenJDK Runtime Environment (build 1.8.0_91-2-redhat-b14)
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> C:\>groovy -version
> Groovy Version: 2.4.6 JVM: 1.8.0_91-2-redhat Vendor: Oracle Corporation OS: Windows 10
> C:\>mvn -version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\Users\jboss-qa\programs\apache-maven-3.3.9\bin\..
> Java version: 1.8.0_91-2-redhat, vendor: Oracle Corporation
> Java home: C:\java-1.8.0-openjdk-1.8.0.91-2.b14.windows.x86_64\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> {noformat}
> Reporter: Radim Hopp
>
> Output of groovy script:
> {noformat}
> C:\Users\jboss-qa\temp\offline>groovy -Dgrape.config="C:\Users\jboss-qa\workspace\.metadata\.plugins\org.jboss.tools.project.examples\offline\jbossToolsGrapeConfig_3.1.0.Alpha1_v20160510_1913_B866.xml" "C:\Users\jboss-qa\workspace\.metadata\.plugins\org.jboss.tools.project.examples\offline\go_offline_3.1.0.Alpha1_v20160510_1913_B866.groovy" http://download.jboss.org/jbosstools/examples/4/4/project-examples-catego... http://download.jboss.org/jbosstools/examples/4/4/project-examples-devstu... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... http://download.jboss.org/jbosstools/examples/4/4/project-examples-shared... -u "http://dcp.jboss.org/v1/rest/search^?content_provider=jboss-developer&con..." -q -e
> 'content_provider' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> Invalid parameter(s)
> QUERY { PROCESS | SESSION | TERMSERVER | USER }
> 'size' is not recognized as an internal or external command,
> operable program or batch file.
> ^CTerminate batch job (Y/N)? Y{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22913:
------------------------------------
This is exactly why we added a check for SNAPSHOT versions in builds -- to avoid confusion around WHICH version of snapshot is used in a build. See https://issues.jboss.org/browse/JBIDE-22446.
Maybe if the openshift-restclient-java-5.0.0-*.jar could be released more often, it could be referenced by fully-qualified version instead of just 5.0.0-SNAPSHOT.
Workarounds:
a) commit any change to the jbosstools-server project to force a new SHA to be the latest in github, which will make the build see that it needs to publish anew. This could be something simple like a comment, eg., <!-- openshift-restclient-java-5.0.0-20160802.212546-5.jar -->
b) kick the build yourself [1], with the skipRevisionCheckWhenPublishing flag checked (=true).
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> 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
[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 closed JBDS-3969.
-----------------------------
> 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