[
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)