[JBoss JIRA] (JBIDE-12638) externalize strings
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12638?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-12638:
----------------------------------
Comment: was deleted
(was: Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.)
> externalize strings
> -------------------
>
> Key: JBIDE-12638
> URL: https://issues.jboss.org/browse/JBIDE-12638
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Alpha1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: cleanup
> Fix For: LATER
>
>
> Messages and other texts are currently still embedded in the code. We should externalize them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12571) Connection wizard: Eclipse preferences: allow users to define a default server
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12571?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-12571 at 6/18/15 9:23 AM:
----------------------------------------------------------------
Reopening. This is relevant also for v3.
was (Author: mlabuda):
Reopening. This can be relevant also for v3 once there is gonna be default server.
> Connection wizard: Eclipse preferences: allow users to define a default server
> ------------------------------------------------------------------------------
>
> Key: JBIDE-12571
> URL: https://issues.jboss.org/browse/JBIDE-12571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Labels: connection_wizard, new_and_noteworthy
> Fix For: LATER
>
> Attachments: 2012-09-10 13.10.bmml, 2012-09-10 13.10.bmml, 2012-09-10 13.10.png
>
>
> Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled, prefilled with the server that is present in the (rhc cli-tooling) openshift configuration. Once unchecked the user can enter a default server and override the openshift server that is configured in the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12571) Connection wizard: Eclipse preferences: allow users to define a default server
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12571?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-12571:
----------------------------------
Comment: was deleted
(was: Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.)
> Connection wizard: Eclipse preferences: allow users to define a default server
> ------------------------------------------------------------------------------
>
> Key: JBIDE-12571
> URL: https://issues.jboss.org/browse/JBIDE-12571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Labels: connection_wizard, new_and_noteworthy
> Fix For: LATER
>
> Attachments: 2012-09-10 13.10.bmml, 2012-09-10 13.10.bmml, 2012-09-10 13.10.png
>
>
> Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled, prefilled with the server that is present in the (rhc cli-tooling) openshift configuration. Once unchecked the user can enter a default server and override the openshift server that is configured in the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18772:
------------------------------------
{quote}3. People in our team wanted to remove mars or luna from the update site url, so now it's this:
http://download.jboss.org/jbosstools/snapshots/builds/RedDeer_master/{quote}
But now you're inconsistently publishing to a URL and no one will know for which version of Eclipse you're targeting.
I've pinged numerous times about all the refctoring/restructuring in JBDS-3208, and there was no objection from you. Can we change your publishing location to be consistent with what everyone else in JBT/JBDS is now using?
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20110) Batch Diagram silently closes Palette view
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20110?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-20110:
-----------------------------------------
I tried the separate palette and I haven't found any strange behaviour, it seems to work the same way as inner palette.
However, I was not able to execute steps 5 and 6 since after restart the palette view was always closed.
I'd suggest you turn off the workaround and I can test it on nightly build.
> Batch Diagram silently closes Palette view
> ------------------------------------------
>
> Key: JBIDE-20110
> URL: https://issues.jboss.org/browse/JBIDE-20110
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Beta1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta2
>
>
> Case 1:
> 1. Open Studio.
> 2. Open Palette.
> 3. Open some batch job xml file.
> FAIL: Palette is silently closed.
> The code that does it, is commented with
> {code}
> /**
> * This is a workaround that ensures that the flyout pallete (inner
> * composite inside the diagram editor) is used instead of a separate
> * pallete view. The separate pallete view does not work with the diagram
> * editor currently.
> */
> {code}
> This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace.
> There is another case when this silent close does not work.
> Case 2:
> 1. Open some batch job xml file.
> 2. Open Palette view.
> 3. Test work with the separate palette.
> 4. Close/Restart Eclipse.
> 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it)
> 6. Test work with the separate palette.
> [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20117) Explorer: new builds get triggered if I'm playing around in OpenShift v3 connection tree
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20117?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-20117:
---------------------------------------
[~jcantrill] maybe it is upstream, but I am absolutely not sure about it. While I left IDE untouched new builds were not triggered as far as I saw. But also after first successfull build, no other builds were triggered (let's say there is build 1 PENDING, 2 FAILED, 3 FAILED, 4 PENDING .... X COMPLETE. After this point builds are not triggered anymore).
> Explorer: new builds get triggered if I'm playing around in OpenShift v3 connection tree
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-20117
> URL: https://issues.jboss.org/browse/JBIDE-20117
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> After I create an application from template and I play around with OpenShift v3 connection (expand tree items, collapse them, refresh resources, connection etc.) there are several builds triggered, what should not be. Currently I do not know what exactly is triggering builds, it's in state of investigating.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20105) Connection wizard: authenticate via OAuth in dialog (was: via external browser)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20105?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20105:
------------------------------------------
rebased, merged and pushed to upstream/master.
> Connection wizard: authenticate via OAuth in dialog (was: via external browser)
> -------------------------------------------------------------------------------
>
> Key: JBIDE-20105
> URL: https://issues.jboss.org/browse/JBIDE-20105
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: connection_wizard, oauth, openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> In JBIDE-19786 we opened the external browser to let the user authenticate via OAuth and copy his token.
> We should use a dialog (like did before but dropped it since we had issues we couldnt solve on time) since this integrates much more nicely.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20105) Connection wizard: authenticate via OAuth in dialog (was: via external browser)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20105?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20105:
------------------------------------------
[~kmarmaliykov] thx for the nice enhancement!
> Connection wizard: authenticate via OAuth in dialog (was: via external browser)
> -------------------------------------------------------------------------------
>
> Key: JBIDE-20105
> URL: https://issues.jboss.org/browse/JBIDE-20105
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: connection_wizard, oauth, openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> In JBIDE-19786 we opened the external browser to let the user authenticate via OAuth and copy his token.
> We should use a dialog (like did before but dropped it since we had issues we couldnt solve on time) since this integrates much more nicely.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months