May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3790) Copyright notices for installer and IDE are "2004-2015" - must we update this to "2004-2016?"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3790?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3790. ---------------------------- Resolution: Duplicate Copyright date in the About dialog changed via JBDS-3845. Date in the EULA I won't change because the latest version of the EULA is from 2010, so there's no need to update it there: https://www.redhat.com/en/about/red-hat-end-user-license-agreements -> https://www.redhat.com/f/pdf/licenses/GLOBAL_EULA_RHEL_English_20101110.pdf > Copyright notices for installer and IDE are "2004-2015" - must we update this to "2004-2016?" > --------------------------------------------------------------------------------------------- > > Key: JBDS-3790 > URL: https://issues.jboss.org/browse/JBDS-3790 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Version: 9.1.0.GA > Build id: GA-v20160410-1849-B495 > Build date: 20160410-1849 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha2 > > Attachments: copyright_IDE.png, copyright_installer.png > > > See the attached screenshots - Must we update these to 2016 before GA? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21041) Appliaction wizard: "Remove" button in Resource Labels page should be "Remove..."

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21041?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21041. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Appliaction wizard: "Remove" button in Resource Labels page should be "Remove..." > --------------------------------------------------------------------------------- > > Key: JBIDE-21041 > URL: https://issues.jboss.org/browse/JBIDE-21041 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: bad-remove-button-label.png > > > Remove button located on the 3rd New OpenShift Application wizard page (the one with resource labels) should have label "Remove..." instead of "Removed". It's because there is invoked dialog for removal confirmation of a label. If it would be Remove, then no confirmation would be expected. We use this approach all over the wizards and dialogs - if there is expected further user interaction, the "..." should follow a label. > !bad-remove-button-label.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21229) Inconsistent upper casing in New Connection dialog

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21229?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21229. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-21229 > URL: https://issues.jboss.org/browse/JBIDE-21229 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22229: ------------------------------- Sprint: devex #114 May 2017 (was: devex #115 May 2017) > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22229: ------------------------------- Sprint: devex #115 May 2017 (was: devex #114 May 2017) > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20904: ------------------------------- Sprint: devex #114 May 2017 (was: devex #115 May 2017) > automate publishing latest CI build to staging, then from staging to development (or stable) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-comman... > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3606) update branding for jbds 10.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3606?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3606: ----------------------------- Sprint: (was: devex #113 April 2016) > update branding for jbds 10.0 installer > --------------------------------------- > > Key: JBDS-3606 > URL: https://issues.jboss.org/browse/JBDS-3606 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > Attachments: installer-10.png > > > name and branding of JBDS set to change. Need the base izpack based installer to have an updated look. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3606) update branding for jbds 10.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3606?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3606: ----------------------------- Sprint: devex #115 May 2017 > update branding for jbds 10.0 installer > --------------------------------------- > > Key: JBDS-3606 > URL: https://issues.jboss.org/browse/JBDS-3606 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > Attachments: installer-10.png > > > name and branding of JBDS set to change. Need the base izpack based installer to have an updated look. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3606) update branding for jbds 10.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3606?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3606: ----------------------------- Sprint: devex #114 May 2017 (was: devex #115 May 2017) > update branding for jbds 10.0 installer > --------------------------------------- > > Key: JBDS-3606 > URL: https://issues.jboss.org/browse/JBDS-3606 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > Attachments: installer-10.png > > > name and branding of JBDS set to change. Need the base izpack based installer to have an updated look. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21775) OpenShift 2 connection loading message is archaic

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21775?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21775. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > OpenShift 2 connection loading message is archaic > ------------------------------------------------- > > Key: JBIDE-21775 > URL: https://issues.jboss.org/browse/JBIDE-21775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Minor > Labels: openshift_v2 > Fix For: 4.4.0.Alpha1 > > Attachments: progress_dialog.png > > > When loading OS2 connection there is sometimes progress dialog informing about loading of connection details. It has deprecated "ExpressConnection" message, probably it remained from times when there was OpenShift Express. > !progress_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016