May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21657: ------------------------------------ Guys, the jobs with "__pull-request" in their name were experimental. Ultimately my goal is to have jobs with just _master or _4.4.neon which will handle BOTH PRs and regular commits. See JBIDE-21785 for that work in progress. I don't think we need 20 separate jobs for each component's PR builds. {quote} Is it necessary to publish e p2 repo for the topic branch? I see the configuration is jbosstools-server__pull-request_master is now much more complicated than a simple "mvn clean verify", introducing an intermediary script to orchestrate Maven ( https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... ). Do we need all that complexity? Do all those build flags need to be overriden? Shouldn't we be using the default from pom.xml instead? {quote} The script actually reduces complexity because instead of having a job that invokes maven 3 times (build, optionally deploy based on shell wrapper for maven, tests), we need only call a single bash script, which is versioned in github, and which works IDENTICALLY for all the component jobs - for both commits and PRs. This prevents devs from accidentally/intentionally making changes to their job config which makes it deviate from other jobs' configs. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-696) Update BPEL feature to 1.3.101.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-696?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-696. ----------------------------------- Verified with updating from JBDS-IS 8.0.2.GA to JBDS-IS 8.0.7.CR1 > Update BPEL feature to 1.3.101.Final > ------------------------------------ > > Key: JBTIS-696 > URL: https://issues.jboss.org/browse/JBTIS-696 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPEL, distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Labels: release_notes, verified_jbdsis-8.0.7 > Fix For: 8.0.7.CR1 > > > The BPEL editor cannot be updated if a user installs it from JBDS-IS 8.0.2.GA and earlier. For more information please see JBTIS-470. > Note that there is no change in BPEL editor the only problem is that it is not automatically updated from 1.0.4 (JBDS-IS 8.0.2) to 1.0.5 (JBDS-IS 8.0.3+) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-696) Update BPEL feature to 1.3.101.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-696?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-696: ------------------------------------ Labels: release_notes verified_jbdsis-8.0.7 (was: ) > Update BPEL feature to 1.3.101.Final > ------------------------------------ > > Key: JBTIS-696 > URL: https://issues.jboss.org/browse/JBTIS-696 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPEL, distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Labels: release_notes, verified_jbdsis-8.0.7 > Fix For: 8.0.7.CR1 > > > The BPEL editor cannot be updated if a user installs it from JBDS-IS 8.0.2.GA and earlier. For more information please see JBTIS-470. > Note that there is no change in BPEL editor the only problem is that it is not automatically updated from 1.0.4 (JBDS-IS 8.0.2) to 1.0.5 (JBDS-IS 8.0.3+) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3470) Toolbars + Icons unusable on UHD screens

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3470?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3470: ----------------------------- Fix Version/s: 10.x (was: 10.0.0.Alpha1) > Toolbars + Icons unusable on UHD screens > ---------------------------------------- > > Key: JBDS-3470 > URL: https://issues.jboss.org/browse/JBDS-3470 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: ui/branding, upstream > Affects Versions: 9.0.0.Beta1 > Environment: Windows + UHD screens > Reporter: Mustafa Musaji > Labels: neon > Fix For: 10.x > > Attachments: hi-res-example.png, jbds-after-scaling.png, wordpad-scaling.png > > > When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > Upstream: https://bugs.eclipse.org/bugs/show_bug.cgi?id=382972 > I'm raising this for QE to ensure we test this in the next release as it was fixed upstream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3605 at 5/16/16 10:24 AM: ------------------------------------------------------------ Apologies for the slow response. Was on PTO last week. If you open images in Chrome, the status bar tells you the file sizes. Or you could download them to check. At any rate, here are the dimensions of the current images, as requested, in pixels. ./installer/src/config/resources/images/jbeap_edit_wiz.png - 75x66 ./installer/src/config/resources/images/jbeap_new_wiz.png - 75x66 ./installer/src/config/resources/icons/jbds_uninstall.ico - 64x64 ./plugins/com.jboss.devstudio.core/themes/jbds/graphics/icons/ctool/gettingstarted.png - 103x103 ./plugins/com.jboss.devstudio.core/themes/jbds/graphics/icons/ctool/gs_nav.png - 32x32 {quote} the red circle would be replaced by the Red Hat Developer bracket logo circle that I sent you a while ago?{quote} Yes. The "JBDS redball" becomes the "RHD brackets" in all the new branding. was (Author: nickboldt): Apologies for the slow response. Was on PTO last week. If you open images in Chrome, the status bar tells you the file sizes. Or you could download them to check. At any rate, here are the dimensions of the current images, as requested, in pixels. ./installer/src/config/resources/images/jbeap_edit_wiz.png - 75x66 ./installer/src/config/resources/images/jbeap_new_wiz.png - 75x66 ./installer/src/config/resources/icons/jbds_uninstall.ico - 64x64 ./plugins/com.jboss.devstudio.core/themes/jbds/graphics/icons/ctool/gettingstarted.png - 103x103 ./plugins/com.jboss.devstudio.core/themes/jbds/graphics/icons/ctool/gs_nav.png - 32x32 > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: about-jbds10.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3605: ---------------------------------- Apologies for the slow response. Was on PTO last week. If you open images in Chrome, the status bar tells you the file sizes. Or you could download them to check. At any rate, here are the dimensions of the current images, as requested, in pixels. ./installer/src/config/resources/images/jbeap_edit_wiz.png - 75x66 ./installer/src/config/resources/images/jbeap_new_wiz.png - 75x66 ./installer/src/config/resources/icons/jbds_uninstall.ico - 64x64 ./plugins/com.jboss.devstudio.core/themes/jbds/graphics/icons/ctool/gettingstarted.png - 103x103 ./plugins/com.jboss.devstudio.core/themes/jbds/graphics/icons/ctool/gs_nav.png - 32x32 > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: about-jbds10.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- 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: ----------------------------- Fix Version/s: 10.0.0.Alpha2 (was: 10.0.0.Alpha1) > 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.Alpha2 > > 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-21567) JBoss EAP 7 Maven repository is not recognized

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21567?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-21567. --------------------------------- Retested with repository: http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0-Beta/jboss-eap-... (the mentioned repository has not accessible) Extracted zip was correctly recognized as a JBoss EAP Maven Repository. Closing issue. Tested in version: Version: 10.0.0.Alpha1 Build id: Alpha1-v20160429-1112-B5258 Build date: 20160429-1112 > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-21567 > URL: https://issues.jboss.org/browse/JBIDE-21567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-708) Update XML tests, XML model editor and dialogs

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-708?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-708: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/716, https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/717 (was: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/716) > Update XML tests, XML model editor and dialogs > ---------------------------------------------- > > Key: JBTIS-708 > URL: https://issues.jboss.org/browse/JBTIS-708 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: Andrej Podhradsky > Fix For: 4.2.6.Final, 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher refresh view but collapse tree items to project level

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22361: --------------------------------------- Ok I've change description and steps to reproduce and lower priority to major, since it is not critical anymore. > OpenShift Explorer: Watcher refresh view but collapse tree items to project level > --------------------------------------------------------------------------------- > > Key: JBIDE-22361 > URL: https://issues.jboss.org/browse/JBIDE-22361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > > When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod in running state. Once watcher should update resources automatically, tree items are collapsed to project level (if service was visible, it is not anymore, only connection with its project). -- 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