October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23353) Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23353?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-23353: ------------------------------------- This is exactly the behavior I expected when opening JBIDE-23015 > Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click > ----------------------------------------------------------------------------- > > Key: JBIDE-23353 > URL: https://issues.jboss.org/browse/JBIDE-23353 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > > In Deploy Image to OpenShift on wizard page with routing settings there is a table with port mapping. There is a table cell with checkbox to be used by routing. This is not editable by clicking on the cell. User is forced to open dialog to edit port mapping, manually click on a checkbox to use for routing and confirm dialog. This is pretty user unfriendly. It should be enabled to click on the cell and have checkbox checked/unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23264) Add content assistant for attributes restart, include, exclude, etc. in design view

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23264?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23264: ---------------------------------- Fix Version/s: 4.4.x > Add content assistant for attributes restart, include, exclude, etc. in design view > ----------------------------------------------------------------------------------- > > Key: JBIDE-23264 > URL: https://issues.jboss.org/browse/JBIDE-23264 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.4.1.Final > Environment: Fedora 24 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.4.x > > > In general, content assist does not work in Design View (in tables, where properties, exception and other components are defined) and also in Diagram View in Properties tab. Seems that this features are not implemented yet. Also, it is missing at defining the properties (ie. in section Properties of Batchlet artefact definitionin design view tab) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23387) enable jiralint nagging for CDK project JIRAs

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23387: ---------------------------------- Summary: enable jiralint nagging for CDK project JIRAs Key: JBIDE-23387 URL: https://issues.jboss.org/browse/JBIDE-23387 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.2.AM2 Reporter: Nick Boldt As discussed on the sprint retrospective, CDK devs are not properly cleaning up their JIRAs (eg., completed issues not marked resolved/closed). So, we should enable jiralint [1] to also nag those devs about their jiras. [1] https://github.com/jbosstools/jiralint -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23387) enable jiralint nagging for CDK project JIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23387?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23387: ------------------------------- Fix Version/s: 4.4.2.AM3 > enable jiralint nagging for CDK project JIRAs > --------------------------------------------- > > Key: JBIDE-23387 > URL: https://issues.jboss.org/browse/JBIDE-23387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > As discussed on the sprint retrospective, CDK devs are not properly cleaning up their JIRAs (eg., completed issues not marked resolved/closed). > So, we should enable jiralint [1] to also nag those devs about their jiras. > [1] https://github.com/jbosstools/jiralint -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23387) enable jiralint nagging for CDK project JIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23387?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23387: ---------------------------------- Assignee: Nick Boldt > enable jiralint nagging for CDK project JIRAs > --------------------------------------------- > > Key: JBIDE-23387 > URL: https://issues.jboss.org/browse/JBIDE-23387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > As discussed on the sprint retrospective, CDK devs are not properly cleaning up their JIRAs (eg., completed issues not marked resolved/closed). > So, we should enable jiralint [1] to also nag those devs about their jiras. > [1] https://github.com/jbosstools/jiralint -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-929) Fuse project starter is available in Central only if we check EarlyAccess

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBTIS-929?page=com.atlassian.jira.plugin.... ] Fred Bricon resolved JBTIS-929. ------------------------------- Fix Version/s: 9.0.2.GA Resolution: Done The fuse examples show up now. Just make sure you restart your workspace. !https://s3.amazonaws.com/uploads.hipchat.com/405735/3426649/qvbGbT1iQ97TwZI/upload.png! > Fuse project starter is available in Central only if we check EarlyAccess > ------------------------------------------------------------------------- > > Key: JBTIS-929 > URL: https://issues.jboss.org/browse/JBTIS-929 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 9.0.2.GA > Environment: JBDS 9.1.0.GA + JBDS-IS 9.0.2.GA > Reporter: Andrej Podhradsky > Assignee: Fred Bricon > Fix For: 9.0.2.GA > > > Fuse project starter is available in Central only if we check EarlyAccess. Moreover, if you close and reopen the RedHat Central then the project starter dissappears. You have to uncheck and check the EA again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23386) add code freeze notification to staging build email notification template

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23386?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23386: ---------------------------------- Assignee: Nick Boldt > add code freeze notification to staging build email notification template > ------------------------------------------------------------------------- > > Key: JBIDE-23386 > URL: https://issues.jboss.org/browse/JBIDE-23386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > So that devs know when code freeze is in effect, we need to add a reminder to the '...is available for QE testing' emails so that: > * for master branch / AMx builds, code freeze is in effect until QE signoff on Tues/Wed after the build is available > * for 4.a.x (or 4.a.b.x) branches / GA builds, code freeze applies only to the 4.a.x branch, not to master. master is wide open for new dev as soon as the branch is created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23386) add code freeze notification to staging build email notification template

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23386?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23386: ------------------------------- Fix Version/s: 4.4.2.AM3 > add code freeze notification to staging build email notification template > ------------------------------------------------------------------------- > > Key: JBIDE-23386 > URL: https://issues.jboss.org/browse/JBIDE-23386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > So that devs know when code freeze is in effect, we need to add a reminder to the '...is available for QE testing' emails so that: > * for master branch / AMx builds, code freeze is in effect until QE signoff on Tues/Wed after the build is available > * for 4.a.x (or 4.a.b.x) branches / GA builds, code freeze applies only to the 4.a.x branch, not to master. master is wide open for new dev as soon as the branch is created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23386) add code freeze notification to staging build email notification template

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23386?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23386: ------------------------------- Description: So that devs know when code freeze is in effect, we need to add a reminder to the '...is available for QE testing' emails so that: * for master branch / AMx builds, code freeze is in effect until QE signoff on Tues/Wed after the build is available * for 4.a.x (or 4.a.b.x) branches / GA builds, code freeze applies only to the 4.a.x branch, not to master. master is wide open for new dev as soon as the branch is created was: So that devs know when code freeze is in effect, we need to add a reminder to the '...is available for QE testing' emails so that: * for master branch / AMx builds, code freeze is in effect until QE signoff on Tues/Wed after the build is available * for 4.y.*.x branches / GA builds, code freeze applies only to the 4.*.x branch, not to master. master is wide open for new dev as soon as the branch is created > add code freeze notification to staging build email notification template > ------------------------------------------------------------------------- > > Key: JBIDE-23386 > URL: https://issues.jboss.org/browse/JBIDE-23386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Fix For: 4.4.2.AM3 > > > So that devs know when code freeze is in effect, we need to add a reminder to the '...is available for QE testing' emails so that: > * for master branch / AMx builds, code freeze is in effect until QE signoff on Tues/Wed after the build is available > * for 4.a.x (or 4.a.b.x) branches / GA builds, code freeze applies only to the 4.a.x branch, not to master. master is wide open for new dev as soon as the branch is created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23386) add code freeze notification to staging build email notification template

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23386: ---------------------------------- Summary: add code freeze notification to staging build email notification template Key: JBIDE-23386 URL: https://issues.jboss.org/browse/JBIDE-23386 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.2.AM2 Reporter: Nick Boldt So that devs know when code freeze is in effect, we need to add a reminder to the '...is available for QE testing' emails so that: * for master branch / AMx builds, code freeze is in effect until QE signoff on Tues/Wed after the build is available * for 4.y.*.x branches / GA builds, code freeze applies only to the 4.*.x branch, not to master. master is wide open for new dev as soon as the branch is created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016