October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23380: ------------------------------------- Not sure if this is connected with this issue but I can not build jbosstools-openshift via vanilla "clean verify": {code} [INFO] jbosstools-openshift ............................... SUCCESS [ 2.690 s] [INFO] openshift.plugins .................................. SUCCESS [ 0.041 s] [INFO] org.jboss.tools.openshift.egit.core ................ SUCCESS [ 25.366 s] [INFO] org.jboss.tools.openshift.egit.ui .................. SUCCESS [ 3.055 s] [INFO] org.jboss.tools.openshift.express.client ........... SUCCESS [ 16.112 s] [INFO] org.jboss.tools.openshift.common.core .............. SUCCESS [ 7.867 s] [INFO] org.jboss.tools.openshift.express.core ............. SUCCESS [ 6.720 s] [INFO] org.jboss.tools.openshift.common.ui ................ SUCCESS [ 27.254 s] [INFO] org.jboss.tools.openshift.express.ui ............... SUCCESS [ 13.835 s] [INFO] org.jboss.tools.openshift.client ................... FAILURE [ 1.593 s] [INFO] org.jboss.tools.openshift.core ..................... SKIPPED [INFO] org.jboss.tools.openshift.ui ....................... SKIPPED [INFO] org.jboss.tools.openshift.cdk.server ............... SKIPPED [INFO] openshift.tests .................................... SKIPPED [INFO] org.jboss.tools.openshift.egit.test ................ SKIPPED [INFO] org.jboss.tools.openshift.express.test ............. SKIPPED [INFO] org.jboss.tools.openshift.test ..................... SKIPPED [INFO] org.jboss.tools.openshift.cdk.server.test .......... SKIPPED [INFO] openshift.features ................................. SKIPPED [INFO] org.jboss.tools.openshift.feature .................. SKIPPED [INFO] org.jboss.tools.openshift.test.feature ............. SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.feature . SKIPPED [INFO] org.jboss.tools.openshift.egit.integration.test.feature SKIPPED [INFO] org.jboss.tools.openshift.express.feature .......... SKIPPED [INFO] org.jboss.tools.openshift.express.test.feature ..... SKIPPED [INFO] org.jboss.tools.openshift.cdk.feature .............. SKIPPED [INFO] org.jboss.tools.openshift.cdk.test.feature ......... SKIPPED [INFO] openshift.site ..................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:27 min [INFO] Finished at: 2016-10-20T12:27:46+02:00 [INFO] Final Memory: 123M/749M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (core-has-ui-deps) on project org.jboss.tools.openshift.client: Execution core-has-ui-deps of goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed. NullPointerException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (core-has-ui-deps) on project org.jboss.tools.openshift.client: Execution core-has-ui-deps of goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed. 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:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) 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 core-has-ui-deps of goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 20 more Caused by: java.lang.NullPointerException at org.jboss.tools.releng.CoreUIDependency.findAllDependencies(CoreUIDependency.java:123) at org.jboss.tools.releng.CoreUIDependency.createModel(CoreUIDependency.java:73) at org.jboss.tools.releng.CoreUIDependency.createModel(CoreUIDependency.java:68) at org.jboss.tools.releng.CoreUIDependency.execute(CoreUIDependency.java:45) at org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:193) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) ... 21 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :org.jboss.tools.openshift.client {code} I have updated parent and base bit this does not help :/ > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23380: ---------------------------------------- This make some components that aren't ready for that rule fail. As there is no resources allocating to fixing this in the sprint AFAIK, please revert the change and make sure it doesn't introduce unexpected extra cost before adopting it. > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-835) Update bpmn2 modeler in both Mars and Neon

by Andrej Podhradsky (JIRA)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-648) Improve the tracking of BPMN2 issues

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-648?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-648. ----------------------------------- I'm closing this issue since QE has all needed permissions. > Improve the tracking of BPMN2 issues > ------------------------------------ > > Key: JBTIS-648 > URL: https://issues.jboss.org/browse/JBTIS-648 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2 > Affects Versions: 4.0.0 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > Fix For: 4.3.0.Final > > > Currently, BPMN2 issues are reported at Eclipse Bugzilla or Red Hat Bugzilla. Our problem is that we are no able to directly query all resolved issues related a specific build (for this purpose we use https://www.eclipse.org/bpmn2-modeler/whatsnew/). > Unfortunately, in Eclipse bugzilla QE doesn't have permissions to change a status of issues which were not created by QE (it seems that only commiters have such permissions). This is very important in testing cycles. > In Red Hat bugzilla all BPMN2 issues are a part of the BxMS products. I'm not sure whether this is the right place for all BPMN2 issues (it would also mean to clone existing issues from Eclipse bugzilla). > Other solutions could be > * Jira will be our primary tracker for BPMN2 issues (and all issues be cloned from Eclipse BZ) > * or move the whole project to the Jira JBoss Tools > What do you think? Do you have any ideas how to improve the process? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-921) Add an IS presence in developers.redhat.com

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-921?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-921: ------------------------------------ Attachment: web_screenshot.png > Add an IS presence in developers.redhat.com > ------------------------------------------- > > Key: JBTIS-921 > URL: https://issues.jboss.org/browse/JBTIS-921 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.2.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: web_screenshot.png > > > Modify the devstudio product in developers.redhat.com to point to an Integration Stack non-product. From there reference Fuse Tooling, DataVirt and BRMS tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-921) Add an IS presence in developers.redhat.com

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-921?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-921. ----------------------------------- Verified > Add an IS presence in developers.redhat.com > ------------------------------------------- > > Key: JBTIS-921 > URL: https://issues.jboss.org/browse/JBTIS-921 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.2.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: web_screenshot.png > > > Modify the devstudio product in developers.redhat.com to point to an Integration Stack non-product. From there reference Fuse Tooling, DataVirt and BRMS tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-937) Update tests so that they use JBTIS TP to 4.4.0.CR1

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-937?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-937. ------------------------------ Resolution: Done PR was pushed to _jbtis-4.4.x_ branch > Update tests so that they use JBTIS TP to 4.4.0.CR1 > --------------------------------------------------- > > Key: JBTIS-937 > URL: https://issues.jboss.org/browse/JBTIS-937 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final > > > Update tests so that they use JBTIS TP to 4.4.0.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-4059: ----------------------------------- And per the recent component qe shuffle, cc'ing [~lvalach], enjoy :) > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Rastislav Wagner reassigned JBDS-4077: -------------------------------------- Assignee: Nick Boldt (was: Rastislav Wagner) > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Rastislav Wagner commented on JBDS-4077: ---------------------------------------- [~akazakov] yes, none of our integration-tests pr check jobs will work until this is fixed > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Rastislav Wagner > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016