[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21761:
----------------------------------
Sprint: devex #3 February 2016, devex #4 March 2016 (was: devex #3 February 2016)
> Port mapping validation is not correct
> --------------------------------------
>
> Key: JBIDE-21761
> URL: https://issues.jboss.org/browse/JBIDE-21761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: validation_msg.png
>
>
> In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image.
> !validation_msg.png!
> There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3566:
------------------------------------
> It does not do a system level popup afaik.
FWIW, it uses Mylyn notifications.
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, aeri-not-firing.png, aeri-popup.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3566 at 3/16/16 8:03 PM:
-----------------------------------------------------------
OK, figured out what the problem is on my system.
AERI doesn't trigger a dialog IN Eclipse. It triggers an -OS-level- swt/gtk3 alert. So... OOTB, nothing happens on my system until I do this:
{code}
export SWT_GTK3=0
{code}
Then the dialog appears exactly as described.
Steps to repro:
1. install JBDS, launch from installer
2. Help > Install new > http://download.eclipse.org/technology/epp/logging/milestones > EPP Logging Manual Tests Feature > shut down JBDS
3. export SWT_GTK3=0
4. launch JBDS
5. from the Log Error dropdown in the coolbar, select Trigger JBoss Error
[^aeri-popup.png]
---
Verified dialog appears with these versions:
* jboss-devstudio-9.1.0.CR1-v20160311-1249-B402-installer-standalone.jar
* jboss-devstudio-10.0.0.Alpha1-v20160316-1022-B4975-installer-standalone.jar
And was able to submit a report here:
https://redhat.ctrlflow.com/community/#/incidents/Nr5PUidTzbV6S4QqAp2akuI...
was (Author: nickboldt):
OK, figured out what the problem is on my system.
AERI doesn't trigger a dialog IN Eclipse. It triggers an OS-level alert. So... OOTB, nothing happens on my system until I do this:
{code}
export SWT_GTK3=0
{code}
Then the dialog appears exactly as described.
Steps to repro:
1. install JBDS, launch from installer
2. Help > Install new > http://download.eclipse.org/technology/epp/logging/milestones > EPP Logging Manual Tests Feature > shut down JBDS
3. export SWT_GTK3=0
4. launch JBDS
5. from the Log Error dropdown in the coolbar, select Trigger JBoss Error
[^aeri-popup.png]
---
Verified dialog appears with these versions:
* jboss-devstudio-9.1.0.CR1-v20160311-1249-B402-installer-standalone.jar
* jboss-devstudio-10.0.0.Alpha1-v20160316-1022-B4975-installer-standalone.jar
And was able to submit a report here:
https://redhat.ctrlflow.com/community/#/incidents/Nr5PUidTzbV6S4QqAp2akuI...
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, aeri-not-firing.png, aeri-popup.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-3566.
---------------------------------------
Resolution: Done
okey, so gtk3 issue. please upgrade to supported fedora version :)
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, aeri-not-firing.png, aeri-popup.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3566 at 3/16/16 8:01 PM:
-----------------------------------------------------------
It triggers what looks like an SWT dialog that appears to live outside Eclipse, rather than a modal dialog inside Eclipse. So no, it's not OS-level but it's IMPACTED by OS-level installation of swt or gtk3 dependencies, unlike most of the rest of Eclipse.
Interestingly, JBDS 10 is missing most of the toolbars OOTB on Fedora20, whereas JBDS 9 looks like it ought to. The missing toolbars appear with ` export SWT_GTK3=0` too.
On my system (Fedora 20) I need to use export SWT_GTK3=0 to make this work.
{code}Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
And I have these installed:
webkitgtk3-2.2.8-3.fc20.x86_64
gtk3-3.10.9-2.fc20.x86_64 {code}
was (Author: nickboldt):
It triggers what looks like an SWT dialog that appears to live outside Eclipse, rather than a modal dialog inside Eclipse. So no, it's not OS-level but it's IMPACTED by OS-level installation of swt or gtk3 dependencies, unlike most of the rest of Eclipse.
Interestingly, JBDS 10 is missing most of the toolbars OOTB on Fedora20, whereas JBDS 9 looks like it ought to. The missing toolbars appear with ` export SWT_GTK3=0` too.
On my system (Fedora 20) I need to use export SWT_GTK3=0 to make this work.
{code}Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux{code}
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, aeri-not-firing.png, aeri-popup.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3566:
----------------------------------
It triggers what looks like an SWT dialog that appears to live outside Eclipse, rather than a modal dialog inside Eclipse. So no, it's not OS-level but it's IMPACTED by OS-level installation of swt or gtk3 dependencies, unlike most of the rest of Eclipse.
Interestingly, JBDS 10 is missing most of the toolbars OOTB on Fedora20, whereas JBDS 9 looks like it ought to. The missing toolbars appear with ` export SWT_GTK3=0` too.
On my system (Fedora 20) I need to use export SWT_GTK3=0 to make this work.
{code}Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux{code}
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, aeri-not-firing.png, aeri-popup.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21662:
-------------------------------------
Sorry if I wasn't clear. Not merged yet, still under review and extensive testing as we speak.
> Server adapter: workspace project is not automatically published if there was no initial publish
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21662
> URL: https://issues.jboss.org/browse/JBIDE-21662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years