[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:
-------------------------------------
Sprint: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018, devex #150 June 2018, devex #152 July 2018 (was: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018, devex #150 June 2018, devex #151 June 2018)
> 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, upstream
> Fix For: 4.9.0.AM1
>
> 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, 8 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 updated JBIDE-25700:
-------------------------------------
Fix Version/s: 4.9.0.AM1
(was: 4.6.0.Final)
> 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, upstream
> Fix For: 4.9.0.AM1
>
> 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, 8 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:
------------------------------------------
warning for oc 3.11 on linux was reverted. Reopening for a fix in 4.9.AM1
> 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, upstream
> Fix For: 4.6.0.Final
>
> 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, 8 months
[JBoss JIRA] (JBIDE-26179) New Application Wizard: Add refresh button for project selection/Better selection of projects
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-26179:
-------------------------------------
Summary: New Application Wizard: Add refresh button for project selection/Better selection of projects
Key: JBIDE-26179
URL: https://issues.jboss.org/browse/JBIDE-26179
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.6.0.Final
Environment: F28
console.engint.openshift.com
Reporter: Josef Kopriva
In New Application Wizard could be added button for refresh of projects. The reason is, in some cases this is not refreshed.
Workflow:
1. Create connection to console engint.openshift.com
2. Delete all projects in connection
3. Open New Application Wizard from File -> New
4. Select connection
5. When you are asked to create project create it
6. Now you should be on New Application Wizard, but project is not selected
Workaround: You can click on Back and Next afterwards, so you can see now project.
I suppose this issue is caused with slower server response, so user should be able to to refresh projects list and maybe edit projects(if he enter wrong name...).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26179) New Application Wizard: Add refresh button for project selection/Better selection of projects
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26179?page=com.atlassian.jira.plugi... ]
Josef Kopriva reassigned JBIDE-26179:
-------------------------------------
Assignee: Josef Kopriva
> New Application Wizard: Add refresh button for project selection/Better selection of projects
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-26179
> URL: https://issues.jboss.org/browse/JBIDE-26179
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: F28
> console.engint.openshift.com
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
>
> In New Application Wizard could be added button for refresh of projects. The reason is, in some cases this is not refreshed.
> Workflow:
> 1. Create connection to console engint.openshift.com
> 2. Delete all projects in connection
> 3. Open New Application Wizard from File -> New
> 4. Select connection
> 5. When you are asked to create project create it
> 6. Now you should be on New Application Wizard, but project is not selected
> Workaround: You can click on Back and Next afterwards, so you can see now project.
> I suppose this issue is caused with slower server response, so user should be able to to refresh projects list and maybe edit projects(if he enter wrong name...).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26178) Stacks errors when creating new server
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26178?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-26178 at 7/11/18 6:13 AM:
----------------------------------------------------------------
I have set up jboss-stacks jenkins verification job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/JBoss%2.... It really show errors in yaml validation of changed files.
Imho, it would be enough to run some unit tests when changing stacks and other yaml files in order to avoid this kind of bugs.
Anyway, I will try to set up a PR check job and link it with github repo but it might require someone with proper rights.
was (Author: odockal):
I have set up jboss-stacks jenkins verification job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/JBoss%2.... It really show errors in yaml validation of changed files.
Imho, it would be enough to run some unit tests when changing stacks and other yaml files...
> Stacks errors when creating new server
> --------------------------------------
>
> Key: JBIDE-26178
> URL: https://issues.jboss.org/browse/JBIDE-26178
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.6.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.6.0.Final
>
> Attachments: missing-commas.png, parse-errors.png
>
>
> When you try to create a server for the first time, stacks.yaml (and pre-stacks.yaml) is downloaded and currently it's invalid yaml, so there are errors thrown in the Error Log view.
> !parse-errors.png!
> One example:
> {code}
> Can't access or parse https://raw.githubusercontent.com/jboss-developer/jboss-stacks/1.0.0.Fina...
> {code}
> {code}
> while parsing a flow mapping
> in "<reader>", line 201, column 12:
> labels: {
> ^
> expected ',' or '}', but got Value
> in "<reader>", line 206, column 25:
> wtp-runtime-type: org.jboss.ide.eclipse.as.runti ...
> ^
> at org.yaml.snakeyaml.parser.ParserImpl$ParseFlowMappingKey.produce(ParserImpl.java:734)
> at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:160)
> at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:145)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeSequenceNode(Composer.java:204)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:157)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
> at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
> at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480)
> at org.yaml.snakeyaml.Yaml.load(Yaml.java:411)
> at org.jboss.jdf.stacks.parser.Parser.parse(Parser.java:55)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromFile(StacksManager.java:177)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromURL(StacksManager.java:163)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:154)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:141)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:106)
> at org.fusesource.ide.server.fuse.core.runtime.integration.FuseDownloadRuntimesProvider.getStacks(FuseDownloadRuntimesProvider.java:29)
> at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.loadDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:66)
> at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.getDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:50)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadableRuntimesFromProviders(RuntimeExtensionManager.java:273)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadRuntimes(RuntimeExtensionManager.java:257)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:199)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:187)
> at org.jboss.tools.runtime.core.RuntimeCoreActivator.getDownloadRuntimes(RuntimeCoreActivator.java:136)
> at org.jboss.tools.as.runtimes.integration.util.DownloadRuntimeServerUtil.getDownloadRuntimes(DownloadRuntimeServerUtil.java:41)
> at org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHyperlinkComposite$1.run(DownloadRuntimeHyperlinkComposite.java:169)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> Apparently [~rob.stryker] broke the file 14 hours ago with this commit:
> https://github.com/jboss-developer/jboss-stacks/commit/48ff290ca4c3f8e901...
> See the missing commas here:
> !missing-commas.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26178) Stacks errors when creating new server
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26178?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26178:
---------------------------------------
I have set up jboss-stacks jenkins verification job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/JBoss%2.... It really show errors in yaml validation of changed files.
Imho, it would be enough to run some unit tests when changing stacks and other yaml files...
> Stacks errors when creating new server
> --------------------------------------
>
> Key: JBIDE-26178
> URL: https://issues.jboss.org/browse/JBIDE-26178
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.6.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.6.0.Final
>
> Attachments: missing-commas.png, parse-errors.png
>
>
> When you try to create a server for the first time, stacks.yaml (and pre-stacks.yaml) is downloaded and currently it's invalid yaml, so there are errors thrown in the Error Log view.
> !parse-errors.png!
> One example:
> {code}
> Can't access or parse https://raw.githubusercontent.com/jboss-developer/jboss-stacks/1.0.0.Fina...
> {code}
> {code}
> while parsing a flow mapping
> in "<reader>", line 201, column 12:
> labels: {
> ^
> expected ',' or '}', but got Value
> in "<reader>", line 206, column 25:
> wtp-runtime-type: org.jboss.ide.eclipse.as.runti ...
> ^
> at org.yaml.snakeyaml.parser.ParserImpl$ParseFlowMappingKey.produce(ParserImpl.java:734)
> at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:160)
> at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:145)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeSequenceNode(Composer.java:204)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:157)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
> at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
> at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480)
> at org.yaml.snakeyaml.Yaml.load(Yaml.java:411)
> at org.jboss.jdf.stacks.parser.Parser.parse(Parser.java:55)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromFile(StacksManager.java:177)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromURL(StacksManager.java:163)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:154)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:141)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:106)
> at org.fusesource.ide.server.fuse.core.runtime.integration.FuseDownloadRuntimesProvider.getStacks(FuseDownloadRuntimesProvider.java:29)
> at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.loadDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:66)
> at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.getDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:50)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadableRuntimesFromProviders(RuntimeExtensionManager.java:273)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadRuntimes(RuntimeExtensionManager.java:257)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:199)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:187)
> at org.jboss.tools.runtime.core.RuntimeCoreActivator.getDownloadRuntimes(RuntimeCoreActivator.java:136)
> at org.jboss.tools.as.runtimes.integration.util.DownloadRuntimeServerUtil.getDownloadRuntimes(DownloadRuntimeServerUtil.java:41)
> at org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHyperlinkComposite$1.run(DownloadRuntimeHyperlinkComposite.java:169)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> Apparently [~rob.stryker] broke the file 14 hours ago with this commit:
> https://github.com/jboss-developer/jboss-stacks/commit/48ff290ca4c3f8e901...
> See the missing commas here:
> !missing-commas.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26178) Stacks errors when creating new server
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26178?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-26178:
-------------------------------
Fix Version/s: 4.6.0.Final
> Stacks errors when creating new server
> --------------------------------------
>
> Key: JBIDE-26178
> URL: https://issues.jboss.org/browse/JBIDE-26178
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.6.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.6.0.Final
>
> Attachments: missing-commas.png, parse-errors.png
>
>
> When you try to create a server for the first time, stacks.yaml (and pre-stacks.yaml) is downloaded and currently it's invalid yaml, so there are errors thrown in the Error Log view.
> !parse-errors.png!
> One example:
> {code}
> Can't access or parse https://raw.githubusercontent.com/jboss-developer/jboss-stacks/1.0.0.Fina...
> {code}
> {code}
> while parsing a flow mapping
> in "<reader>", line 201, column 12:
> labels: {
> ^
> expected ',' or '}', but got Value
> in "<reader>", line 206, column 25:
> wtp-runtime-type: org.jboss.ide.eclipse.as.runti ...
> ^
> at org.yaml.snakeyaml.parser.ParserImpl$ParseFlowMappingKey.produce(ParserImpl.java:734)
> at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:160)
> at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:145)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeSequenceNode(Composer.java:204)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:157)
> at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
> at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
> at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
> at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480)
> at org.yaml.snakeyaml.Yaml.load(Yaml.java:411)
> at org.jboss.jdf.stacks.parser.Parser.parse(Parser.java:55)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromFile(StacksManager.java:177)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromURL(StacksManager.java:163)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:154)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:141)
> at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:106)
> at org.fusesource.ide.server.fuse.core.runtime.integration.FuseDownloadRuntimesProvider.getStacks(FuseDownloadRuntimesProvider.java:29)
> at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.loadDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:66)
> at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.getDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:50)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadableRuntimesFromProviders(RuntimeExtensionManager.java:273)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadRuntimes(RuntimeExtensionManager.java:257)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:199)
> at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:187)
> at org.jboss.tools.runtime.core.RuntimeCoreActivator.getDownloadRuntimes(RuntimeCoreActivator.java:136)
> at org.jboss.tools.as.runtimes.integration.util.DownloadRuntimeServerUtil.getDownloadRuntimes(DownloadRuntimeServerUtil.java:41)
> at org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHyperlinkComposite$1.run(DownloadRuntimeHyperlinkComposite.java:169)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> Apparently [~rob.stryker] broke the file 14 hours ago with this commit:
> https://github.com/jboss-developer/jboss-stacks/commit/48ff290ca4c3f8e901...
> See the missing commas here:
> !missing-commas.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months