[JBoss JIRA] (JBIDE-20711) Changing deploy-name in component xml file will not take effect
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-20711.
---------------------------------
Resolution: Done
Actually I'm resolving the issue myself. Unless you see something we can actually fix or behaves as you wouldn't expect.
> Changing deploy-name in component xml file will not take effect
> ---------------------------------------------------------------
>
> Key: JBIDE-20711
> URL: https://issues.jboss.org/browse/JBIDE-20711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> Steps to replicate:
> 1) Create a dynamic web project TestProject
> 2) Create a server
> 3) Add/Remove action in servers view. You will see the module name is TestProject
> 4) Open the component.xml file in .settings folder and change deploy-name to some new value (RobsTest)
> 5) Add/Remove, note module name didn't change
> 6) Publish deployment, note its still deploying as TestProject
> 7) Close project, then re-open it
> 8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar)
> 9) Publish, note module is deployed as RobsTest.war
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-20711) Changing deploy-name in component xml file will not take effect
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20711:
-------------------------------------
> Then I changed the deploy-name in TestProject/.settings/org.eclipse.wst.common.component (in vi in terminal),
This usecase is never expected to work without a refresh. If you change the file outside of the workspace, we cannot expect eclipse to notice that.
My point was if you change the contents **inside** eclipse, it works without a refresh.
With this in mind, I still suggest this is working exactly as expected.
[~mmalina] Please close the issue if you can verify that modifying the xml file inside eclipse is sufficient without a refresh. We cannot handle the situation of users editing files outside eclipse.
> Changing deploy-name in component xml file will not take effect
> ---------------------------------------------------------------
>
> Key: JBIDE-20711
> URL: https://issues.jboss.org/browse/JBIDE-20711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> Steps to replicate:
> 1) Create a dynamic web project TestProject
> 2) Create a server
> 3) Add/Remove action in servers view. You will see the module name is TestProject
> 4) Open the component.xml file in .settings folder and change deploy-name to some new value (RobsTest)
> 5) Add/Remove, note module name didn't change
> 6) Publish deployment, note its still deploying as TestProject
> 7) Close project, then re-open it
> 8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar)
> 9) Publish, note module is deployed as RobsTest.war
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23817:
------------------------------------
I tried with oc from within the OCP 3.4 VM (aka CDK 2.4RC0) and it seems that the oc client issues a get request on the scale object then a put to update this object where the only issue of PUT through the OSJC. Will check with OCP 3.3 (aka CDK 2.3)
> Scaling: is not working with OpenShift 3.4 (CDK 2.4)
> ----------------------------------------------------
>
> Key: JBIDE-23817
> URL: https://issues.jboss.org/browse/JBIDE-23817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: CDK 2.4
> Devstudio 10.3.0.AM2
> Reporter: Radim Hopp
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.3.Final
>
> Attachments: Spectacle.yJ3971.png
>
>
> Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now).
> When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again.
> This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23822) Server adapter: is not working with oc v1.4.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23822?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23822 at 2/7/17 11:22 AM:
-------------------------------------------------------------------
I can reproduce this with oc version v1.4.x+
I tested the github and enterprise versions and they all fail against the minishift cdk which is running:
{code}
openshift v3.4.0.39
kubernetes v1.4.0+776c994
{code}
* the ones that dont work:
** oc v3.4.1.2
** oc v3.4.0.40
** oc v1.4.0-alpha.1+f189ede
** oc v1.4.0+208f053
** oc v1.4.1+3f9807a
** oc v1.5.0-alpha.2+e4b43ee
* the ones that work:
** oc v3.3.1.7
** oc v1.3.3
the error output given by oc is that the auth info for <user> doesnt exist (the user that I am using on my minishift is `system`):
{code}
error: auth info "system" does not exist
{code}
The exact cmd line that I am running is
{code}
oc rsync --user=system --token=<TOKEN> --server=https://192.168.99.100:8443 --insecure-skip-tls-verify=true --exclude='.git' nodejs-mongodb-example-1-i31y4:/opt/app-root/src/ -n gigu /Users/adietish/Documents/jboss-workspaces/jbosstools-github/runtime-openshift2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/gigu@mongodb/deploy/
{code}
was (Author: adietish):
I can reproduce this with oc version v1.4.x+
I tested the github and enterprise versions and they all fail against the minishift cdk which is running:
{code}
openshift v3.4.0.39
kubernetes v1.4.0+776c994
{code}
* the ones that dont work:
** oc v3.4.1.2
** oc v3.4.0.40
** oc v1.4.0-alpha.1+f189ede
** oc v1.4.0+208f053
** oc v1.4.1+3f9807a
** oc v1.5.0-alpha.2+e4b43ee
* the ones that work:
** oc v3.3.1.7
** oc v1.3.3
the error output given by oc is that the auth info for <user> doesnt exist (the user that I am using on my minishift is `system`):
{code}
error: auth info "system" does not exist
{code}
> Server adapter: is not working with oc v1.4.x
> ---------------------------------------------
>
> Key: JBIDE-23822
> URL: https://issues.jboss.org/browse/JBIDE-23822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: Devstudio 10.3.0.AM2.
> CDK 2.4 (OpenShift 3.4)
> oc v1.4.1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> {noformat}
> !ENTRY org.jboss.tools.openshift.core 2 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !STACK 1
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:83)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Contains: OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !SUBENTRY 2 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !ENTRY org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE Could not sync /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23822) Server adapter: is not working with oc v1.4.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23822?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23822:
------------------------------------------
I can reproduce this with oc version v1.4.x+
I tested the github and enterprise versions and they all fail against the minishift cdk which is running:
{code}
openshift v3.4.0.39
kubernetes v1.4.0+776c994
{code}
* the ones that dont work:
** oc v3.4.1.2
** oc v3.4.0.40
** oc v1.4.0-alpha.1+f189ede
** oc v1.4.0+208f053
** oc v1.4.1+3f9807a
** oc v1.5.0-alpha.2+e4b43ee
* the ones that work:
** oc v3.3.1.7
** oc v1.3.3
the error output given by oc is that the auth info for <user> doesnt exist (the user that I am using on my minishift is `system`):
{code}
error: auth info "system" does not exist
{code}
> Server adapter: is not working with oc v1.4.x
> ---------------------------------------------
>
> Key: JBIDE-23822
> URL: https://issues.jboss.org/browse/JBIDE-23822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: Devstudio 10.3.0.AM2.
> CDK 2.4 (OpenShift 3.4)
> oc v1.4.1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> {noformat}
> !ENTRY org.jboss.tools.openshift.core 2 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !STACK 1
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:83)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Contains: OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !SUBENTRY 2 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !ENTRY org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE Could not sync /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23822) Server adapter: is not working with oc v1.4.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23822?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23822:
-------------------------------------
Summary: Server adapter: is not working with oc v1.4.x (was: Server adapter: is not working with oc v1.4.1)
> Server adapter: is not working with oc v1.4.x
> ---------------------------------------------
>
> Key: JBIDE-23822
> URL: https://issues.jboss.org/browse/JBIDE-23822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: Devstudio 10.3.0.AM2.
> CDK 2.4 (OpenShift 3.4)
> oc v1.4.1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> {noformat}
> !ENTRY org.jboss.tools.openshift.core 2 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !STACK 1
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:83)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Contains: OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !SUBENTRY 2 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !ENTRY org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE Could not sync /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23768) Publish tagged version of jboss tools parent pom to public repository
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23768:
------------------------------------
Not saying it's the wrong thing. Just trying to minimize the overhead we incur every time we change the TP version. But we can try it this time (next week is code freeze for JBT 4.4.3.Final) and see what happens.
> Publish tagged version of jboss tools parent pom to public repository
> ---------------------------------------------------------------------
>
> Key: JBIDE-23768
> URL: https://issues.jboss.org/browse/JBIDE-23768
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.4.2.Final, 4.4.3.AM1
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 4.4.3.Final
>
>
> it will allow Fuse Tooling (and other dependent projects) to have tagged version of their parent pom for tagged release.
> i'm talking about org.jboss.tools:parent
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23862:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have "oc" available at a path that contains a " " (ex. /Users/adietish/Download/oc binaries/oc)
# ASSERT: have an OpenShift server adapter
# EXEC: start the adapter
Result:
Publishing fails, reporting that the "oc" binary could not be found
was:
# ASSERT: make sure that you have "oc" available at a path that contains a " " (ex. /Users/adietish/Download/oc binaries/oc)
# ASSERT: have an OpenShift server adapter
# EXEC: start the adapter
Result:
Publishing fails, reporting that the "oc" binary could not be found
> Server adapter: if "oc" in preferences is set to path with a " " syncing fails
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23862
> URL: https://issues.jboss.org/browse/JBIDE-23862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.4.3.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month