August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22382: ------------------------------------- I find it a bit ... agressive, but maybe it's just me. But it sure matches the RHD branding. [~akazakov], [~maxandersen] thoughts? But we're starting to digress from the original issue which is to change the shadowman logo for Central. I'm fine repurposing this JIRA for Central rebranding, but eventually we'll have to address that damn icon :-) > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.x > > Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-22382 at 8/11/16 2:44 PM: -------------------------------------------------------------- [~fbricon] [~crobson] I've pulled in the branding fro RHD into this IDE panel. 1. I've opted to use colors verses an grey monotones 2. I've used Red Hat icons from the icon set !tools_rebrand.png! Thoughts? was (Author: james.cobb): [~fbricon] [~crobson] I've pulled in the branding fro RHD into this IDE panel. 1. I've opted to use colors verses an grey monotones 2. I've used Red Hat icons from the icon set Thoughts? > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.x > > Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-377) [JS Debugger] Need to add path validation for Chromium / Chrome Runtime [EBZ#499567]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-377: --------------------------------------- Summary: [JS Debugger] Need to add path validation for Chromium / Chrome Runtime [EBZ#499567] Key: ERT-377 URL: https://issues.jboss.org/browse/ERT-377 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-704) Marketplace entries use the old license

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-704?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-704: ---------------------------------- This is the same issue as with JBTIS-702. The fix is more complicated though - can't modify the jar manually with any certainty. This is fixed in JBDSIS 9.0.2. > Marketplace entries use the old license > --------------------------------------- > > Key: JBTIS-704 > URL: https://issues.jboss.org/browse/JBTIS-704 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: jbdsis901ga_marketplace.png > > > The following features still use the old license > - com.jboss.devstudio.integration-stack.bpr.feature > - com.jboss.devstudio.integration-stack.ds.feature (on EA) > - com.jboss.devstudio.integration-stack.fuse.feature (on EA) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-702) BxMS feature in marketplace doesn't install Kie navigator

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-702?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-702 at 8/11/16 2:05 PM: ----------------------------------------------------------- See comment. [~apodhrad] - please try EM again. I think there might be an issue with my Java 1.8_101. I hand corrected the feature.xml to include KIE. was (Author: pleacu): See comment. > BxMS feature in marketplace doesn't install Kie navigator > --------------------------------------------------------- > > Key: JBTIS-702 > URL: https://issues.jboss.org/browse/JBTIS-702 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Environment: Eclipse Mars.2 for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.2.GA > > > After installing BxMS feature form marketplace I noticed that the Kie Navigator is missing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-702) BxMS feature in marketplace doesn't install Kie navigator

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-702?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-702. ------------------------------ Fix Version/s: 9.0.2.GA (was: 9.0.1.GA) Resolution: Done See comment. > BxMS feature in marketplace doesn't install Kie navigator > --------------------------------------------------------- > > Key: JBTIS-702 > URL: https://issues.jboss.org/browse/JBTIS-702 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Environment: Eclipse Mars.2 for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.2.GA > > > After installing BxMS feature form marketplace I noticed that the Kie Navigator is missing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-376) [JS Debugger] Need to improve mapping logic between base url and js files in workspace [EBZ#499566]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-376: --------------------------------------- Summary: [JS Debugger] Need to improve mapping logic between base url and js files in workspace [EBZ#499566] Key: ERT-376 URL: https://issues.jboss.org/browse/ERT-376 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot For now js debugger available for launch on IServerModules map application base url to project's "webapp" folder. This will not always works (resources can be located in other places).Assuming that servers have a way to gather and assemble the deployment artifacts need to improve mapping logic -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22966: ------------------------------- Description: Sample issue to scrape: https://bugzilla.redhat.com/show_bug.cgi?id=1363849 More issues: https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... Target method: * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) Mappings: * BZ Product = Red Hat Software Collections --> RHECLIPSE jira * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA * Target Milestone --> label in JIRA * Target Release -> label in JIRA [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py was: Sample issue to scrape: https://bugzilla.redhat.com/show_bug.cgi?id=1363849 More issues: https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... Target method: * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) Mappings: * BZ Product = Red Hat Software Collections --> RH-ECLIPSE jira * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA * Target Milestone --> label in JIRA * Target Release -> label in JIRA [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22966: ------------------------------------ https://issues.jboss.org/projects/RHECLIPSE has been created. [~maxandersen] has agreed to look into creating a similar project entry on issues.stage.jboss.org too. > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RH-ECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22968: ------------------------------------ More p2diff checks enabled here: https://github.com/jbdevstudio/jbdevstudio-ci/commit/3305669b60f2a8f296ce... > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016