November 2018 - jbosstools-issues

[JBoss JIRA] (JBDS-4739) devstudio.product_master Job on Jenkins is failing

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBDS-4739?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-4739. ------------------------------- > devstudio.product_master Job on Jenkins is failing > -------------------------------------------------- > > Key: JBDS-4739 > URL: https://issues.jboss.org/browse/JBDS-4739 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 12.10.0.AM1 > Environment: Jenkins > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Job is failing due to *Could not resolve plugin org.eclipse.equinox.launcher.win32.win32.x86_null;* > Full Log: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code:java} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:1.3.0-SNAPSHOT:build-qualifier-aggregator (default-build-qualifier-aggregator) on project com.jboss.devstudio.core.site: Execution default-build-qualifier-aggregator of goal org.eclipse.tycho:tycho-packaging-plugin:1.3.0-SNAPSHOT:build-qualifier-aggregator failed: Could not resolve plugin org.eclipse.equinox.launcher.win32.win32.x86_null; Path to dependency: -> [Help 1] > 14:37:28 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:1.3.0-SNAPSHOT:build-qualifier-aggregator (default-build-qualifier-aggregator) on project com.jboss.devstudio.core.site: Execution default-build-qualifier-aggregator of goal org.eclipse.tycho:tycho-packaging-plugin:1.3.0-SNAPSHOT:build-qualifier-aggregator failed: Could not resolve plugin org.eclipse.equinox.launcher.win32.win32.x86_null; Path to dependency: > 14:37:28 > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > 14:37:28 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > 14:37:28 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) > 14:37:28 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) > 14:37:28 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) > 14:37:28 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) > 14:37:28 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > 14:37:28 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > 14:37:28 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > 14:37:28 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > 14:37:28 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > 14:37:28 at java.lang.reflect.Method.invoke (Method.java:498) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) > 14:37:28 Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-build-qualifier-aggregator of goal org.eclipse.tycho:tycho-packaging-plugin:1.3.0-SNAPSHOT:build-qualifier-aggregator failed: Could not resolve plugin org.eclipse.equinox.launcher.win32.win32.x86_null; Path to dependency: > 14:37:28 > 14:37:28 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:145) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > 14:37:28 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > 14:37:28 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) > 14:37:28 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) > 14:37:28 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) > 14:37:28 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) > 14:37:28 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > 14:37:28 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > 14:37:28 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > 14:37:28 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > 14:37:28 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > 14:37:28 at java.lang.reflect.Method.invoke (Method.java:498) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) > 14:37:28 Caused by: java.lang.RuntimeException: Could not resolve plugin org.eclipse.equinox.launcher.win32.win32.x86_null; Path to dependency: > 14:37:28 > 14:37:28 at org.eclipse.tycho.core.ArtifactDependencyVisitor.newRuntimeException (ArtifactDependencyVisitor.java:42) > 14:37:28 at org.eclipse.tycho.core.ArtifactDependencyVisitor.missingPlugin (ArtifactDependencyVisitor.java:33) > 14:37:28 at org.eclipse.tycho.core.osgitools.AbstractArtifactDependencyWalker.traversePlugin (AbstractArtifactDependencyWalker.java:216) > 14:37:28 at org.eclipse.tycho.core.osgitools.AbstractArtifactDependencyWalker.traverseProduct (AbstractArtifactDependencyWalker.java:159) > 14:37:28 at org.eclipse.tycho.core.osgitools.EclipseRepositoryProject$1.walk (EclipseRepositoryProject.java:61) > 14:37:28 at org.eclipse.tycho.buildversion.BuildQualifierAggregatorMojo.getBuildTimestamp (BuildQualifierAggregatorMojo.java:77) > 14:37:28 at org.eclipse.tycho.buildversion.BuildQualifierMojo.calculateQualifiedVersion (BuildQualifierMojo.java:162) > 14:37:28 at org.eclipse.tycho.buildversion.BuildQualifierMojo.execute (BuildQualifierMojo.java:135) > 14:37:28 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) > 14:37:28 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > 14:37:28 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) > 14:37:28 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > 14:37:28 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) > 14:37:28 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) > 14:37:28 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) > 14:37:28 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) > 14:37:28 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > 14:37:28 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > 14:37:28 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > 14:37:28 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > 14:37:28 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > 14:37:28 at java.lang.reflect.Method.invoke (Method.java:498) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) > 14:37:28 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) > 14:37:28 [ERROR] > 14:37:28 [ERROR] Re-run Maven using the -X switch to enable full debug logging. > 14:37:28 [ERROR] > 14:37:28 [ERROR] For more information about the errors and possible solutions, please read the following articles: > 14:37:28 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException > 14:37:28 [ERROR] > 14:37:28 [ERROR] After correcting the problems, you can resume the build with the command > 14:37:28 [ERROR] mvn <goals> -rf :com.jboss.devstudio.core.site > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4740) Add a build slave that is capable of building Flatpak versions of Eclipse products

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4740?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4740: -------------------------------- Git Pull Request: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m... (was: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m...) > Add a build slave that is capable of building Flatpak versions of Eclipse products > ---------------------------------------------------------------------------------- > > Key: JBDS-4740 > URL: https://issues.jboss.org/browse/JBDS-4740 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build > Reporter: Mat Booth > Assignee: Mat Booth > Priority: Major > > I'm filing a Jira ticket as suggested in Mattermost. > In order to explore shipping our Eclipse-based products as Flatpak applications, (initially SCL and maybe eventually also JBDS) I need a build slave for the Jenkins[1] that is capable of generating Flatpaks. > The newly released RHEL 7.6 has a sufficiently new version of *flatpak* and *flatpak-builder* packages. Please also ensure there is *java-1.8.0-openjdk-devel* and a recent maven installed. > Please consider adding such a builder. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4745) Drools maven archetype or quickstart using kjar packaging doesn't build

by Mister PM (Jira)

Mister PM created JBDS-4745: ------------------------------- Summary: Drools maven archetype or quickstart using kjar packaging doesn't build Key: JBDS-4745 URL: https://issues.jboss.org/browse/JBDS-4745 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: build Affects Versions: 12.9.0.GA Reporter: Mister PM Attachments: pom.xml Any drools project which needs to use kie-maven-plugin to packing kjar maven project it's falling to build with the following error: An internal error occurred during: "Updating Maven Project". Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie' artifactId = 'kie-maven-plugin' versionRange = '7.13.0.Final' goals = '[]' You can create a maven project from the catalog archetype kie-drools-archetype, which will come with ... <packaging>kjar</packaging> ... ... <plugin> <groupId>org.kie</groupId> <artifactId>kie-maven-plugin</artifactId> <version>${drools-version}</version> <extensions>true</extensions> </plugin> I also added this part here in the pom file <pluginManagement> <plugins>  <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.kie</groupId> <artifactId>kie-maven-plugin</artifactId> <versionRange>${drools-version}</versionRange> <goals> <goal>compile</goal> <goal>package</goal> <goal>build</goal> </goals> </pluginExecutionFilter> <action> <ignore /> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement> Which was a workaround in previous drools version. However this didn't work either. I can build from the command line with or without the pluginManagement and I can build this archetype without issues in other IDE like IntelliJ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24492) Application wizard: Details for custom template are not shown until "Next" is pressed.

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-24492?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24492: ---------------------------------- Sprint: devex #158 November 2019 (was: devex #157 November 2019) > Application wizard: Details for custom template are not shown until "Next" is pressed. > -------------------------------------------------------------------------------------- > > Key: JBIDE-24492 > URL: https://issues.jboss.org/browse/JBIDE-24492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Radim Hopp > Assignee: Josef Kopriva > Priority: Major > Labels: application_wizard > Fix For: 4.10.0.AM1 > > > Almost certainly a regression caused by JBIDE-23473. > I know that validation is now bound to pressing "Next" button, but this prevents from showing user the defined resources on first page of wizard in "Details" section. Maybe showing them on second page would solve the problem? > Screencast: https://youtu.be/uGAmL_sMIXc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26442) Openshift Itests: automate eap-cd tests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26442?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26442: ---------------------------------- Sprint: devex #158 November 2019 (was: devex #157 November 2019) > Openshift Itests: automate eap-cd tests > --------------------------------------- > > Key: JBIDE-26442 > URL: https://issues.jboss.org/browse/JBIDE-26442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26450) Server ITests: Investigate failure in org.jboss.tools.as.itests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26450?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26450: ---------------------------------- Sprint: devex #158 November 2019 (was: devex #157 November 2019) > Server ITests: Investigate failure in org.jboss.tools.as.itests > --------------------------------------------------------------- > > Key: JBIDE-26450 > URL: https://issues.jboss.org/browse/JBIDE-26450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code:java} > org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes[org.jboss.ide.eclipse.as.wildfly.140]Failed with 0 retries > Error Details > Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly> > Stack Trace > junit.framework.AssertionFailedError: Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly> > at org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes(ServerBeanLoaderIntegrationTest.java:69) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26466) Openshift ITests: Investigate why DeleteResources ITests are failing on Jenkins

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26466?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26466: ---------------------------------- Story Points: 5 > Openshift ITests: Investigate why DeleteResources ITests are failing on Jenkins > ------------------------------------------------------------------------------- > > Key: JBIDE-26466 > URL: https://issues.jboss.org/browse/JBIDE-26466 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26466) Openshift ITests: Investigate why DeleteResources ITests are failing on Jenkins

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26466?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26466: ---------------------------------- Sprint: devex #158 November 2019 > Openshift ITests: Investigate why DeleteResources ITests are failing on Jenkins > ------------------------------------------------------------------------------- > > Key: JBIDE-26466 > URL: https://issues.jboss.org/browse/JBIDE-26466 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26466) Openshift ITests: Investigate why DeleteResources ITests are failing on Jenkins

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26466: ------------------------------------- Summary: Openshift ITests: Investigate why DeleteResources ITests are failing on Jenkins Key: JBIDE-26466 URL: https://issues.jboss.org/browse/JBIDE-26466 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, openshift Affects Versions: 4.10.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.10.0.AM1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26465) Openshift ITests: Update nodejs template in tests

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26465: ------------------------------------- Summary: Openshift ITests: Update nodejs template in tests Key: JBIDE-26465 URL: https://issues.jboss.org/browse/JBIDE-26465 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, openshift Affects Versions: 4.10.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.10.0.AM1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 November 2018