[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15485:
-------------------------------------
Priority: Minor (was: Major)
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.Alpha1
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 6 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15485:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: openshift-java-client
> Fix For: 4.2.x
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 6 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15485:
-------------------------------------
Labels: openshift-java-client (was: )
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: openshift-java-client
> Fix For: 4.2.0.Alpha1
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 6 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15485:
------------------------------------------
I mailed Dan Mace about removing the above but I had no answer yet. Will have to ping him up.
Postponing this non-critical issue.
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 6 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15485:
-------------------------------------
Issue Type: Enhancement (was: Bug)
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 6 months
[JBoss JIRA] (JBIDE-15523) Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15523?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-15523.
--------------------------------------
Resolution: Done
client was fixed in JBIDE-15525 and deployed to maven central. All done.
> Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15523
> URL: https://issues.jboss.org/browse/JBIDE-15523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
> Attachments: embeddable-carts-with-descriptions.png, embedded-cartridges-lables-fixed.png
>
>
> With the update to the latest OpenShift client (?) the OpenShift application / import wizard displays the embeddable (add-on) cartridges with their (very verbose) description where they should get shown with their display name:
> !embeddable-carts-with-descriptions.png!
> In consequence it's very awkward for some cartridges to know what cartridge is listed (not all embeddable cartridges start with their name in the description).
> Standalone (Web-) cartridges are not affected.
--
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, 6 months
[JBoss JIRA] (JBIDE-15523) Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15523?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15523:
------------------------------------------
with the new client (created with the fix in JBIDE-15525, deployed to maven central), the Eclipse Tooling build picks it up automatically and doesnt show the issue any more:
!embedded-cartridges-lables-fixed.png!
> Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15523
> URL: https://issues.jboss.org/browse/JBIDE-15523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
> Attachments: embeddable-carts-with-descriptions.png, embedded-cartridges-lables-fixed.png
>
>
> With the update to the latest OpenShift client (?) the OpenShift application / import wizard displays the embeddable (add-on) cartridges with their (very verbose) description where they should get shown with their display name:
> !embeddable-carts-with-descriptions.png!
> In consequence it's very awkward for some cartridges to know what cartridge is listed (not all embeddable cartridges start with their name in the description).
> Standalone (Web-) cartridges are not affected.
--
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, 6 months