[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25700 at 4/16/18 4:23 AM:
-------------------------------------------------------------------
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run (notice the --no-perms=true):
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
was (Author: adietish):
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run (notice the *--no-perms=true*):
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25700 at 4/16/18 4:23 AM:
-------------------------------------------------------------------
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run (notice the --no-perms=true):
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
was (Author: adietish):
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run:
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25700 at 4/16/18 4:23 AM:
-------------------------------------------------------------------
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run (notice the *--no-perms=true*):
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
was (Author: adietish):
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run (notice the --no-perms=true):
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25700 at 4/16/18 4:22 AM:
-------------------------------------------------------------------
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run:
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
was (Author: adietish):
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run:
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true camel-ose-springboot-xml-1-rgbfn:/deployments/BOOT-INF/classes/ <LOCAL FILESYSTEM>
{code}
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25700:
------------------------------------------
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run:
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true camel-ose-springboot-xml-1-rgbfn:/deployments/BOOT-INF/classes/ <LOCAL FILESYSTEM>
{code}
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3871:
--------------------------------
Fix Version/s: 12.0.0.GA
(was: 11.3.0.GA)
> installer credentials misleading/incomplete information.
> --------------------------------------------------------
>
> Key: JBDS-3871
> URL: https://issues.jboss.org/browse/JBDS-3871
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Win 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
> Fix For: 12.0.0.GA
>
> Attachments: screenshot-1.png
>
>
> There are several problems a with the information on the platform installer's login screen:
> # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process.
> # The register link points to the login page, not the register page.
> # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed."
> # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription.
> The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access."
> Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials".
> During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet.
> Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account.
> Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software.
> Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer..
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25919) OpenShift: java.io.FileNotFoundException: /icons/apps/apache.png
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-25919:
-------------------------------------
Summary: OpenShift: java.io.FileNotFoundException: /icons/apps/apache.png
Key: JBIDE-25919
URL: https://issues.jboss.org/browse/JBIDE-25919
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.3.Final
Environment: CDK 3.4.0-2 + DevStudio 11.3.0.GA
Reporter: Josef Kopriva
Assignee: Andre Dietisheim
{code:java}
eclipse.buildId=11.3.0.GA-v20180413-0714-B2352
java.version=1.8.0_162
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -data file:/home/jkopriva/devstudio_B2352/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.eclipse.jface
Error
Sun Apr 15 23:31:25 CEST 2018
/icons/apps/apache.png
java.io.FileNotFoundException: /icons/apps/apache.png
at org.eclipse.osgi.storage.url.bundleentry.Handler.findBundleEntry(Handler.java:49)
at org.eclipse.osgi.storage.url.BundleResourceHandler.openConnection(BundleResourceHandler.java:169)
at java.net.URL.openConnection(URL.java:979)
at org.eclipse.osgi.storage.url.BundleURLConverter.toFileURL(BundleURLConverter.java:32)
at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:207)
at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:230)
at org.eclipse.jface.resource.URLImageDescriptor.access$2(URLImageDescriptor.java:218)
at org.eclipse.jface.resource.URLImageDescriptor$URLImageFileNameProvider.getImagePath(URLImageDescriptor.java:54)
at org.eclipse.swt.internal.DPIUtil.validateAndGetImagePathAtZoom(DPIUtil.java:408)
at org.eclipse.swt.graphics.Image.<init>(Image.java:771)
at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:261)
at org.eclipse.jface.resource.ImageDescriptor.createImage(ImageDescriptor.java:240)
at org.jboss.tools.openshift.internal.ui.OpenShiftImages.getAppImage(OpenShiftImages.java:82)
at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceDetailViews$ApplicationSourceDetailView.updateImage(ApplicationSourceDetailViews.java:101)
at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceDetailViews$ApplicationSourceDetailView.onVisible(ApplicationSourceDetailViews.java:97)
at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:92)
at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:83)
at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.lambda$0(AbstractStackedDetailViews.java:79)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:61)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:103)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:76)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:61)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:103)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:76)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:82)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:126)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$3(SimplePropertyObservableValue.java:118)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:70)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:149)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:153)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:171)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:66)
at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:69)
at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:50)
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:328)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)
at org.jboss.tools.common.databinding.ObservablePojo.firePropertyChange(ObservablePojo.java:29)
at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.updateSelectedAppSource(NewApplicationWizardModel.java:105)
at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.update(NewApplicationWizardModel.java:88)
at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.setServerAppSource(NewApplicationWizardModel.java:190)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:59)
at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:54)
at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:89)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:110)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:66)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:115)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:115)
at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:469)
at org.eclipse.core.databinding.ValueBinding$3$1.run(ValueBinding.java:210)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:149)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:153)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:171)
at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:200)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:149)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:153)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:171)
at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:162)
at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:151)
at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:46)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:61)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:103)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:76)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:82)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:126)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$3(SimplePropertyObservableValue.java:118)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:70)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:149)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:153)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:171)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:66)
at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:69)
at org.eclipse.jface.internal.databinding.viewers.SelectionChangedListener.selectionChanged(SelectionChangedListener.java:36)
at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:155)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:152)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2180)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1223)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1252)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:240)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:235)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
at org.eclipse.jface.window.Window.open(Window.java:794)
at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-4691) dns
by Jehad Meshmesh (JIRA)
Jehad Meshmesh created JBDS-4691:
------------------------------------
Summary: dns
Key: JBDS-4691
URL: https://issues.jboss.org/browse/JBDS-4691
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: integration
Affects Versions: 11.3.0.AM3
Reporter: Jehad Meshmesh
Fix For: 11.3.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-4671) Errors updating from 11.1.0.GA to latest one
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4671?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4671 at 4/14/18 10:21 AM:
------------------------------------------------------------
0. Fedora 27 w/ JDK 8u151
{code}
$➔ java -version
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
[10:15:45] nboldt@fc27:~/devstudio
$➔ uname -a
Linux fc27.vm02 4.14.13-300.fc27.x86_64 #1 SMP Thu Jan 11 04:00:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
{code}
1. Install devstudio 11.2.0.GA release from installer jar via console.
{code}
echo 1 | java -jar devstudio-11.2.0.GA-v20180122-2025-B1884-installer-standalone.jar -console
{code}
2. start devstudio via the wayland launcher:
{code}
cd ~/devstudio/; ./devstudio-wayland{code}
3. Since it's not yet released, add the devstudio 11.3 staging site at http://devstudio.redhat.com/11/staging/updates/ via Help > Install > (paste into 'Work with:' field) > Add > wait until loaded > cancel.
4. Check for updates ...
!ds11.2-update-to-11.3.png|thumbnail!
So I'm pretty confident this will work for updating from 11.2 to 11.3 when we go GA in a couple weeks.
was (Author: nickboldt):
0. Fedora 27 w/ JDK 8u151
{code}
$➔ java -version
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
[10:15:45] nboldt@fc27:~/devstudio
$➔ uname -a
Linux fc27.vm02 4.14.13-300.fc27.x86_64 #1 SMP Thu Jan 11 04:00:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
{code}
1. Install devstudio 11.2.0.GA release from installer jar via console.
{code}
echo 1 | java -jar devstudio-11.2.0.GA-v20180122-2025-B1884-installer-standalone.jar -console
{code}
2. start devstudio via the wayland launcher:
{code}
cd ~/devstudio/; ./devstudio-wayland{code}
3. Since it's not yet released, add the devstudio 11.3 staging site at http://devstudio.redhat.com/11/staging/updates/ via Help > Install > (paste into field) > Add > wait until loaded > cancel.
4. Check for updates ...
!ds11.2-update-to-11.3.png|thumbnail!
So I'm pretty confident this will work for updating from 11.2 to 11.3 when we go GA in a couple weeks.
> Errors updating from 11.1.0.GA to latest one
> --------------------------------------------
>
> Key: JBDS-4671
> URL: https://issues.jboss.org/browse/JBDS-4671
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, updatesite
> Affects Versions: 11.1.0.GA
> Environment: Red Hat JBoss Developer Studio 11.1.0.GA with early access activate.
> openjdk version "1.8.0_151" .OpenJDK Runtime Environment (build 1.8.0_151-b12)
> Operating System: Fedora 27
> Reporter: Roman Martin Gil
> Assignee: Jeff MAURY
> Fix For: 11.3.0.GA
>
> Attachments: 01-rhjbds-available-updates.png, 02-rhjbds-about-installation.png, 03-rhjbds-updating-error.png, ds11.2-update-sites.png, ds11.2-update-to-11.3.png, ds11.2.0.ga.png, rhjbds11-software-sites.png
>
>
> Since some days I am getting alerts to update my RHJBDS 11.1.0.GA to latest versions however I could not complete anyway.
> Everyday I get a update alert with latest versions but it seems that they are not ready to be applied.
> After some moments updating the environment I got the following error and stack trace:
> {code:java}
> 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=).
> No repository found containing: osgi.bundle,com.jboss.devstudio.core,11.3.0.AM1-v20180125-1048-B1900
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.capabilities,11.3.0.v20180124-1725
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.central,11.3.0.AM1-v20180125-1048-B1900
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.project.examples,11.3.0.v20180124-1725
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.usage.branding,11.3.0.v20180124-1725
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.capabilities.feature,11.3.0.v20180124-1725
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.feature,11.3.0.v20180125-1048
> No repository found containing: binary,com.jboss.devstudio.core.package.executable.gtk.linux.x86_64,11.3.0.AM1-v20180125-1048-B1900
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpm.feature,11.3.0.v20180125-1048
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpmdeps.feature,11.3.0.v20180124-1725
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.fuse.feature,11.3.0.v20180124-1725
> {code}
> I attached some screenshots with the process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months