August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22856) TP does not allow to run RedDeer UI tests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22856?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22856: ------------------------------- Sprint: devex #119 August 2016 > TP does not allow to run RedDeer UI tests > ----------------------------------------- > > Key: JBIDE-22856 > URL: https://issues.jboss.org/browse/JBIDE-22856 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.1.Final > > > The TP does not allow to run RedDeer UI tests. When launching such a test, the following error is shown: > {code:shell} > !ENTRY org.eclipse.osgi 4 0 2016-07-29 16:46:32.581 > !MESSAGE Application error > !STACK 1 > java.lang.RuntimeException: Application "org.jboss.reddeer.ui.reddeertestapplication" could not be found in the registry. The applications available are: org.eclipse.ant.core.antRunner, org.eclipse.ant.ui.antRunner, org.eclipse.datatools.connectivity.console.profile.StorageFileEditor, org.eclipse.e4.ui.workbench.swt.E4Application, org.eclipse.e4.ui.workbench.swt.GenTopic, org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger, org.eclipse.emf.codegen.ecore.Generator, org.eclipse.emf.importer.ecore.Ecore2GenModel, org.eclipse.emf.importer.java.Java2GenModel, org.eclipse.emf.importer.rose.Rose2GenModel, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.reconciler.application, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication, org.eclipse.equinox.p2.touchpoint.natives.nativePackageExtractor, org.eclipse.equinox.p2.updatesite.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.CategoryPublisher, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool, org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter, org.eclipse.jdt.core.JavaIndexer, org.eclipse.pde.build.Build, org.eclipse.pde.junit.runtime.uitestapplication, org.eclipse.pde.junit.runtime.legacytestapplication, org.eclipse.pde.junit.runtime.coretestapplication, org.eclipse.pde.junit.runtime.coretestapplicationnonmain, org.eclipse.pde.junit.runtime.nonuithreadtestapplication, org.eclipse.swtbot.eclipse.core.swtbottestapplication, org.eclipse.ui.ide.workbench, org.eclipse.wst.jsdt.core.JavaCodeFormatter, org.eclipse.wst.server.preview.preview, org.eclipse.xsd.ecore.importer.XSD2GenModel. > at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248) > at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2340) Move jbds.target to JBDS repository

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2340?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2340. ---------------------------- Fix Version/s: 10.1.0.GA (was: LATER) Resolution: Done Closing. This isn't happening because the process for development and maintenance of the TPs makes it easier/better/safer to have them co-located in the same repo. That way diffs/changes can be easily applied in jbt and devstudio TPs via the same PRs. Moving to another repo would split this into two PRs, making PR builds more complicated. > Move jbds.target to JBDS repository > ----------------------------------- > > Key: JBDS-2340 > URL: https://issues.jboss.org/browse/JBDS-2340 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Optional > Labels: f2f2012 > Fix For: 10.1.0.GA > > > The jbds.target file should reside in JBDS SVN. > It must contain what we want in JBDS: latest versions of all 3rd-party dependencies. > No Birt, No GWT. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2340) Move jbds.target to JBDS repository

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2340?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2340. ---------------------------- Resolution: Rejected > Move jbds.target to JBDS repository > ----------------------------------- > > Key: JBDS-2340 > URL: https://issues.jboss.org/browse/JBDS-2340 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Optional > Labels: f2f2012 > > The jbds.target file should reside in JBDS SVN. > It must contain what we want in JBDS: latest versions of all 3rd-party dependencies. > No Birt, No GWT. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22581: ------------------------------- Sprint: devex #120 September 2016 > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM1 > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22611: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.2.AM1) > target platform validation fails to detect duplicate IUs > -------------------------------------------------------- > > Key: JBIDE-22611 > URL: https://issues.jboss.org/browse/JBIDE-22611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.Final > > > Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example: > {code} > [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency. > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022) > BUILD FAILED > {code} > But this is not the same error that Paul Leacu recently reported: > {code} > > [ERROR] Resolution failed: > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code} > So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is. > Either way, we need to make these problems more visible so they're caught sooner. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22611. ------------------------------ Resolution: Done Tycho 0.26 released today so this could be fixed too. > target platform validation fails to detect duplicate IUs > -------------------------------------------------------- > > Key: JBIDE-22611 > URL: https://issues.jboss.org/browse/JBIDE-22611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.Final > > > Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example: > {code} > [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency. > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022) > BUILD FAILED > {code} > But this is not the same error that Paul Leacu recently reported: > {code} > > [ERROR] Resolution failed: > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code} > So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is. > Either way, we need to make these problems more visible so they're caught sooner. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23024) [p2diff] Add ability to do binary comparison of IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23024?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23024: ------------------------------- Sprint: devex #120 September 2016 > [p2diff] Add ability to do binary comparison of IUs > --------------------------------------------------- > > Key: JBIDE-23024 > URL: https://issues.jboss.org/browse/JBIDE-23024 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > See https://github.com/irbull/p2diff/issues/12 and JBIDE-22968 for context & why this enhancement is a good one. > Currently, only openshift has the potential to include a nested SNAPSHOT jar in the lib/ folder of openshift.client, so the problem is relatively localized. > In future however this may come back and be more urgent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3996) No installer jar as a result of jbdevstudio-product repo build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3996?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3996. ------------------------------ Resolution: Done Merged in master for 10.1.0.GA. Thanks, [~mmalina] > No installer jar as a result of jbdevstudio-product repo build > -------------------------------------------------------------- > > Key: JBDS-3996 > URL: https://issues.jboss.org/browse/JBDS-3996 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer > Affects Versions: 10.1.0.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.1.0.GA > > > When I build the jbdevstudio-product git repo using {code}mvn clean verify -DskipTests{code}, I was expecting to have the installer jar created in installer/target/, but all I see is a installer-10.1.0-SNAPSHOT.zip , not the installer jar (which should be called devstudio*.jar). > This was on mac and I did it because I wanted to verify this JIRA: > JBDS-3986 support building devstudio on windows > So I wanted to try this on another platform first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22866) Update arquillian bot integration tests to be more reliable - less prone to timing related failures

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22866?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-22866. -------------------------------- Changes have been made. > Update arquillian bot integration tests to be more reliable - less prone to timing related failures > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-22866 > URL: https://issues.jboss.org/browse/JBIDE-22866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.1.AM1 > Reporter: Len DiMaggio > Fix For: 4.4.1.AM3 > > > Some of the org.jboss.tools.arquillian.ui.bot.test tests are experiencing intermittent failures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3954) Target Platform Requirements for JBDS 10.0.1.GA

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3954?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3954: ----------------------------- > Target Platform Requirements for JBDS 10.0.1.GA > ----------------------------------------------- > > Key: JBDS-3954 > URL: https://issues.jboss.org/browse/JBDS-3954 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: 3rd-party-certification > Affects Versions: 10.1.0.AM1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.1.0.AM3 > > > Track changes to third party inclusions in JBDS 10.0.1 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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