[JBoss JIRA] (JBIDE-11298) Git clone destination folder is not validated
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-11298:
----------------------------------------
Summary: Git clone destination folder is not validated
Key: JBIDE-11298
URL: https://issues.jboss.org/browse/JBIDE-11298
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Lucia Jelinkova
Fix For: 3.3.0.Beta1
# ASSERT: make sure you have a folder in <home>/git/<project name> (ex. former clone, empty folder, etc.) ex. have a folder <home>/git/*as*
# EXEC: launch the OpenShift Express Application wizard
# EXEC: log in and choose a new name <project name> & type (no embedded cartridges needed) ex. "*as*" as name
# EXEC: on the project page: choose *Create new*
Result:
*Finish" is enabled even though the checkout will not be possible: You already have a folder with the same name as the clone.
!finish-enabled.png!
The clone would have to remove that one or cancel, warning about it.
The wizard with the clone settings has no warning/error telling you that the clone destination is not valid.
!missing-error.png!
Expected result:
*Finish* must be disabled as long as the git clone destination is invalid (already a file/folder present). The clone settings page must decorate the *Location* input.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11148) ConcurrentModificationException when creating new application
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-11148:
---------------------------------------
Summary: ConcurrentModificationException when creating new application
Key: JBIDE-11148
URL: https://issues.jboss.org/browse/JBIDE-11148
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Environment: JBDS Beta1c
Reporter: Lucia Jelinkova
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
When I create a new application an error messagee window appears with ConcurrentModificationException.
Error log:
{code}
Errors running builder 'JAX-RS Builder' on project 'ssshh'.
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$EntryIterator.next(HashMap.java:834)
at java.util.HashMap$EntryIterator.next(HashMap.java:832)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.unindexElement(JaxrsMetamodel.java:239)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.indexElement(JaxrsMetamodel.java:177)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.add(JaxrsMetamodel.java:158)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.postProcessHttpMethod(ResourceChangedProcessor.java:479)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processHttpMethodChangesOnScopeAdditionOrChange(ResourceChangedProcessor.java:387)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEvent(ResourceChangedProcessor.java:176)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEntireProject(ResourceChangedProcessor.java:108)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processAffectedResources(ResourceChangedProcessor.java:83)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:123)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:83)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-10938) tooltips fail in wizard examples
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-10938:
-------------------------------------------
Summary: tooltips fail in wizard examples
Key: JBIDE-10938
URL: https://issues.jboss.org/browse/JBIDE-10938
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.Beta1-soa
http://screencast.com/t/ggT7HZrV
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.SWT.error(SWT.java:4168)
at org.eclipse.swt.widgets.Widget.error(Widget.java:774)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:568)
at org.eclipse.swt.widgets.Control.getShell(Control.java:1903)
at org.eclipse.jface.window.ToolTip.toolTipHide(ToolTip.java:449)
at org.eclipse.jface.window.ToolTip.access$1(ToolTip.java:447)
at org.eclipse.jface.window.ToolTip$TooltipHideListener.handleEvent(ToolTip.java:676)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
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:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBIDE-9726) inconsistent licensing terms across JBoss Tools - SOA Tooling site
by Nick Boldt (JIRA)
inconsistent licensing terms across JBoss Tools - SOA Tooling site
------------------------------------------------------------------
Key: JBIDE-9726
URL: https://issues.jboss.org/browse/JBIDE-9726
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools, pi4soa, Savara, teiid, updatesite
Affects Versions: 3.3.0.M3
Reporter: Nick Boldt
Assignee: Kris Verlaenen
Fix For: 3.3.0.M4
Attachments: inconsistent-license-details.png
Most features in JBoss Tools have a license from Red Hat which mentions EPL, GPL, and other licenses. It's a catch-all which allows a cleaner view of what's being installed.
!inconsistent-license-details.png!
The following features should adopt this statement in their features so that we're consistent across the board:
Savara (GPL)
Drools (ASL)
pi4soa (ASL)
Teiid (EPL)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months