[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by James Cobb (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
James Cobb commented on JBIDE-22382:
------------------------------------
[~fbricon] [~crobson] - I agree that the branding of "Red Hat Central" should reflect the RHD brand. The current background graphics used are from the website branding of jboss.org. Can I please request a full screenshot of the IDE with all of the content for that panel visible?
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: respin-a
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-654:
----------------------------------
Yes. - thanks Max.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-22807:
----------------------------------
Steps to Reproduce:
Machydra job for example: machydra job: jbds10-nightly.freemarker.ui.test.
Otherwise: run integration tests with maven commands in command line and pass parameter test.installBase=existing/devstudio/path
was:for example: machydra job: jbds10-nightly.freemarker.ui.test.
> Could not install bundle. A bundle is already installed with the name xxx
> -------------------------------------------------------------------------
>
> Key: JBIDE-22807
> URL: https://issues.jboss.org/browse/JBIDE-22807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Environment: Fedora 24, x86_64
> devstudio:
> Version: 10.0.1.AM2
> Build id: AM2-v20160720-1632-B5674
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> Reporter: Ondrej Dockal
> Priority: Critical
> Fix For: 4.4.1.AM2
>
>
> Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio)
> Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message).
> This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-22807:
----------------------------------
Fix Version/s: 4.4.1.AM2
> Could not install bundle. A bundle is already installed with the name xxx
> -------------------------------------------------------------------------
>
> Key: JBIDE-22807
> URL: https://issues.jboss.org/browse/JBIDE-22807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Environment: Fedora 24, x86_64
> devstudio:
> Version: 10.0.1.AM2
> Build id: AM2-v20160720-1632-B5674
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> Reporter: Ondrej Dockal
> Priority: Critical
> Fix For: 4.4.1.AM2
>
>
> Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio)
> Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message).
> This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22846) Incorrectly referenced artifact are not validated/reported in Source tab in batch editor.
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22846?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-22846.
---------------------------------
Fix Version/s: 4.4.1.AM2
Resolution: Cannot Reproduce
I could not reproduce this bug anymore, closing.
> Incorrectly referenced artifact are not validated/reported in Source tab in batch editor.
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22846
> URL: https://issues.jboss.org/browse/JBIDE-22846
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.4.1.AM2
> Environment: Fedora 24, x86_64,
> devstudio:
> Version: 10.0.1.AM2
> Build id: AM2-v20160725-1821-B5680
> Build date: 20160725-1821
> Reporter: Ondrej Dockal
> Priority: Critical
> Fix For: 4.4.1.AM2
>
> Attachments: BatchNoValidationSourceTab.png
>
>
> There is no validation of attributes ref or class in source tab of the batch editor. In design and diagram source is seems alright. Also validation of other attributes that reference another artifact are not working. On the other hand, validation of uniqueness of id is working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22382:
-------------------------------------
[~crobson] the icon used in the attached screenshot was reverted to the shadowman when [~james.cobb] pointed out we couldn't use that branding in a product, right before the JBDS 10 release. So this is what we currently have:
!http://content.screencast.com/users/fbricon/folders/Jing/media/0eaad79e-b968-48a4-8da8-9ce3baf52d26/00000446.png|width=650!
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: respin-a
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-21766) NPE when trying to generate mapping files on project with no console config
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21766?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-21766.
-------------------------------
Resolution: Done
> NPE when trying to generate mapping files on project with no console config
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21766
> URL: https://issues.jboss.org/browse/JBIDE-21766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Fix For: 4.4.1.AM3
>
>
> {code}
> java.lang.NullPointerException
> at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.getService(ConfigurationActor.java:127)
> at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfiguration(ConfigurationActor.java:134)
> at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfigurations(ConfigurationActor.java:117)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.createConfigurations(NewHibernateMappingFileWizard.java:559)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.getPlaces2Gen(NewHibernateMappingFileWizard.java:316)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.handlePageChanging(NewHibernateMappingFileWizard.java:172)
> at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1554)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1551)
> at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:899)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1186)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3627:
-------------------------------------------
Note - this issue is not about JBDS, this is about developer suite installer.
I don't know the status of devstudio [~rob.stryker] can you give an update ?
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Catherine Robson commented on JBIDE-22382:
------------------------------------------
[~james.cobb] Can you take a look at this? There's a screenshot of how the developers icon is being used for Red Hat Central. Red Hat Central is a "landing page" for our version of Eclipse that gives developers news, access to quickstarts and other project starters, etc. My thought is we have two options:
# Move this towards Red Hat Developers branding with name & with wording - see if we can associate it with the program completely since the content is the same content that we have on the site, and we're trying to drive Developers towards the site then with this mechanism as a entrypoint into what we have to offer Red Hat Developers. My preference is here.
# Remove the Developers branding and move back to Shadowman, and keep it generic to Red Hat.
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: respin-a
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months