February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21792) Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21792?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21792: -------------------------------- Priority: Minor (was: Major) > Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically > --------------------------------------------------------------------------- > > Key: JBIDE-21792 > URL: https://issues.jboss.org/browse/JBIDE-21792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Minor > Labels: openshift_v2, server_adapter_wizard > Fix For: LATER > > > Domains listed in a combo in the New OpenShift 2 Server Adapter wizard are currently not order alphabetically or alphanumerically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21788) Jenkins: builds for master and jbosstools-4.3.x are failing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21788?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21788: ------------------------------- Summary: Jenkins: builds for master and jbosstools-4.3.x are failing (was: Jenkins: builds for master and jbosstools-4.3.x are failing for openshift) > Jenkins: builds for master and jbosstools-4.3.x are failing > ----------------------------------------------------------- > > Key: JBIDE-21788 > URL: https://issues.jboss.org/browse/JBIDE-21788 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Priority: Critical > Labels: build, jenkins > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Both jenkins builds for [jbosstools-4.3.x|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbo...] and [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > 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:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > 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:497) > 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.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. > at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490) > at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21788) Jenkins: builds for master and jbosstools-4.3.x are failing for openshift

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21788?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21788: ------------------------------- Component/s: build (was: openshift) > Jenkins: builds for master and jbosstools-4.3.x are failing for openshift > ------------------------------------------------------------------------- > > Key: JBIDE-21788 > URL: https://issues.jboss.org/browse/JBIDE-21788 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Priority: Critical > Labels: build, jenkins > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Both jenkins builds for [jbosstools-4.3.x|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbo...] and [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > 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:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > 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:497) > 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.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. > at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490) > at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21792) Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21792?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21792: -------------------------------- Fix Version/s: LATER > Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically > --------------------------------------------------------------------------- > > Key: JBIDE-21792 > URL: https://issues.jboss.org/browse/JBIDE-21792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Labels: openshift_v2, server_adapter_wizard > Fix For: LATER > > > Domains listed in a combo in the New OpenShift 2 Server Adapter wizard are currently not order alphabetically or alphanumerically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3644) Document installer/cdk/devstudio basic workflow

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3644?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3644: ----------------------------------- Specifically for "Container Development" - Start CDK - Insure things are working correctly (e.g. hit the openshift console URL) then 2 paths A & B: A1) New Java Project with Dockerfile A2) Docker build (via the CDK) A3) Docker run (via the CDK) A4) run that Docker image on OpenShift (via the CDK) B1) New OpenShift Java Project from Template B2) Initial deployment (via CDK) B3) Edit-Save-Refresh B4) Debug > Document installer/cdk/devstudio basic workflow > ----------------------------------------------- > > Key: JBDS-3644 > URL: https://issues.jboss.org/browse/JBDS-3644 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation > Reporter: Max Rydahl Andersen > Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-564) Cannot install Fuse / SwitchYard tooling in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-564?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-564: -------------------------------- Assignee: Paul Leacu > Cannot install Fuse / SwitchYard tooling in offline mode > -------------------------------------------------------- > > Key: JBTIS-564 > URL: https://issues.jboss.org/browse/JBTIS-564 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1a EA Zip (md5 6ab445b312d39c451802232c5a54846b) > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) > Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found > Cannot satisfy dependency: > From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) > To: org.switchyard.tools.feature.feature.group 0.0.0 > {code} > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) > Missing requirement: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) requires 'org.eclipse.zest.core 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-564) Cannot install Fuse / SwitchYard tooling in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-564?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-564: ------------------------------------ Description: {code} Cannot complete the install because one or more required items could not be found. Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found Cannot satisfy dependency: From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) To: org.switchyard.tools.feature.feature.group 0.0.0 {code} {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) Missing requirement: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) requires 'org.eclipse.zest.core 0.0.0' but it could not be found {code} was: {code} Cannot complete the install because one or more required items could not be found. Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found Cannot satisfy dependency: From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) To: org.switchyard.tools.feature.feature.group 0.0.0 {code} > Cannot install Fuse / SwitchYard tooling in offline mode > -------------------------------------------------------- > > Key: JBTIS-564 > URL: https://issues.jboss.org/browse/JBTIS-564 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1a EA Zip (md5 6ab445b312d39c451802232c5a54846b) > Reporter: Andrej Podhradsky > Priority: Critical > > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) > Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found > Cannot satisfy dependency: > From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) > To: org.switchyard.tools.feature.feature.group 0.0.0 > {code} > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) > Missing requirement: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) requires 'org.eclipse.zest.core 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-564) Cannot install Fuse / SwitchYard tooling in offline mode

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-564: --------------------------------------- Summary: Cannot install Fuse / SwitchYard tooling in offline mode Key: JBTIS-564 URL: https://issues.jboss.org/browse/JBTIS-564 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 9.0.0.Beta1 Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1a EA Zip (md5 6ab445b312d39c451802232c5a54846b) Reporter: Andrej Podhradsky Priority: Critical {code} Cannot complete the install because one or more required items could not be found. Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found Cannot satisfy dependency: From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) To: org.switchyard.tools.feature.feature.group 0.0.0 {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3647) Investigate why we are including both cygwin and mingw

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3647?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3647: --------------------------------- Labels: havoc (was: ) > Investigate why we are including both cygwin and mingw > ------------------------------------------------------ > > Key: JBDS-3647 > URL: https://issues.jboss.org/browse/JBDS-3647 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: cdk, installer, openshift > Reporter: Pete Muir > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > > We shouldn't need to include cygwin to make vagrant work. Let's check why we include this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3648) Remove confirmation dialog at start of installer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3648?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3648: --------------------------------- Labels: havoc (was: ) > Remove confirmation dialog at start of installer > ------------------------------------------------ > > Key: JBDS-3648 > URL: https://issues.jboss.org/browse/JBDS-3648 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Pete Muir > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > There is no need to request confirmation before the unpacker. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2016