October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23126) Eclipse DZone Refcard

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23126?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23126: ------------------------------------- FYI, I will be on two week PTO (31.10 - 13.11), so will not be able to look at this task till mid November If some work need to be done for this issue - let me know and I will drag it to the next sprint > Eclipse DZone Refcard > --------------------- > > Key: JBIDE-23126 > URL: https://issues.jboss.org/browse/JBIDE-23126 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: upstream, website > Reporter: Mickael Istria > Assignee: Mickael Istria > > We're going to have a DZone Refcard about development with Eclipse IDE published. This task is here to track this (mostly complete) effort. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23126) Eclipse DZone Refcard

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23126?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23126: ---------------------------------------- [~lincolnthree] ping. > Eclipse DZone Refcard > --------------------- > > Key: JBIDE-23126 > URL: https://issues.jboss.org/browse/JBIDE-23126 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: upstream, website > Reporter: Mickael Istria > Assignee: Mickael Istria > > We're going to have a DZone Refcard about development with Eclipse IDE published. This task is here to track this (mostly complete) effort. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-941) Prepare a job for verifying TP changes

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-941?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-941: ----------------------------------------- For example to verify issues such as - JBTIS-922 - JBTIS-861 > Prepare a job for verifying TP changes > -------------------------------------- > > Key: JBTIS-941 > URL: https://issues.jboss.org/browse/JBTIS-941 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-941) Prepare a job for verifying TP changes

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-941: --------------------------------------- Summary: Prepare a job for verifying TP changes Key: JBTIS-941 URL: https://issues.jboss.org/browse/JBTIS-941 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-938) Fix using Fuse master (CI) update site in tests

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-938?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-938. ----------------------------------- pushed to master, jbtis-4.3.x and jbtis-4.4.x > Fix using Fuse master (CI) update site in tests > ----------------------------------------------- > > Key: JBTIS-938 > URL: https://issues.jboss.org/browse/JBTIS-938 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.0.Final > > > SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23389) OpenShift 3.4 support

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-23389: -------------------------------------- Summary: OpenShift 3.4 support Key: JBIDE-23389 URL: https://issues.jboss.org/browse/JBIDE-23389 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Alexey Kazakov Assignee: Jeff MAURY Priority: Critical Fix For: 4.4.2.Final OpenShift 3.4 is currently in progress but we need to start testing it now to see if we need adjust anything in our tools to support it. cc: [~adietish] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-936) Fuse: Allow to run 'FuseProjectTest' without fresh Maven repository

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-936?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-936. ----------------------------------- pushed to master, jbtis-4.3.x and jbtis-4.4.x > Fuse: Allow to run 'FuseProjectTest' without fresh Maven repository > ------------------------------------------------------------------- > > Key: JBTIS-936 > URL: https://issues.jboss.org/browse/JBTIS-936 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.4.0.Final > > > to save a lot of time ;-) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23309. -------------------------------- Verified in 10.2.0.AM3 > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, target-platform > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23380 at 10/20/16 9:31 AM: -------------------------------------------------------------------- and yes, this change made openshift go red in jenkins, too. Started on the 20th (today), see [#1623|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1623/]. The actual error is an NPE in the mojo: {code} [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] {code} Happy we reverted. Build is back to the expected. was (Author: adietish): and yes, this change made openshift go red in jenkins, too. Started on the 20th (today), see [#1623|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1623/]. Happy we reverted. > 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23380: ------------------------------------------ and yes, this change made openshift go red in jenkins, too. Started on the 20th (today), see [#1623|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1623/]. Happy we reverted. > 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

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