[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2719:
-------------------------------------
[~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far.
First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet).
With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error.
In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up.
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 days, 5 hours
[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance
by Jim Tyrrell (JIRA)
Console not showing up when staritng a EAP/SOA-P Instance
---------------------------------------------------------
Key: JBDS-983
URL: https://jira.jboss.org/jira/browse/JBDS-983
Project: JBoss Developer Studio
Issue Type: Feature Request
Affects Versions: 3.0.0.M4
Reporter: Jim Tyrrell
For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 month, 2 weeks
[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM:
------------------------------------------------------------
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/
There are ways to achieve more-than-260-char paths, but do we want to?
was (Author: nickboldt):
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
> Align installation default path with installer filename
> -------------------------------------------------------
>
> Key: JBDS-3044
> URL: https://issues.jboss.org/browse/JBDS-3044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: discuss
> Fix For: 8.0.0.Beta3
>
>
> Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync.
> This question is open for discussion. Nick pointed out some reasons against this suggestion:
> {quote}
> Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons:
> a) Max is AFK, and will want to vet/veto this idea
> b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces
> c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience
> So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters.
> Max Rydahl Andersen WDYT?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
2 months, 1 week
[JBoss JIRA] (JBIDE-26461) jbosstools-javaee master build is broken since updated TP
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26461?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26461:
---------------------------------------
jbosstools-webservices also contains StubUtility, the same problem will be there.
> jbosstools-javaee master build is broken since updated TP
> ---------------------------------------------------------
>
> Key: JBIDE-26461
> URL: https://issues.jboss.org/browse/JBIDE-26461
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch, cdi, jsf
> Affects Versions: 4.10.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Blocker
> Fix For: 4.10.0.AM1
>
>
> Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency.
> See the jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cannot resolve org.eclipse.jdt.internal.corext.codemanipulation.StubUtility -> was moved to org.eclipse.jdt.core.codemanipulation with this [commit|https://github.com/eclipse/eclipse.jdt.ui/commit/bc3bc858da1855f31...]
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.3.0-SNAPSHOT:compile (default-compile) on project org.jboss.tools.batch.ui: Compilation failure: Compilation failure:
> 14:48:50 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/batch/plugins/org.jboss.tools.batch.ui/src/org/jboss/tools/batch/ui/internal/wizard/NewBatchArtifactWizardPage.java:[35]
> 14:48:50 [ERROR] import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility;
> 14:48:50 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 14:48:50 [ERROR] The import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility cannot be resolved
> 14:48:50 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/batch/plugins/org.jboss.tools.batch.ui/src/org/jboss/tools/batch/ui/internal/wizard/NewBatchArtifactWizardPage.java:[387]
> 14:48:50 [ERROR] String lineDelimiter = StubUtility.getLineDelimiterUsed(newType
> 14:48:50 [ERROR] ^^^^^^^^^^^
> 14:48:50 [ERROR] StubUtility cannot be resolved
> 14:48:50 [ERROR] 2 problems (2 errors)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (JBIDE-26461) jbosstools-javaee master build is broken since updated TP
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26461?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26461:
----------------------------------
Summary: jbosstools-javaee master build is broken since updated TP (was: jbosstools-javaee master build is broken since updated tycho to 1.3.0-SNAPSHOT)
> jbosstools-javaee master build is broken since updated TP
> ---------------------------------------------------------
>
> Key: JBIDE-26461
> URL: https://issues.jboss.org/browse/JBIDE-26461
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch, cdi, jsf
> Affects Versions: 4.10.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Blocker
> Fix For: 4.10.0.AM1
>
>
> Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency.
> See the jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cannot resolve org.eclipse.jdt.internal.corext.codemanipulation.StubUtility -> was moved to org.eclipse.jdt.core.codemanipulation with this [commit|https://github.com/eclipse/eclipse.jdt.ui/commit/bc3bc858da1855f31...]
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.3.0-SNAPSHOT:compile (default-compile) on project org.jboss.tools.batch.ui: Compilation failure: Compilation failure:
> 14:48:50 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/batch/plugins/org.jboss.tools.batch.ui/src/org/jboss/tools/batch/ui/internal/wizard/NewBatchArtifactWizardPage.java:[35]
> 14:48:50 [ERROR] import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility;
> 14:48:50 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 14:48:50 [ERROR] The import org.eclipse.jdt.internal.corext.codemanipulation.StubUtility cannot be resolved
> 14:48:50 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/batch/plugins/org.jboss.tools.batch.ui/src/org/jboss/tools/batch/ui/internal/wizard/NewBatchArtifactWizardPage.java:[387]
> 14:48:50 [ERROR] String lineDelimiter = StubUtility.getLineDelimiterUsed(newType
> 14:48:50 [ERROR] ^^^^^^^^^^^
> 14:48:50 [ERROR] StubUtility cannot be resolved
> 14:48:50 [ERROR] 2 problems (2 errors)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (JBIDE-26409) Creating of Launcher project in central throws errors
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26409?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-26409.
---------------------------------
Resolution: Done
> Creating of Launcher project in central throws errors
> -----------------------------------------------------
>
> Key: JBIDE-26409
> URL: https://issues.jboss.org/browse/JBIDE-26409
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.9.0.Final
> Environment: Fedora 28
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.10.x
>
>
> I got some errors just after launcher project is created:
> {code}
> Errors occurred during the build.
> Errors running builder 'Maven Project Builder' on project 'Thortnail'.
> Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0
> Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0
> Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0
> Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0
> {code}
> and
> {code}
> eclipse.buildId=12.9.0.GA-v20180928-1629-B3448
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/odockal/workspace1290GA/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.m2e.core
> Error
> Wed Oct 03 08:31:55 CEST 2018
> Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0
> org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:181)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:286)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:244)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:168)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:961)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:76)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:97)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:508)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:288)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:175)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:143)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133)
> at org.jboss.tools.common.launcher.ui.wizard.NewLauncherProjectWizardController.createMavenProject(NewLauncherProjectWizardController.java:135)
> at org.jboss.tools.common.launcher.ui.wizard.NewLauncherProjectWizardController.createProject(NewLauncherProjectWizardController.java:94)
> at org.jboss.tools.common.launcher.ui.wizard.NewLauncherProjectWizardController.run(NewLauncherProjectWizardController.java:63)
> at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:276)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:192)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:253)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 34 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from https://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the update interval of redhat-ea-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from/to redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:422)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:224)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:201)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:261)
> ... 37 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from https://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the update interval of redhat-ea-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from/to redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:240)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:208)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:563)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:481)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:399)
> ... 40 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (JBIDE-26332) regression in org.jboss.ide.eclipse.archives.ui.test.bot: Server ITest fails after move from RD 2.2 to 2.3.Beta
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26332?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26332.
---------------------------------
Resolution: Done
Closing, this is unstable test and that job is no longer used. See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> regression in org.jboss.ide.eclipse.archives.ui.test.bot: Server ITest fails after move from RD 2.2 to 2.3.Beta
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26332
> URL: https://issues.jboss.org/browse/JBIDE-26332
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, server
> Reporter: Nick Boldt
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> With the change from RD 2.2 to 2.3.Beta in the JBT TP (4.9.0.AM3-SNAPSHOT) [1] as part of JBIDE-26180, this integration test is failing:
> {code}
> Regression
> org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest.testModifyingArchiveWithExplorer no-configuration (from org.jboss.ide.eclipse.archives.ui.test.ArchivesAllBotTests)
> Failing for the past 1 build (Since Unstable#452 )
> Took 0.65 sec.
> add description
> Error Message
> Tree Item org.eclipse.reddeer.core.handler.TreeItemHandler@7c5de2fb has no Tree Item with text Project Archives
> Stacktrace
> org.eclipse.reddeer.core.exception.CoreLayerException: Tree Item org.eclipse.reddeer.core.handler.TreeItemHandler@7c5de2fb has no Tree Item with text Project Archives
> at org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest.testModifyingArchiveWithExplorer(ModifyingArchiveTest.java:65)
> Standard Output
> 00:05:13.207 INFO [WorkbenchTestable][RequirementsRunner] Finished test: testDeletingArchiveWithExplorer no-configuration(org.jboss.ide.eclipse.archives.ui.test.bot.DeletingArchiveTest)
> 00:05:13.208 DEBUG [WorkbenchTestable][RunIAfterClassExtensions] Run after class extensions for test class org.jboss.ide.eclipse.archives.ui.test.bot.DeletingArchiveTest
> 00:05:13.208 DEBUG [WorkbenchTestable][RunIAfterClassExtensions] Run method runAfterTestClass() of class org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt
> 00:05:13.208 INFO [WorkbenchTestable][WorkbenchShellHandler] Closing all shells...
> 00:05:13.208 DEBUG [WorkbenchTestable][AbstractWait] Waiting until active shell exists...
> 00:05:13.208 DEBUG [WorkbenchTestable][AbstractWait] Waiting until active shell exists finished successfully
> 00:05:13.208 DEBUG [WorkbenchTestable][RequirementsRunner] Injecting fulfilled requirements into static fields of test class: org.eclipse.reddeer.junit.internal.requirement.Requirements
> 00:05:13.208 DEBUG [WorkbenchTestable][RunIBeforeClassExtensions] Run before class extensions for test class org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest
> 00:05:13.208 DEBUG [WorkbenchTestable][RunIBeforeClassExtensions] Run method runBeforeTestClass() of class org.eclipse.reddeer.junit.extension.before.test.impl.DisableAERI
> 00:05:13.208 INFO [WorkbenchTestable][PreferencesUtil] Setting the aeri reporting to never send.
> 00:05:13.208 DEBUG [WorkbenchTestable][RunIBeforeClassExtensions] Run method runBeforeTestClass() of class org.eclipse.reddeer.junit.extension.before.test.impl.CloseWelcomeScreenExt
> 00:05:13.208 DEBUG [WorkbenchTestable][CloseWelcomeScreenExt] Trying to close Welcome Screen
> 00:05:13.208 DEBUG [WorkbenchTestable][RunIBeforeClassExtensions] Run method runBeforeTestClass() of class org.eclipse.reddeer.junit.extension.before.test.impl.SetOpenAssociatedPerspectiveExt
> 00:05:13.208 DEBUG [WorkbenchTestable][SetOpenAssociatedPerspectiveExt] Setting open associated perspective to: 'never'
> 00:05:13.208 DEBUG [WorkbenchTestable][RunIBeforeClassExtensions] Run method runBeforeTestClass() of class org.eclipse.reddeer.junit.extension.before.test.impl.DoNotDownloadMavenIndexesExt
> ...
> {code}
> See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... for complete log
> [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.9...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months