[JBoss JIRA] (JBIDE-15772) Remove referenced juno sites in integration-tests site pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15772?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15772 at 11/20/13 1:24 PM:
--------------------------------------------------------------
Now the only remaining concern is that when you publish your site, it will reference nightly and staging sites that may cease to exist later.
Therefore, you should update your root pom [1] to point at released, stable URLs when you're ready to build and release a *.Final* version of this site. /staging/ and /nightly/ are subject to disappear or change w/o notice.
[1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
Also, I screwed up the indents here:
https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si...
:(
was (Author: nickboldt):
Now the only remaining concern is that when you publish your site, it will reference nightly and staging sites that may cease to exist later.
Therefore, you should update your root pom [1] to point at released, stable URLs when you're ready to build and release a *.Final* version of this site. /staging/ and /nightly/ are subject to disappear or change w/o notice.
[1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
> Remove referenced juno sites in integration-tests site pom
> ----------------------------------------------------------
>
> Key: JBIDE-15772
> URL: https://issues.jboss.org/browse/JBIDE-15772
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: qa
> Affects Versions: 4.1.1.Beta1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.1.1.CR1
>
>
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si...
> {code}
> <associateSite>http://download.jboss.org/jbosstools/updates/juno/soa-tooling/</associateSite>
> <associateSite>http://download.jboss.org/jbosstools/updates/juno/</associateSite>
> <associateSite>http://download.jboss.org/jbosstools/updates/stable/juno/</associateSite>
> <associateSite>http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/</associateSite>
> {code}
> These are added when you add the integration-tests update site to Eclipse to resolve dependencies.
> We most probably don't need them. Or if we do, we should update to kepler links.
--
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] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2821:
-----------------------------
Attachment: tooltip-tech-preview.png
Here's the tooltip I added for the new Technology Preview connector certification:
!tooltip-tech-preview.png!
Note that for some reason, JBDS on my system (Fedora 18, running xfce) sometimes truncates the ends of JBoss Central connectors, so as you can see in the screenshot, SOME of the certifications are shown, some are truncated, and some are missing. I've reported this to [~snjeza] but she can't reproduce it.
> Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
> -----------------------------------------------------------------------------------
>
> Key: JBDS-2821
> URL: https://issues.jboss.org/browse/JBDS-2821
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 7.1.0.CR1
>
> Attachments: Central_updates_exp.png, JBDS_Cordo_VJET.png, JBDS_installing_incubating_experimental_techprev.png, JBT_Arq_exper.png, JBT_Cordo_techprev.png, JBT_installing_incubating_experimental_techprev.png, JBT_VJET_exper.png, tooltip-tech-preview.png
>
>
> In JBoss Central, software/updates tab, Hybrid Mobile is labelled as
> 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*"
> 2. "by JBoss by ..., *Experimental*"
> I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better.
> !Central_updates_exp.png!
--
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] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2821:
-----------------------------
Attachment: JBDS_installing_incubating_experimental_techprev.png
JBDS_Cordo_VJET.png
JBT_installing_incubating_experimental_techprev.png
JBT_Cordo_techprev.png
JBT_Arq_exper.png
JBT_VJET_exper.png
Here's what users will see when the above PRs are applied:
*JBDS*
!JBDS_Cordo_VJET.png!
!JBDS_installing_incubating_experimental_techprev.png!
*JBoss Tools*
!JBT_Arq_exper.png!
!JBT_Cordo_techprev.png!
!JBT_VJET_exper.png!
!JBT_installing_incubating_experimental_techprev.png!
> Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
> -----------------------------------------------------------------------------------
>
> Key: JBDS-2821
> URL: https://issues.jboss.org/browse/JBDS-2821
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 7.1.0.CR1
>
> Attachments: Central_updates_exp.png, JBDS_Cordo_VJET.png, JBDS_installing_incubating_experimental_techprev.png, JBT_Arq_exper.png, JBT_Cordo_techprev.png, JBT_installing_incubating_experimental_techprev.png, JBT_VJET_exper.png
>
>
> In JBoss Central, software/updates tab, Hybrid Mobile is labelled as
> 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*"
> 2. "by JBoss by ..., *Experimental*"
> I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better.
> !Central_updates_exp.png!
--
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-15878) Visual Page Editor conflicts with mobile palette because of sqllite incompatibility
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15878?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15878:
----------------------------------------
[~vpakan], It actually depends on the particular environment. Not only on OS. The best way to verify this fix is installing JBDS 7.0 and make sure it fails there. Then you can verify it on JBDS 7.1.0.CR1 to make sure it works fine.
> Visual Page Editor conflicts with mobile palette because of sqllite incompatibility
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-15878
> URL: https://issues.jboss.org/browse/JBIDE-15878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.1.Beta1
> Environment: Linux (since osx and windows allows codesharing)
> Reporter: Max Rydahl Andersen
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: tablewizardfedora18.png
>
>
> We've found that like JBIDE-9144 we still have a problem mixing webkit and xulrunner.
> Test to see if it fails:
> 1 Run Linux (version from JBIDE-9144)
> 2 Create a html5 page
> {code}
> <!DOCTYPE html>
> <html>
> <head>
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.css" />
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> </head>
> <body>
> <h1>HTML 5</h1>
> </body>
> </html>
> {code}
> 3 Use a fresh workspace
> 4 Open Preferences , Ensure "Source" is set as default active editor tab for "Visual Page Editor"
> 5. Open html5 page (DO NOT OPEN VISUAL/PREVIEW TABS IN VPE!)
> 6 Open Palette, see JQueryMobile drag "Table" to the page - see preview working
> 7. Switch to Visual/Source (visual part should be enabled)
> 8. Drag another "table" to the page
> Take screenshot showing dialog with Table at the same time as VPE shows preview of html5
> 9. write down linux versoin, Java version (32/64 bit)
>
--
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-14597) ng-app AngularJS
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14597?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-14597:
----------------------------------------
Let's just ignore ng-* attributes.
> ng-app AngularJS
> ----------------
>
> Key: JBIDE-14597
> URL: https://issues.jboss.org/browse/JBIDE-14597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Reporter: Burr Sutter
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.x
>
> Attachments: 2013-05-23_0752.png, 2013-05-23_1548.png, html5_demo.fsh, Screen Shot 2013-05-23 at 3.51.53 PM.png
>
>
> Warning:
> Undefined attribute name (ng-app).
> Undefined attribute name (ng-controller).
> AngularJS is part of the new HTML5 Scaffolding feature in Forge 1.3
> forge install-plugin angularjs
--
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-15505) exception in jaxrs at startup
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15505?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-15505:
---------------------------------------
Not sure how to reproduce the problem, the fix is about avoid the NPE given the stacktrace, but I suspect it happens in a kind of race-condition, where the metamodel has already been removed. Maybe when closing the project ?
> exception in jaxrs at startup
> -----------------------------
>
> Key: JBIDE-15505
> URL: https://issues.jboss.org/browse/JBIDE-15505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> Not sure how I got the error, but I just restarted a workspace after deleting some projects in previous session.
> At startup I got this error:
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.dispose(UriMappingsContentProvider.java:116)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider$1.run(SafeDelegateTreeContentProvider.java:76)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.dispose(SafeDelegateTreeContentProvider.java:74)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension$3.run(NavigatorContentExtension.java:210)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.dispose(NavigatorContentExtension.java:207)
> at org.eclipse.ui.internal.navigator.NavigatorContentService.dispose(NavigatorContentService.java:355)
> at org.eclipse.ui.navigator.CommonViewer.dispose(CommonViewer.java:251)
> at org.eclipse.ui.navigator.CommonViewer.handleDispose(CommonViewer.java:239)
> at org.eclipse.jface.viewers.ContentViewer$2.widgetDisposed(ContentViewer.java:214)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1308)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.disposeWidget(SWTPartRenderer.java:152)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.disposeWidget(ContributedPartRenderer.java:273)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.disposeWidget(ElementReferenceRenderer.java:109)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1598)
> at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:1231)
> at org.eclipse.ui.internal.WorkbenchWindow.access$14(WorkbenchWindow.java:1198)
> at org.eclipse.ui.internal.WorkbenchWindow$10.run(WorkbenchWindow.java:1261)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1259)
> at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:1096)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1079)
> at org.eclipse.ui.internal.Workbench.access$19(Workbench.java:1024)
> at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1327)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1325)
> at org.eclipse.ui.internal.Workbench.restart(Workbench.java:2480)
> at org.eclipse.ui.internal.handlers.RestartWorkbenchHandler.execute(RestartWorkbenchHandler.java:31)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> 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)
--
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] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2821:
-----------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
> -----------------------------------------------------------------------------------
>
> Key: JBDS-2821
> URL: https://issues.jboss.org/browse/JBDS-2821
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 7.1.0.CR1
>
> Attachments: Central_updates_exp.png
>
>
> In JBoss Central, software/updates tab, Hybrid Mobile is labelled as
> 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*"
> 2. "by JBoss by ..., *Experimental*"
> I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better.
> !Central_updates_exp.png!
--
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] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2821:
-----------------------------
CDW qa_ack: + (was: ?)
> Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill
> -----------------------------------------------------------------------------------
>
> Key: JBDS-2821
> URL: https://issues.jboss.org/browse/JBDS-2821
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 7.1.0.CR1
>
> Attachments: Central_updates_exp.png
>
>
> In JBoss Central, software/updates tab, Hybrid Mobile is labelled as
> 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*"
> 2. "by JBoss by ..., *Experimental*"
> I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better.
> !Central_updates_exp.png!
--
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