August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ] Catherine Robson updated JBDS-4444: ----------------------------------- Attachment: RHDS_Installer_RHDAccountLoginScreen_Aug6-2017.jpg > [DevSuite Installer] Move Account step after Confirmation step > -------------------------------------------------------------- > > Key: JBDS-4444 > URL: https://issues.jboss.org/browse/JBDS-4444 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, ui > Fix For: 11.0.0.GA > > Attachments: RHDS_Installer_RHDAccountLoginScreen_Aug6-2017.jpg, about-background.png, about-update1.png, devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png, install-step-3-1.png, install-step-3-2.png, install-step-4.png, install-step-5-1.png, install-step-5-2.png, install-step-6-1.png, install-step-6.png, install-step1.png, install-step2.png > > > As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation. > Current workflow is > !devsuite-installer-1.4.0-workflow.png|thumbnail! > should be transformed to > !devsuite-installer-2.0.0-workflow.png|thumbnail! > This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation. > Here are screenshots for how it could look like for scenario when Red Hat Product Selected: > !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-1.png|thumbnail! !install-step-4.png|thumbnail! !install-step-5-2.png|thumbnail! !install-step-6-1.png|thumbnail! > and when community or 3rd party components only selected: > !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-2.png|thumbnail! !install-step-5-1.png|thumbnail! !install-step-6.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1158) Removing Pattern via Property View Leaves Empty Attribute

by Scott England-Sullivan (JIRA)

Scott England-Sullivan created JBTIS-1158: --------------------------------------------- Summary: Removing Pattern via Property View Leaves Empty Attribute Key: JBTIS-1158 URL: https://issues.jboss.org/browse/JBTIS-1158 Project: JBoss Tools Integration Stack Issue Type: Bug Components: Fuse IDE Affects Versions: 10.3.0.GA Environment: OSX 10.11 JBDS 10.4.0 Java 1.8 Camel 2.17 Spring Project Reporter: Scott England-Sullivan Attachments: Screen Shot 2017-08-06 at 3.34.15 PM.png When using the Property View / Details Tab, if a user adds a "Pattern" to a component a pattern attribute is created in the XML and the value is added to the attribute. If the value is removed via the same view and tab, the pattern attribute is left in the element with an empty string creating an error in the resulting XML. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4407) DevSuite 1.4 Installer, No Help, About, Place to Report Bugs, etc.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4407?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4407: -------------------------------- Sprint: (was: devex #135 July 2017) > DevSuite 1.4 Installer, No Help, About, Place to Report Bugs, etc. > ------------------------------------------------------------------ > > Key: JBDS-4407 > URL: https://issues.jboss.org/browse/JBDS-4407 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 11.0.0.GA > > > The DevSuite 1.4 installer has No Help or About links. There are absolutely no clues for the user where to go for help or how to resolve problems. > Note: A version number is shown but only on the first screen. It disappears after you login and is difficult to get back to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24485) Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24485?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24485: ------------------------------- Summary: Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time (was: split release job into two pieces so jbosstools and devstudio can run in parallel to save time) > Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24485 > URL: https://issues.jboss.org/browse/JBIDE-24485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.0.Final > > > Should split release job [1] into two pieces so jbosstools and devstudio can run in parallel to save time. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) Testing: coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Summary: Testing: coretests composite site not updated when publishing to /static and /stable (was: coretests composite site not updated when publishing to /static and /stable) > Testing: coretests composite site not updated when publishing to /static and /stable > ------------------------------------------------------------------------------------ > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: releasework > Fix For: 4.5.0.Final > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3894) Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3894?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3894: ----------------------------- Summary: Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio (was: Refactor discovery plugins/TPs from jbds/jbdevstudio to devstudio) > Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio > --------------------------------------------------------------------- > > Key: JBDS-3894 > URL: https://issues.jboss.org/browse/JBDS-3894 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: central-update, target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM1 > > > In https://github.com/jbosstools/jbosstools-discovery/ we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio and jbds. > Affected: publishing/staging/release scripts, discovery sites, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Summary: Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) (was: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final)) > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > * https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24798) Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24798?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24798: ------------------------------- Summary: Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata) (was: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)) > Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata) > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24798 > URL: https://issues.jboss.org/browse/JBIDE-24798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, build, updatesite > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.1.AM1 > > > After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata). > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Refactoring: get rid of "fullSite", stick with "repository"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19715: ------------------------------- Summary: Refactoring: get rid of "fullSite", stick with "repository" (was: Get rid of "fullSite", stick with "repository") > Refactoring: get rid of "fullSite", stick with "repository" > ----------------------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.1.AM1 > > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Refactoring: get rid of "fullSite", stick with "repository"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19715: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.x) > Refactoring: get rid of "fullSite", stick with "repository" > ----------------------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.1.AM1 > > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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