September 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26377) Upgrade jacoco to 0.8.2+

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-26377: --------------------------------------- Summary: Upgrade jacoco to 0.8.2+ Key: JBIDE-26377 URL: https://issues.jboss.org/browse/JBIDE-26377 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Aurélien Pupier requires upgrade of Jenkins plugins it will allow to benefits from latest fix and improvements of Jacoco and avoids to have to set a specific version of jacoco for each jdk version profile -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24769) Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24769?page=com.atlassian.jira.plugi... ] Aurélien Pupier resolved JBIDE-24769. ------------------------------------- Resolution: Won't Do given the time it has been opened and the fact that dev slows down, i think we can close as "won't do" > Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools > --------------------------------------------------------------------------------------- > > Key: JBIDE-24769 > URL: https://issues.jboss.org/browse/JBIDE-24769 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Fix For: 4.9.x > > > as reported in initial document here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > The differences are explained in this old thread http://lists.jboss.org/pipermail/jbosstools-dev/2016-January/010908.html > I gave a talk @EclipseCon on the subject: https://www.youtube.com/watch?v=IGkFy2H-d60 > To make it short: > Fuse Tooling: > - "unit test" are at class level --> plugin named *.tests, test named *Test > - "integration test" are at osgi level --> plugin named *.tests.integration, test named *IT > Jboss Tools: > - "unit test" are at osgi level --> plugin named *.tests; test named *Test > - "integration test" are also at osgi level but with more complex requirements on environment -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24769) Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24769?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-24769: --------------------------------------- Assignee: (was: Aurélien Pupier) > Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools > --------------------------------------------------------------------------------------- > > Key: JBIDE-24769 > URL: https://issues.jboss.org/browse/JBIDE-24769 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Fix For: 4.9.x > > > as reported in initial document here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > The differences are explained in this old thread http://lists.jboss.org/pipermail/jbosstools-dev/2016-January/010908.html > I gave a talk @EclipseCon on the subject: https://www.youtube.com/watch?v=IGkFy2H-d60 > To make it short: > Fuse Tooling: > - "unit test" are at class level --> plugin named *.tests, test named *Test > - "integration test" are at osgi level --> plugin named *.tests.integration, test named *IT > Jboss Tools: > - "unit test" are at osgi level --> plugin named *.tests; test named *Test > - "integration test" are also at osgi level but with more complex requirements on environment -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by James Cobb (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] James Cobb commented on JBDS-4730: ---------------------------------- [~nickboldt] - I heard back from Brand on this. "All of these product names should follow this naming structure: Master Brand + Sub Brand + Product Name + optional modifier so the new name would be: *Red Hat Code Ready Developer Studio* Erin had previously shared a list of names that would be transitioning under the Code Ready umbrella which included Developer Studio, but asked us to hold off while some details got ironed out. Our understanding is that nothing has been finalized enough to start creating any assets quite yet." So it seems like this should be held up a bit until this gets ironed out. > [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Comment: was deleted (was: Thanks. I believe the name is only CodeReady Studio, not Red Hat CodeReady Studio, but they'll know best. :D) > [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Description: Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio". As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. was: Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. > [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Summary: [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text (was: [Rebranding] Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text) > [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) [Rebranding] Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4730: ----------------------------- Summary: [Rebranding] Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text (was: Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text) > [Rebranding] Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > -------------------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26334?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26334: ------------------------------------- Attachment: new-wizard-page.png > Launcher wizard: improve user experience > ---------------------------------------- > > Key: JBIDE-26334 > URL: https://issues.jboss.org/browse/JBIDE-26334 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: launcher_wizard > Fix For: 4.9.0.Final > > Attachments: error-markers-for-missing-info.png, location-missing-decoration.png, maven-artifact-elements.png, mission-infos.png, new-wizard-page.png > > > The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user. > Suggested improvements: > * A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide. > !mission-infos.png! > * A novice user has no idea what the maven artifact elements are for. > !maven-artifact-elements.png! > * Generally speaking it is preferable to decorate missing input fields with a "*" than to mark them as errors (as one can see in most web forms). OpenShift tooling does this as a rule of thumb. > !error-markers-for-missing-info.png! > * Location is not decorated with an "required value" (or error) marker > !location-missing-decoration.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26334?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26334: ------------------------------------------ The PR changed the wizard to look like this: !new-wizard-page.png! > Launcher wizard: improve user experience > ---------------------------------------- > > Key: JBIDE-26334 > URL: https://issues.jboss.org/browse/JBIDE-26334 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: launcher_wizard > Fix For: 4.9.0.Final > > Attachments: error-markers-for-missing-info.png, location-missing-decoration.png, maven-artifact-elements.png, mission-infos.png, new-wizard-page.png > > > The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user. > Suggested improvements: > * A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide. > !mission-infos.png! > * A novice user has no idea what the maven artifact elements are for. > !maven-artifact-elements.png! > * Generally speaking it is preferable to decorate missing input fields with a "*" than to mark them as errors (as one can see in most web forms). OpenShift tooling does this as a rule of thumb. > !error-markers-for-missing-info.png! > * Location is not decorated with an "required value" (or error) marker > !location-missing-decoration.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 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 September 2018