December 2016 - jbosstools-issues

[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 #115 May 2016, devex #116 June 2016, devex #118 July 2016, devex #119 August 2016, devex #121 October 2016, devex #124 December 2017 (was: devex #115 May 2016, devex #116 June 2016, devex #118 July 2016, devex #119 August 2016, devex #121 October 2016) > 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.x > > > 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 (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4214) use a less confusing path segment for the devstudio update & build folders

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4214?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4214: ---------------------------------- Order of preference: * 11 * 11.x * oxygen -1 for e47 > use a less confusing path segment for the devstudio update & build folders > -------------------------------------------------------------------------- > > Key: JBDS-4214 > URL: https://issues.jboss.org/browse/JBDS-4214 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, updatesite > Affects Versions: 10.2.0.GA > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 11.0.0.AM1 > > > Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing. > So, for devstudio 11, we could use: > * /11/ > * /11.x/ > * /oxygen/ (because this is based on Eclipse Oxygen) > * /e47/ (because this is based on Eclipse 4.7) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4214) use a less confusing path segment for the devstudio update & build folders

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4214?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-4214: -------------------------------------- I like 11, 11.x and /oxygen. If there is no objections from PM then I would go with "oxygen". It will allow us to use to be consistent with both Devstudio and JBoss Tools. [~jeffmaury] WDYT? [~tmancini] ? > use a less confusing path segment for the devstudio update & build folders > -------------------------------------------------------------------------- > > Key: JBDS-4214 > URL: https://issues.jboss.org/browse/JBDS-4214 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, updatesite > Affects Versions: 10.2.0.GA > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 11.0.0.AM1 > > > Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing. > So, for devstudio 11, we could use: > * /11/ > * /11.x/ > * /oxygen/ (because this is based on Eclipse Oxygen) > * /e47/ (because this is based on Eclipse 4.7) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4214) use a less confusing path segment for the devstudio update & build folders

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4214: -------------------------------- Summary: use a less confusing path segment for the devstudio update & build folders Key: JBDS-4214 URL: https://issues.jboss.org/browse/JBDS-4214 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: build, rpm, updatesite Affects Versions: 10.2.0.GA Reporter: Nick Boldt Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing. So, for devstudio 11, we could use: * /11/ * /11.x/ * /oxygen/ (because this is based on Eclipse Oxygen) * /e47/ (because this is based on Eclipse 4.7) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4214) use a less confusing path segment for the devstudio update & build folders

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4214?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4214: -------------------------------- Assignee: Alexey Kazakov > use a less confusing path segment for the devstudio update & build folders > -------------------------------------------------------------------------- > > Key: JBDS-4214 > URL: https://issues.jboss.org/browse/JBDS-4214 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, updatesite > Affects Versions: 10.2.0.GA > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 11.0.0.AM1 > > > Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing. > So, for devstudio 11, we could use: > * /11/ > * /11.x/ > * /oxygen/ (because this is based on Eclipse Oxygen) > * /e47/ (because this is based on Eclipse 4.7) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4214) use a less confusing path segment for the devstudio update & build folders

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4214?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4214: ----------------------------- Fix Version/s: 11.0.0.AM1 > use a less confusing path segment for the devstudio update & build folders > -------------------------------------------------------------------------- > > Key: JBDS-4214 > URL: https://issues.jboss.org/browse/JBDS-4214 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, updatesite > Affects Versions: 10.2.0.GA > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 11.0.0.AM1 > > > Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing. > So, for devstudio 11, we could use: > * /11/ > * /11.x/ > * /oxygen/ (because this is based on Eclipse Oxygen) > * /e47/ (because this is based on Eclipse 4.7) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13035) Maven Repositories : TextMerge Preview always shows whitespace changes on Windows

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13035?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13035: -------------------------------- Summary: Maven Repositories : TextMerge Preview always shows whitespace changes on Windows (was: Mave Repositories : TextMerge Preview always shows whitespace changes on Windows) > Maven Repositories : TextMerge Preview always shows whitespace changes on Windows > --------------------------------------------------------------------------------- > > Key: JBIDE-13035 > URL: https://issues.jboss.org/browse/JBIDE-13035 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.0.0.Beta2 > Environment: Windows 7 pro 64 > Reporter: Fred Bricon > Assignee: Alexey Kazakov > Fix For: 4.5.0.AM1 > > Attachments: Text_Merge_preview_show_whitespace_changes.png > > > On Windows, the Maven Repositories wizard's preview pane always shows whitespace changes, diminishing the preview usefulness. > !Text_Merge_preview_show_whitespace_changes.png! > I tried to mess with the code a bit but to no avail. I suspected some line endings weirdness, but it seems to be really a problem with white spaces. I tried to compare the contents of my original settings.xml, to the contents in both panels, using an hex editor, they really are identical. > I don't have any issue on linux. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23559) Server New and Noteworthy for 4.4.2.Final

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23559?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23559: -------------------------------- Fix Version/s: 4.4.2.Final > Server New and Noteworthy for 4.4.2.Final > ----------------------------------------------------- > > Key: JBIDE-23559 > URL: https://issues.jboss.org/browse/JBIDE-23559 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.Final > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Server4.4.2.Final #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of Server, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4170) Remove windows uninstaller from mac distribution

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4170?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4170: ----------------------------------- Assignee: Sudhir Verma (was: Denis Golovin) > Remove windows uninstaller from mac distribution > ------------------------------------------------ > > Key: JBDS-4170 > URL: https://issues.jboss.org/browse/JBDS-4170 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: mac osx > Reporter: Jan Richter > Assignee: Sudhir Verma > Fix For: 10.3.0.AM1 > > > The uninstaller/uninstall.ps1 is getting generated by the mac installer. Remove it or replace with something that runs on mac (like a shell script). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3022) Iintermittent/Recurring Crash of JBDS 7.1.1 - when defining a new server runtime

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3022?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3022: ---------------------------------- Is this still a problem? This was reported for jbds 7... which is 3 Eclipse major releases ago. > Iintermittent/Recurring Crash of JBDS 7.1.1 - when defining a new server runtime > -------------------------------------------------------------------------------- > > Key: JBDS-3022 > URL: https://issues.jboss.org/browse/JBDS-3022 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: runtime-detection, upstream > Affects Versions: 7.1.1.GA, 8.0.0.Beta2 > Environment: uname -a > Linux ldimaggi.csb 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux > cat /etc/redhat-release > Red Hat Enterprise Linux Workstation release 6.5 (Santiago) > java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (rhel-2.4.4.1.el6_5-x86_64 u51-b02) > OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 10.3.0.AM1 > > Attachments: Crash.mov, hs_error.log > > > Iintermittent/Recurring Crash of JBDS 7.1.1 - when defining a new server runtime > See attached screencast - crash occurs at the 14 second mark - seeing this 50-80% of the time on one RHEL 6.5 system. > Steps to repeat: > * install JBDS 7.1.1 > jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > -or- > jbdevstudio-product-universal-7.1.1.GA-v20140314-2145-B688.jar > * Create a new server runtime - at the point that Next> is pressed after selecting the runtime version, the crash occurs > * Only seeing this with JBDS - not Eclipse Kepler + JBTools -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016