March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4313) Show Installer window when content is loaded and ready

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4313?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4313: -------------------------------- Description: When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. !DevSuite Installer-Window Loading Before.mp4! !DevSuite Installer-Window Loading After.mp4! was: When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. ! > Show Installer window when content is loaded and ready > ------------------------------------------------------ > > Key: JBDS-4313 > URL: https://issues.jboss.org/browse/JBDS-4313 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.AM2 > > Attachments: DevSuite Installer-Window Loading After.mp4, DevSuite Installer-Window Loading Before.mp4 > > > When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. > !DevSuite Installer-Window Loading Before.mp4! !DevSuite Installer-Window Loading After.mp4! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4313) Show Installer window when content is loaded and ready

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4313?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4313: -------------------------------- Description: When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. ! was:When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. > Show Installer window when content is loaded and ready > ------------------------------------------------------ > > Key: JBDS-4313 > URL: https://issues.jboss.org/browse/JBDS-4313 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.AM2 > > Attachments: DevSuite Installer-Window Loading After.mp4, DevSuite Installer-Window Loading Before.mp4 > > > When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. > ! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1050) Move MWQE Jenkins jobs to Central CI

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1050?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1050: ----------------------------------- # Completed job transfers: https://devstudiois-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/JBTISTarg... https://devstudiois-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/JBTISTPNo... > Move MWQE Jenkins jobs to Central CI > ------------------------------------ > > Key: JBTIS-1050 > URL: https://issues.jboss.org/browse/JBTIS-1050 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > > The middleware Jenkins jobs need to be migrated to Central CI > https://mojo.redhat.com/groups/mw-qe-central-ci-migration > ref: @lucinka > From Nick: > I'm also working on a migrateJob.sh script which makes it easier to > copy & modify a job so that migration isn't so manual a process. > It generates a stub job on the CCI server based on a template, then > downloads the config.xml and replaces it with the old job from Bos MW > Jenkins. But before pushing it back to CCI, it applies some sed > transforms to fix things like JDK name, Maven name, label expression / > assignedNode (we don't have "RHEL6" or "RHEL7" on CCI, only rhel7 and > "rhel7-devstudio-releng" slaves... plus some windows and OSX ones for > ITests). It's not 100% working yet but it's better than doing the work > by hand. > https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/migrat... > It requires that you compile and run my jenkins sync/publisher mojos > [1],[2], which are wrapped with my hacky hud{push,pull}*.sh scripts > (they're just simplifications to be able to push/pull job configs w/ > less typing). So it's a bit of a kludge at the moment but I can walk > you through set up if you're ready to start migrating. Or you can wait > until I'm done.) > [1] https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... > [2] https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-publish... > --- > Work in progress: > https://issues.jboss.org/browse/JBDS-4233 and > http://etherpad.corp.redhat.com/nboldt-status > MOJO doc: > https://mojo.redhat.com/docs/DOC-1099087#comment-1053465 > Central CI migration sync call on Wednesdays (every 4 weeks). I just > go as fly on the wall. > * Blue Jeans: https://bluejeans.com/327849748 > * Meeting agenda/log: http://etherpad.corp.redhat.com/fb2t56DJnX > * Mojo: https://mojo.redhat.com/groups/mw-qe-central-ci-migration > * ML: mw-scale-ci(a)redhat.com -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1058) Update conflicting repo ID in the 4.4.2 TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1058?page=com.atlassian.jira.plugin... ] Paul Leacu resolved JBTIS-1058. ------------------------------- Fix Version/s: 4.4.3.CR1-TP Resolution: Done This can be verified by looking at https://origin-repository.jboss.org/nexus/content/repositories/snapshots/... But we'll be updating that again for the latest core 4.4.4. > Update conflicting repo ID in the 4.4.2 TP > ------------------------------------------ > > Key: JBTIS-1058 > URL: https://issues.jboss.org/browse/JBTIS-1058 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 4.4.2.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.4.3.CR1-TP > > > from the build log > 14:51:12 [WARNING] p2 repository with URL http://download.jboss.org/jbosstools/neon/stable/updates/core is associated with multiple IDs; was 'jbt-core-4.4.2.Final', now is 'jbt-core-4.4.3.Final' > 14:51:12 [WARNING] p2 repository with URL http://download.jboss.org/jbosstools/neon/stable/updates/core is associated with multiple IDs; was 'jbt-core-4.4.3.Final', now is 'jbt-core-4.4.2.Final' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4313) Show Installer window when content is loaded and ready

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4313?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4313: -------------------------------- Attachment: DevSuite Installer-Window Loading After.mp4 DevSuite Installer-Window Loading Before.mp4 > Show Installer window when content is loaded and ready > ------------------------------------------------------ > > Key: JBDS-4313 > URL: https://issues.jboss.org/browse/JBDS-4313 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.AM2 > > Attachments: DevSuite Installer-Window Loading After.mp4, DevSuite Installer-Window Loading Before.mp4 > > > When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24079) baseline check should be bound to package phase

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24079?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24079. ------------------------------ Resolution: Rejected Since it breaks builds that rely on baseline check, and since no real reason for WHY this was requested was provided, I'm closing this as rejected until explanation and better PR can be provided. > baseline check should be bound to package phase > ----------------------------------------------- > > Key: JBIDE-24079 > URL: https://issues.jboss.org/browse/JBIDE-24079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, check > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > The baseline check is currently bound to the verify phase. It would be more convenient to have it bound to the package phase. I think this can be done in the parent POM, not using the default phase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4313) Show Installer window when content is loaded and ready

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4313?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4313: -------------------------------- Attachment: (was: Sprint-129-installer-window-loading-after.flv) > Show Installer window when content is loaded and ready > ------------------------------------------------------ > > Key: JBDS-4313 > URL: https://issues.jboss.org/browse/JBDS-4313 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.AM2 > > > When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4313) Show Installer window when content is loaded and ready

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4313?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4313: -------------------------------- Attachment: Sprint-129-installer-window-loading-after.flv > Show Installer window when content is loaded and ready > ------------------------------------------------------ > > Key: JBDS-4313 > URL: https://issues.jboss.org/browse/JBDS-4313 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.AM2 > > > When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24079) baseline check should be bound to package phase

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24079?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24079: ------------------------------------ Must revert this change as it breaks builds -- need to ensure ALL packaging steps are done before doing these checks. "JBIDE-24079 bind baseline check and enforcer checks to package phase" > baseline check should be bound to package phase > ----------------------------------------------- > > Key: JBIDE-24079 > URL: https://issues.jboss.org/browse/JBIDE-24079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, check > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > The baseline check is currently bound to the verify phase. It would be more convenient to have it bound to the package phase. I think this can be done in the parent POM, not using the default phase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24079) baseline check should be bound to package phase

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24079?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24079: ------------------------------------ Must revert this change as it breaks builds -- need to ensure ALL packaging steps are done before doing these checks. "JBIDE-24079 bind baseline check and enforcer checks to package phase" > baseline check should be bound to package phase > ----------------------------------------------- > > Key: JBIDE-24079 > URL: https://issues.jboss.org/browse/JBIDE-24079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, check > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > The baseline check is currently bound to the verify phase. It would be more convenient to have it bound to the package phase. I think this can be done in the parent POM, not using the default phase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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