April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22134: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Sometimes docker image data are not shown in Deploy to OpenShift wizard > ----------------------------------------------------------------------- > > Key: JBIDE-22134 > URL: https://issues.jboss.org/browse/JBIDE-22134 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22150) Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22150?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22150: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22150 > URL: https://issues.jboss.org/browse/JBIDE-22150 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > > When opening a New OpenShift 3 Server Adapter wizard via context menu of a service in Properties view, the selected service from properties view is not preselected in the wizard. This is happening for more services within one project. It select first service under a project in the wizard. Preselection of a service for different projects works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22150) Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22150?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22150: ----------------------------------- Assignee: Andre Dietisheim > Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22150 > URL: https://issues.jboss.org/browse/JBIDE-22150 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > > When opening a New OpenShift 3 Server Adapter wizard via context menu of a service in Properties view, the selected service from properties view is not preselected in the wizard. This is happening for more services within one project. It select first service under a project in the wizard. Preselection of a service for different projects works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-636) Missing DS feature in JBDS-IS 9.0.0.CR1 earlyaccess

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-636?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-636. ----------------------------------- Verified with JBDS 9.1.0.CR1b (B495) + JBDS-IS 9.0.0.CR1a > Missing DS feature in JBDS-IS 9.0.0.CR1 earlyaccess > --------------------------------------------------- > > Key: JBTIS-636 > URL: https://issues.jboss.org/browse/JBTIS-636 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.CR1a > > > There is no DS feature such as com.jboss.devstudio.integration-stack.ds.feature at > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.0.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3598: ------------------------------------- [~nickboldt], respin-c? Do we have one? :) I don't think this is critical enough to warrant a new respin. But if we have one, then sure, it would be great to have the info complete. You can also point to to repo in the readme in that case. But I wouldn't mention that the zip is no longer supported - I think for now it is. We can talk about removing it completely for the next release. > Error while building Jboss developer studio 9.1.0 Beta 2 from source > -------------------------------------------------------------------- > > Key: JBDS-3598 > URL: https://issues.jboss.org/browse/JBDS-3598 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.1.0.Beta2 > Environment: RHEL 7.1 PPC64le and Ubuntu x86_64 > Maven - 3.3.9 > JDK - 1.8 > Reporter: Deepali Chourasia > Assignee: Nick Boldt > Labels: respin-c > Fix For: 9.1.0.GA > > Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt > > > I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source. > The build fails with the following error: > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3787: ----------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3787: ---------------------------------- Summary: Installer - Installation of each component should be optional Key: JBDS-3787 URL: https://issues.jboss.org/browse/JBDS-3787 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 9.1.0.GA Reporter: Len DiMaggio Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3787: ------------------------------- Labels: havoc (was: ) > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Labels: havoc > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-657) Fuse EA tooling cannot be installed from central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-657?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-657: ----------------------------------------- [~pleacu] do you have any idea how can we hide the quickstart until a user enables early access? > Fuse EA tooling cannot be installed from central > ------------------------------------------------ > > Key: JBTIS-657 > URL: https://issues.jboss.org/browse/JBTIS-657 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.CR1 > Reporter: Jan Richter > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Final > > > It fails with the following message: > {noformat}Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found{noformat} > and this is in the error log: > {noformat}HTTP Server 'Gateway Timeout': https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.1.Final-SNAP... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-657) Fuse EA tooling cannot be installed from central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-657?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky edited comment on JBTIS-657 at 4/11/16 9:52 AM: ------------------------------------------------------------------ The Fuse tooling can be installed if we enable the EA and the JBDS instance is run with the following args {code} -Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/earlyaccess/devstudio-directory.xml -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/ -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/earlyaccess/ -Djboss.discovery.site.url=https://devstudio.redhat.com/9.0/staging/updates/ -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/9.1.0.CR1b/ -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/9.1.0.CR1b/devstudio-earlyaccess.properties {code} I assume that after releasing GA builds of JBDS and JBDS-IS then we do not have to set the args above. So, the only problem is that the quickstart is visible even if we didn't enable EA. was (Author: apodhrad): The Fuse tooling can be installed if we enable the EA and the JBDS instance is run with the following args {code} -Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/earlyaccess/devstudio-directory.xml -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/ -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/earlyaccess/ -Djboss.discovery.site.url=https://devstudio.redhat.com/9.0/staging/updates/ -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/9.1.0.CR1b/ -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/9.1.0.CR1b/devstudio-earlyaccess.properties {code} I assume that after releasing GA builds of JBDS and JBDS-IS then we do have to set the args above. So, the only problem is that the quickstart is visible even if we didn't enable EA. > Fuse EA tooling cannot be installed from central > ------------------------------------------------ > > Key: JBTIS-657 > URL: https://issues.jboss.org/browse/JBTIS-657 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.CR1 > Reporter: Jan Richter > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Final > > > It fails with the following message: > {noformat}Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found{noformat} > and this is in the error log: > {noformat}HTTP Server 'Gateway Timeout': https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.1.Final-SNAP... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2016