[JBoss JIRA] (TOOLSDOC-424) Hybrid Mobile + CordovaSim 7.1 chapter - add screen capture
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-424:
----------------------------------------
Summary: Hybrid Mobile + CordovaSim 7.1 chapter - add screen capture
Key: TOOLSDOC-424
URL: https://issues.jboss.org/browse/TOOLSDOC-424
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: User Guide - Hybrid Mobile Tools
Affects Versions: 4.1.1
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.1.1
Add screen captures to documents once UI changing JIRAs resolved for 7.1.0.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15887) Application wizard: typing application name is delayed, sluggish, poor responsiveness
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15887?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15887 at 11/7/13 12:44 PM:
--------------------------------------------------------------------
I have no clue what is causing this. I tried with a fresh Eclipse IDE and it didnt help. Connecting jvisualvm did not unveil anything suspicious but major activity of org.eclipse.core.internal.databinding.beans.BeanPropertyHelper#readProperty right after native GTK (most likely key events)
!visual-vm.png!
I noticed that when you change the name of the application you trigger 3 MultiValidators:
- ApplicationConfigurationWizardPage#NewApplicationNameValidator
- ProjectAndServerAdapterSettingsWizardPage#UseExistingOpenProjectValidator
- GitCloningSettingsWizardPage#RepoPathValidationStatusProvider
This is required since the application name is the name of the new workspace project that the application will get imported into (thus needs to be validated aka made sure no such proj exists). And the application name is also used for the folder that the application is cloned into (and thus needs to get validated, too).
The lagging improves a lot as soon as I comment some validators (just the body, not the creation).
was (Author: adietish):
I have no clue what is causing this. I tried with a fresh Eclipse IDE and it didnt help. Connecting jvisualvm did not unveils major activity of org.eclipse.core.internal.databinding.beans.BeanPropertyHelper#readProperty right after native GTK (most likely key events)
!visual-vm.png!
I noticed that when you change the name of the application you trigger 3 MultiValidators:
- ApplicationConfigurationWizardPage#NewApplicationNameValidator
- ProjectAndServerAdapterSettingsWizardPage#UseExistingOpenProjectValidator
- GitCloningSettingsWizardPage#RepoPathValidationStatusProvider
This is required since the application name is the name of the new workspace project that the application will get imported into (thus needs to be validated aka made sure no such proj exists). And the application name is also used for the folder that the application is cloned into (and thus needs to get validated, too).
The lagging improves a lot as soon as I comment some validators (just the body, not the creation).
> Application wizard: typing application name is delayed, sluggish, poor responsiveness
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-15887
> URL: https://issues.jboss.org/browse/JBIDE-15887
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: openshift-jbds7-ga.ogv, openshift-jbds71Beta1b.ogv, openshift.ogv, visual-vm.png
>
>
> If you launch the Application wizard to create a new application you get the first wizard page where you should provide a name for your new application. Typing into this text-field is very slow, the inputs make it to the widget in a very delayed manner.
--
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
12 years, 5 months
[JBoss JIRA] (TOOLSDOC-401) Write Customize Maven Tools section
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-401?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-401:
-------------------------------------
Fix Version/s: 4.2.0
(was: 4.1.1)
> Write Customize Maven Tools section
> -----------------------------------
>
> Key: TOOLSDOC-401
> URL: https://issues.jboss.org/browse/TOOLSDOC-401
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0
>
> Original Estimate: 1 day, 2 hours
> Remaining Estimate: 1 day, 2 hours
>
> Section 3. Customize Maven Tools
> 3.1 Customizing Overview
> 3.x Enable Configurators
> 3.x Specify Maven Profiles (Configure Maven repository access)
> 3.x Automatically Add JBoss Maven Source Container
> 3.x Source Lookup Behavior
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15900) NPE in CSS Editor on jquery css
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15900?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15900:
-----------------------------------
Fix Version/s: 4.2.x
> NPE in CSS Editor on jquery css
> --------------------------------
>
> Key: JBIDE-15900
> URL: https://issues.jboss.org/browse/JBIDE-15900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.1.Beta1
> Reporter: Vlado Pakan
> Fix For: 4.2.x
>
>
> While testing JBIDE-14849 I found the following:
> Using jquery.mobile-1.3.2.css I'm getting this error when opening CSS dialog for first time:
> Unhandled event loop exception
> java.lang.NullPointerException
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocumentRegion.getFullText(BasicStructuredDocumentRegion.java:151)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.getCollapsedText(CSSDeclarationItemParser.java:1092)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.makeString(CSSDeclarationItemParser.java:873)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.createStringValue(CSSDeclarationItemParser.java:539)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.createPrimitiveValue(CSSDeclarationItemParser.java:392)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:1021)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:969)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueTextCore(CSSStyleDeclItemImpl.java:260)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueText(CSSStyleDeclItemImpl.java:234)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclarationImpl.setProperty(CSSStyleDeclarationImpl.java:267)
> at org.jboss.tools.jst.css.dialog.common.CSSModel.updateCSSStyle(CSSModel.java:297)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.handleSelectorSwitched(CSSClassDialog.java:250)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog$1.modifyText(CSSClassDialog.java:152)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Combo.select(Combo.java:1738)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.updateControlPane(CSSClassDialog.java:377)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.createContents(CSSClassDialog.java:99)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> When opening CSS dialog next times there are empty messages with no message and no stack trace in Error Log and no style class available to select within opened CSS dialog. Plugin name displayed in error log is org.jboss.tools.jst,css
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15900) NPE in CSS Editor on jquery css
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15900?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-15900:
--------------------------------------
Assignee: Daniel Azarov
> NPE in CSS Editor on jquery css
> --------------------------------
>
> Key: JBIDE-15900
> URL: https://issues.jboss.org/browse/JBIDE-15900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.1.Beta1
> Reporter: Vlado Pakan
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
>
> While testing JBIDE-14849 I found the following:
> Using jquery.mobile-1.3.2.css I'm getting this error when opening CSS dialog for first time:
> Unhandled event loop exception
> java.lang.NullPointerException
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocumentRegion.getFullText(BasicStructuredDocumentRegion.java:151)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.getCollapsedText(CSSDeclarationItemParser.java:1092)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.makeString(CSSDeclarationItemParser.java:873)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.createStringValue(CSSDeclarationItemParser.java:539)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.createPrimitiveValue(CSSDeclarationItemParser.java:392)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:1021)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:969)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueTextCore(CSSStyleDeclItemImpl.java:260)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueText(CSSStyleDeclItemImpl.java:234)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclarationImpl.setProperty(CSSStyleDeclarationImpl.java:267)
> at org.jboss.tools.jst.css.dialog.common.CSSModel.updateCSSStyle(CSSModel.java:297)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.handleSelectorSwitched(CSSClassDialog.java:250)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog$1.modifyText(CSSClassDialog.java:152)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Combo.select(Combo.java:1738)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.updateControlPane(CSSClassDialog.java:377)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.createContents(CSSClassDialog.java:99)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> When opening CSS dialog next times there are empty messages with no message and no stack trace in Error Log and no style class available to select within opened CSS dialog. Plugin name displayed in error log is org.jboss.tools.jst,css
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15868) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15868?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15868:
---------------------------------------
I can reproduce the issue locally in PDE.
A change in WTP 3.5.1 is the cause of the test failure.
The issue happens because the seam/validation project contains the .settings directory what makes m2e-wtp/wtp confused.
The PR fixes the issue by removing the seam/validation/.settings directory.
I will also create a bug against WTP.
> 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
> ----------------------------------------------------------
>
> Key: JBIDE-15868
> URL: https://issues.jboss.org/browse/JBIDE-15868
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: testfailure
>
> *1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> # [org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest|https://je...] (failing for 18 builds)
> [Search for Test Failure JIRAs in JBIDE 4.1.1.Beta1 for maven component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest : testJBIDE11570_constraintViolations{color} (failing for 18 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-central_41/103/testReport/org.jboss.tools.maven.configurators.tests/SeamConfiguratorTest/testJBIDE11570_constraintViolations}
> <case>
> <age>18</age>
> <className>org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest</className>
> <duration>1.229</duration>
> <errorStackTrace>java.lang.NullPointerException
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePaths(VirtualResource.java:119)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingFiles(VirtualFile.java:104)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingResources(VirtualFile.java:93)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.exists(VirtualResource.java:88)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getNonBinaryComponentManifest(ManifestUtilities.java:124)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifest(ManifestUtilities.java:81)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifestClasspath(ManifestUtilities.java:147)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getManifestClasspath(J2EEModuleVirtualComponent.java:248)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:368)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207)
> at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386)
> at org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:107)
> at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:746)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:865)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:289)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:216)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:326)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:324)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:299)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:286)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:273)
> at org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest.testJBIDE11570_constraintViolations(SeamConfiguratorTest.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72)
> at java.lang.Thread.run(Thread.java:662)
> </errorStackTrace>
> <failedSince>86</failedSince>
> <name>testJBIDE11570_constraintViolations</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>TEST-SETUP: testJBIDE11570_constraintViolations
> Restoring user settings file: /home/hudson/.m2/settings.xml
> </stdout>
> </case>
> {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
12 years, 5 months