[JBoss JIRA] (JBIDE-18124) Server adapter: Creating a new server adapter does not use filled name
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18124?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18124:
-------------------------------------
Fix Version/s: 4.3.x
> Server adapter: Creating a new server adapter does not use filled name
> ----------------------------------------------------------------------
>
> Key: JBIDE-18124
> URL: https://issues.jboss.org/browse/JBIDE-18124
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.3.x
>
>
> While creating a new server adapter there is a field in New Server shell for Server's host name and Server name. At least the field Server name should be taken into consideration while creating a server adapter and created server adapter should have be named "filledName at OpenShift [Started]" instead of "applicationName at OpenShift [Started]".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18124) Server adapter: Creating a new server adapter does not use filled name
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18124?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18124:
-------------------------------------
Priority: Minor (was: Major)
> Server adapter: Creating a new server adapter does not use filled name
> ----------------------------------------------------------------------
>
> Key: JBIDE-18124
> URL: https://issues.jboss.org/browse/JBIDE-18124
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
>
> While creating a new server adapter there is a field in New Server shell for Server's host name and Server name. At least the field Server name should be taken into consideration while creating a server adapter and created server adapter should have be named "filledName at OpenShift [Started]" instead of "applicationName at OpenShift [Started]".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-16877) Application wizard: Domain- and gear-combo are too small, selected item is not fully visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16877?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16877:
------------------------------------------
In the screencast that's attached to JBIDE-18100 one can see a combo with the correct height in the 1st wizard page at 0:11 (where one is choosing the connection: the combo with the existing connections is not cropped, it is not too small). Then there 2 combos on the 3rd wizard page at 0:20 (where one can configure the application settings: the domain combo and the gear profile combo) are both too small, cropped.
I compared both layouting codes and both use the following grid data:
{code}
GridDataFactory.fillDefaults()
.align(SWT.FILL, SWT.CENTER).grab(true, false).applyTo(domainViewer.getControl());
{code}
* Connection combo (correct height): https://github.com/adietish/jbosstools-openshift/blob/master/plugins/org....
* Domain combo (too small): https://github.com/adietish/jbosstools-openshift/blob/master/plugins/org....
> Application wizard: Domain- and gear-combo are too small, selected item is not fully visible
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-16877
> URL: https://issues.jboss.org/browse/JBIDE-16877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) GTK3
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
> Labels: application_wizard, gtk3, upstream
> Fix For: 4.2.0.CR1
>
> Attachments: OpenShift_newpg2.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> The default wizard window size obscures fields, Domain and Gear profile.
> Work around: If I click Advanced then Embedded Cartridges pane shrinks vertically and the whole of the Domain and Gear profile fields can be seen.
> Is there a way to ensure the whole of the Domain and Gear profile fields can be seen in the default view? Perhaps by reducing the size of the Embedded Cartridges pane?
> !OpenShift_newpg2.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18124) Server adapter: Creating a new server adapter does not use filled name
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-18124:
-------------------------------------
Summary: Server adapter: Creating a new server adapter does not use filled name
Key: JBIDE-18124
URL: https://issues.jboss.org/browse/JBIDE-18124
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.CR1
Reporter: Marián Labuda
While creating a new server adapter there is a field in New Server shell for Server's host name and Server name. At least the field Server name should be taken into consideration while creating a server adapter and created server adapter should have be named "filledName at OpenShift [Started]" instead of "applicationName at OpenShift [Started]".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18123) Embed wizard: Deselecting embeddable cartridge does not trigger "possible data loss" dialog
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-18123:
-------------------------------------
Summary: Embed wizard: Deselecting embeddable cartridge does not trigger "possible data loss" dialog
Key: JBIDE-18123
URL: https://issues.jboss.org/browse/JBIDE-18123
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.CR1
Reporter: Marián Labuda
In JBIDE-13961 we implemented showing a dialog informing about possible data loss after removing an embeddable cartridge. Nowadays this dialog is not shown anymore after unselecting embedded cartridge in Edit Embedded Cartridges shell (opened via context menu of an application).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18095:
---------------------------------------------
[~AxelW] are you saying that this worked in Kepler or that it was broken there too ?
And what do you mean closing the projects fixes it ?
any chance you can attach a simple project to reproduce it ?
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months