April 2018 - jbosstools-issues - Jboss List Archives

[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 updated JBIDE-25700: ------------------------------------- Attachment: server-adapter-rebublish-state.png > 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 > Priority: Critical > Labels: server_adapter, springboot > Fix For: 4.5.3.AM3 > > 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

1
0
0 / 0

[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 updated JBIDE-25700: ------------------------------------- Attachment: permission-error-rsync-fc26.png > 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 > Priority: Critical > Labels: server_adapter, springboot > Fix For: 4.5.3.AM3 > > Attachments: permission-error-rsync-fc26.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

1
0
0 / 0

[JBoss JIRA] (ERT-620) Update rh-eclipse47 collection to Oxygen.3 bits

by Václav Kadlčík (JIRA)

[ https://issues.jboss.org/browse/ERT-620?page=com.atlassian.jira.plugin.sy... ] Václav Kadlčík resolved ERT-620. -------------------------------- Resolution: Done solved in DevTools 2018.2 > Update rh-eclipse47 collection to Oxygen.3 bits > ----------------------------------------------- > > Key: ERT-620 > URL: https://issues.jboss.org/browse/ERT-620 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Mat Booth > Assignee: Mat Booth > > See the erratum for details: https://errata.devel.redhat.com/advisory/33102 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4690) Import Spring Starter Project shows error

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4690?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4690. ------------------------------ Resolution: Done As of 11.3.0.GA Central will include Spring IDE 3.9.3. > Import Spring Starter Project shows error > ----------------------------------------- > > Key: JBDS-4690 > URL: https://issues.jboss.org/browse/JBDS-4690 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: 3rd-party-certification > Affects Versions: 11.3.0.AM3 > Environment: F28 > + > Red Hat JBoss Developer Studio > Version: 11.3.0.AM3 > Build id: AM3-v20180322-1027-B2194 > Build date: 20180322-1027 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 11.3.0.GA > > > {code:java} > null > org.springframework.ide.eclipse.beans.core > Error > Fri Mar 23 15:35:53 CET 2018 > Problems occurred when invoking code from plug-in: "org.springframework.ide.eclipse.beans.core". > java.lang.NoSuchMethodError: org.springframework.util.Assert.state(ZLjava/util/function/Supplier;)V > at org.springframework.boot.autoconfigure.cache.CacheConfigurations.getConfigurationClass(CacheConfigurations.java:55) > at org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration$CacheConfigurationImportSelector.selectImports(CacheAutoConfiguration.java:169) > at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:517) > at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:286) > at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:237) > at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:536) > at org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:481) > at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:191) > at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:321) > at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25856) Can't update from JBT 4.5.2.Final to 4.5.3.AM3 using Check for Updates

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25856?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25856. -------------------------------- Resolution: Won't Fix Workaround exists. Won't fix. May actually fix itself when updating from 4.5.2 to 4.5.3.Final, however. IIRC we don't guarantee that users can update from Final to a milestone, only from Final -> Final. > Can't update from JBT 4.5.2.Final to 4.5.3.AM3 using Check for Updates > ---------------------------------------------------------------------- > > Key: JBIDE-25856 > URL: https://issues.jboss.org/browse/JBIDE-25856 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > Attachments: CheckForUpdates.png, InstallNewSoftware_Keep.png, InstallNewSoftware_ShowOriginalErrors.png, InstallNewSoftware_Update.png > > > I tested an update form Oxygen2+JBT 4.5.2.Final to JBT 4.5.3.AM3. When I went through Check For Updates I got this error: > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201) > Software currently installed: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426) > Only one of the following can be installed at once: > JBoss WebServices Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.ui 2.0.0.v20180105-1426) > JBoss WebServices Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.ui 2.0.1.v20180311-2201) > Cannot satisfy dependency: > From: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201) > To: org.jboss.tools.ws.ui [2.0.1.v20180311-2201] > Cannot satisfy dependency: > From: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426) > To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426] > {code} > If my understanding is correct, the eclipse plans to update JAX-RS but doesn't plan to update JAX-WS. > I know that we fixed similar issue recently in JBIDE-25665. > The "Check for Updates" doesn't offer any remediation action but Install new Software offers nice solution. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Sprint: (was: devex #147 April 2018) > [release] externalize common properties to parameterize jobs > ------------------------------------------------------------ > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.x > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.3.Final) > [release] externalize common properties to parameterize jobs > ------------------------------------------------------------ > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.x > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Sprint: (was: devex #147 April 2018) > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM1, 4.6.0.Final > > > In order to start Photon based builds, we need a working Photon based target platform > For sprint 148 / AM1: Photon.0.M6 > For sprint 149 / AM2: Photon.0.M7 > For sprint 150 / AM3: Photon.0.RC3 > For sprint 151 / GA: Photon.0.GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25585) release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25585?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25585: ------------------------------- Sprint: devex #145 February 2018 (was: devex #145 February 2018, devex #147 April 2018) > release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25585 > URL: https://issues.jboss.org/browse/JBIDE-25585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM1, 4.6.0.Final > > > Need a semi-working placeholder (even if it's a CI build) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ > Once we release 4.6.0.Final, we can then update the symlink to point here: > http://download.jboss.org/jbosstools/photon/stable/updates/ > Upstream issue: > https://bugs.eclipse.org/529801 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4615) [rpm] org.springframework.ide.eclipse.boot.wizard causes a constraint violation when starting up Eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4615?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4615. ---------------------------- Fix Version/s: 11.3.0.GA (was: 11.x) Resolution: Won't Fix Won't get fixed in 11.3. > [rpm] org.springframework.ide.eclipse.boot.wizard causes a constraint violation when starting up Eclipse > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-4615 > URL: https://issues.jboss.org/browse/JBDS-4615 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central, central-update, rpm > Affects Versions: 11.1.0.GA > Environment: RHEL7, devtools 2.1 \[1\] and DevStudio 11 snapshot \[2\]. > \[1\] http://brewweb.engineering.redhat.com/brewroot/repos/devtools-2.1-rh-ecli... > \[2\] https://devstudio.redhat.com/11/snapshots/rpms/11/x86_64/ > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.3.0.GA > > Attachments: 12426720_rh-eclipse47-devstudio4.7.1-5.2.el7.log.20171024-1353_strict.txt > > > [~nickboldt] said: > {quote} > There appear to be two connectors causing problems. When I simply install Spring, I get this: > [^12426720_rh-eclipse47-devstudio4.7.1-5.2.el7.log.20171024-1353_strict.txt] > So we'll need to figure out which plugins have require-bundle restrictions instead of import-package ones, and submit a fix upstream to https://github.com/spring-projects/spring-ide/issues ... https://github.com/spring-projects/spring-ide/issues/211 > {quote} > An upstream issue: > https://github.com/spring-projects/spring-ide/issues/211 > We have to pull new version of Spring IDE plugin and update the Central discovery site. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018