June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24561: ------------------------------- Fix Version/s: 4.5.0.AM1 > Checking console output takes 80 mins? > -------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24561: ---------------------------------- Summary: Checking console output takes 80 mins? Key: JBIDE-24561 URL: https://issues.jboss.org/browse/JBIDE-24561 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, target-platform Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt Description setter plugin seems to take 80 mins to parse the console log. So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! {code} 10:05:56 Terminating xvnc. 10:05:56 $ /usr/bin/vncserver -kill :33 10:05:57 Killing Xvnc process ID 9997 10:05:59 Archiving artifacts 10:05:59 Checking console output 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... {code} 10:04:53 Terminating xvnc. 10:04:53 $ /usr/bin/vncserver -kill :35 10:04:54 Killing Xvnc process ID 9993 10:04:56 Archiving artifacts 10:04:57 Checking console output 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24560) Server adapter very slow to restart in debug

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24560?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24560: ---------------------------------- Assignee: Andre Dietisheim > Server adapter very slow to restart in debug > --------------------------------------------- > > Key: JBIDE-24560 > URL: https://issues.jboss.org/browse/JBIDE-24560 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > When the server adapter has been created and just started, if you restart in debug, it is very slow to restart. It seems to happen only the first time after you created it and started. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24457) Hibernate New and Noteworthy for 4.5.0.AM1

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24457?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-24457: ---------------------------------------- Assignee: Dmitrii Bocharov (was: Koen Aers) > Hibernate New and Noteworthy for 4.5.0.AM1 > --------------------------------------------------- > > Key: JBIDE-24457 > URL: https://issues.jboss.org/browse/JBIDE-24457 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Priority: Critical > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24455 #comment Create N&N for Hibernate 4.5.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4440?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4440: ---------------------------------- JBDS TP is now 822M as it includes sources. https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > Add sources to the JBDS target platform > --------------------------------------- > > Key: JBDS-4440 > URL: https://issues.jboss.org/browse/JBDS-4440 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: p2diff_JBT_JBDS_TPs.txt, p2diff_JBT_JBDS_TPs_filtered.txt > > > We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. > Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. > I will ask people at jbosstools-dev for their opinions. > CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24560) Server adapter very slow to restart in debug

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24560?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24560: ------------------------------- Steps to Reproduce: 1. Create the server adapter 2. Once started, restart it in debug mode. It will take a long time to appear in debug mode 3. Restart it in run mode 4. Restart it in debug mode. This time, it will take less time to appear in debug mode > Server adapter very slow to restart in debug > --------------------------------------------- > > Key: JBIDE-24560 > URL: https://issues.jboss.org/browse/JBIDE-24560 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > When the server adapter has been created and just started, if you restart in debug, it is very slow to restart. It seems to happen only the first time after you created it and started. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24560) Server adapter very slow to restart in debug

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-24560: ---------------------------------- Summary: Server adapter very slow to restart in debug Key: JBIDE-24560 URL: https://issues.jboss.org/browse/JBIDE-24560 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.Final Reporter: Jeff MAURY Fix For: 4.5.0.AM2 When the server adapter has been created and just started, if you restart in debug, it is very slow to restart. It seems to happen only the first time after you created it and started. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24244) add fuse tools features to JBT core, coretests, integration-tests update sites (as appropriate)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24244?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24244. -------------------------------- Verified, update sites \[1\] & \[2\] contains all features listed in Fuse category.xml \[3\]. \[1\] http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ \[2\] https://devstudio.jboss.com/11/snapshots/updates/ \[3\] https://github.com/jbosstools/jbosstools-fuse/blob/master/site/category.xml > add fuse tools features to JBT core, coretests, integration-tests update sites (as appropriate) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24244 > URL: https://issues.jboss.org/browse/JBIDE-24244 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > Attachments: fuse-in-jbt.png > > > Need a list of features to include in JBT, and how to categorize them. > See: > * See https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... for Core site > * See https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... for Core tests site > * See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... for integration tests site -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24547: ------------------------------------ +1 for running ITests through the profile and not by default > Refactor ITests settings in parent pom > -------------------------------------- > > Key: JBIDE-24547 > URL: https://issues.jboss.org/browse/JBIDE-24547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.0.AM1 > > > It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ). > The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-24547: ------------------------------------ I also like the second option more, PR #255. Let's see what [~jeffmaury] has to say. > Refactor ITests settings in parent pom > -------------------------------------- > > Key: JBIDE-24547 > URL: https://issues.jboss.org/browse/JBIDE-24547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.0.AM1 > > > It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ). > The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017