April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} > Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > So we could use this to create composite sites in folders like: > * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date) > But also to point to remote (/stable/) URLs from pointer sites, like: > * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd) > * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1) > * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24225: ------------------------------- Fix Version/s: 4.5.x (was: 4.4.4.AM3) > publish p2diff app to Nexus for easier use in jenkins jobs > ---------------------------------------------------------- > > Key: JBIDE-24225 > URL: https://issues.jboss.org/browse/JBIDE-24225 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > Attachments: maven-releng-fetch.png > > > Rather than bootstrapping by hand and having to reference p2diff like this: > {code} > p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff > {code} > It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) ... > !maven-releng-fetch.png|thumbnail! > ... and automatically unpack it to the workspace. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM3) > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Nick Boldt > Labels: upstream > Fix For: 10.4.0.AM3 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Fix Version/s: 10.4.0.AM3 (was: 10.4.0.GA) > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Nick Boldt > Labels: upstream > Fix For: 10.4.0.AM3 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017, devex #130 April 2017 (was: devex #127 February 2017, devex #128 February 2017) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24248) Document process for async Fuse Tools releases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24248?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24248: ------------------------------- Fix Version/s: 4.5.0.AM1 > Document process for async Fuse Tools releases > ---------------------------------------------- > > Key: JBIDE-24248 > URL: https://issues.jboss.org/browse/JBIDE-24248 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fuse-tooling, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Need to add a new devdoc explaining the release process for async Fuse Tooling releases. > See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... > Something like this, but with steps to update the composite*.xml files: > {quote} > If an async release is needed: > * any CI build can be chosen to be copied from /snapshots/ to /staging/ for QE review & approval > * Once approved, that staged build can then be copied to /stable/ URL and can then be linked from Central so users can discover the update. > * Thus http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... and https://devstudio.redhat.com/10.0/stable/updates/compositeArtifacts.xml would simply add in the new Fuse x.y.z release ... VERY MINIMAL effort to update these files (Nick or Paul can both do this) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23824) Move hibernate.reddeer + itests from jbosstools-integration-tests to jbosstools-hibernate

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23824?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23824: ------------------------------------ There are couple of items being solved in devex 130. 1) download-devstudio profile: doesn't work when run on component level. The resolution is to not use it by default and to define all deps in manifest. See: https://issues.jboss.org/browse/JBIDE-24129 2) the tests have been failing on macOs because, sakila db has not been ready. The db process was running but not accepting connections. Added check into DatabaseUtils. 3) problem with another profile that QE is using. ITests profile defines useUIThread=false and some plugin customizations, however the hibernate unit tests are failing with useUIThread=false, but itests do require useUIThread=false. We need to find best solution. Working on this jira always bring new problems to solve. > Move hibernate.reddeer + itests from jbosstools-integration-tests to jbosstools-hibernate > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23824 > URL: https://issues.jboss.org/browse/JBIDE-23824 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate, integration-tests > Affects Versions: 4.4.3.AM2 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24195) Forge New and Noteworthy for 4.4.4.AM3

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24195?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-24195: ------------------------------------ Fix Version/s: 4.4.4.AM3 > Forge New and Noteworthy for 4.4.4.AM3 > --------------------------------------------------- > > Key: JBIDE-24195 > URL: https://issues.jboss.org/browse/JBIDE-24195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.4.AM3 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge 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 Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge 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... {code}JBIDE-24190 #comment Create N&N for Forge 4.4.4.AM3 #close{code}... 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 Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24195) Forge New and Noteworthy for 4.4.4.AM3

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24195?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-24195: ------------------------------------ Affects Version/s: 4.4.4.AM2 > Forge New and Noteworthy for 4.4.4.AM3 > --------------------------------------------------- > > Key: JBIDE-24195 > URL: https://issues.jboss.org/browse/JBIDE-24195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.4.AM3 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge 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 Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge 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... {code}JBIDE-24190 #comment Create N&N for Forge 4.4.4.AM3 #close{code}... 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 Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 April 2017