October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25265) parent pom should set skipTestsWithPrivateRequirements based on true/false nature of skipTestsOrITests and skipPrivateRequirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25265?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25265: ---------------------------------- Assignee: Nick Boldt > parent pom should set skipTestsWithPrivateRequirements based on true/false nature of skipTestsOrITests and skipPrivateRequirements > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25265 > URL: https://issues.jboss.org/browse/JBIDE-25265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.Final > > > Purpose: > when skipTests=true or skipITests=true or skipPrivateRequirements=true, don't download EAP runtimes. > Implementation: > https://github.com/jbosstools/jbosstools-build/pull/264 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25233) Docker New and Noteworthy for 4.5.1.Final

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25233?page=com.atlassian.jira.plugi... ] Jeff Johnston closed JBIDE-25233. --------------------------------- Resolution: Rejected 4.5.1.Final contains only bug-fixes for Docker and an updated Test base. > Docker New and Noteworthy for 4.5.1.Final > ----------------------------------------------------- > > Key: JBIDE-25233 > URL: https://issues.jboss.org/browse/JBIDE-25233 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Labels: task > Fix For: 4.5.1.Final > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker 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 Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker 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-25230 #comment Create N&N for Docker 4.5.1.Final #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 Docker for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.1.Final since the AM3 release of Docker, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.1.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.1.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24897: ------------------------------------ As soon as someone contributes a PR for the update sites and discovery plugins, it can be added to Central's Early Access site. Did we ever get a +1 from [~jeffmaury] or [~rpdavis] to include it? I don't recall seeing that statement in MM, IRC, on a call, or via email, but might have missed it. > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.Final > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4590) Provide Development Suite Installer for Linux

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4590?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4590: ----------------------------- Component/s: rpm upstream > Provide Development Suite Installer for Linux > --------------------------------------------- > > Key: JBDS-4590 > URL: https://issues.jboss.org/browse/JBDS-4590 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer, rpm, upstream > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 11.x > > > it will be nice to have the installer also for Linux. it will allow to provide the same easy installation instructions for all platforms. > (currently a blocker to mention usage of Dev Suite installer on hello-world page for Fuse) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4590) Provide Development Suite Installer for Linux

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4590?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4590 at 10/17/17 12:21 PM: ------------------------------------------------------------- Fuse is currently an OPTIONAL install in the installer jar and in the devsuite installer, but has not been added to the devstudio rpm as that would make it a REQUIRED install. We could concoct a second rpm for that if there's a need for it. [~aurelien.pupier] if this is what you're requesting, please get approval from [~rpdavis] and/or [~jeffmaury] and I can create an RPM for fuse. I think it's possible to generate two RPMs from the same spec file, which would be the ideal implementation here so rh-eclipse47-devstudio and rh-eclipse47-fusetools could be built together. That said I don't know how much work would be involved in wrapping the Fuse *server* options with RPMs. was (Author: nickboldt): Fuse is currently an OPTIONAL install in the installer jar and in the devsuite installer, but has not been added to the devstudio rpm as that would make it a REQUIRED install. We could concoct a second rpm for that if there's a need for it. [~aurelien.pupier] if this is what you're requesting, please get approval from [~rpdavis] and/or [~jeffmaury] and I can create an RPM for fuse. I think it's possible to generate two RPMs from the same spec file, which would be the ideal implementation here so rh-eclipse47-devstudio and rh-eclipse47-fusetools could be built together. > Provide Development Suite Installer for Linux > --------------------------------------------- > > Key: JBDS-4590 > URL: https://issues.jboss.org/browse/JBDS-4590 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 11.x > > > it will be nice to have the installer also for Linux. it will allow to provide the same easy installation instructions for all platforms. > (currently a blocker to mention usage of Dev Suite installer on hello-world page for Fuse) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4590) Provide Development Suite Installer for Linux

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4590?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4590: ----------------------------- Fix Version/s: 11.x > Provide Development Suite Installer for Linux > --------------------------------------------- > > Key: JBDS-4590 > URL: https://issues.jboss.org/browse/JBDS-4590 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 11.x > > > it will be nice to have the installer also for Linux. it will allow to provide the same easy installation instructions for all platforms. > (currently a blocker to mention usage of Dev Suite installer on hello-world page for Fuse) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4590) Provide Development Suite Installer for Linux

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4590?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4590: ---------------------------------- Fuse is currently an OPTIONAL install in the installer jar and in the devsuite installer, but has not been added to the devstudio rpm as that would make it a REQUIRED install. We could concoct a second rpm for that if there's a need for it. [~aurelien.pupier] if this is what you're requesting, please get approval from [~rpdavis] and/or [~jeffmaury] and I can create an RPM for fuse. I think it's possible to generate two RPMs from the same spec file, which would be the ideal implementation here so rh-eclipse47-devstudio and rh-eclipse47-fusetools could be built together. > Provide Development Suite Installer for Linux > --------------------------------------------- > > Key: JBDS-4590 > URL: https://issues.jboss.org/browse/JBDS-4590 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Aurélien Pupier > Assignee: Denis Golovin > > it will be nice to have the installer also for Linux. it will allow to provide the same easy installation instructions for all platforms. > (currently a blocker to mention usage of Dev Suite installer on hello-world page for Fuse) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24763: -------------------------------- Description: Here's the job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... Just keep checking it and running it until something works... ... I guess was: Here's the job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Currently we got around 30 failures: {code} All Failed Tests Test Name Duration Age org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 {code} Nick already shared some details in JBIDE-22799 > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: server-itests.png > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > Just keep checking it and running it until something works... ... I guess -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24763: ------------------------------------- The job to check is this one: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... All other job links seem to be deprecated. > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: server-itests.png > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Currently we got around 30 failures: > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 > org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 > org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 > {code} > Nick already shared some details in JBIDE-22799 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23868) Fix jbt-server otherOS test cases: take 2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23868?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-23868. ------------------------------- Resolution: Duplicate Issue Closing as duplicate > Fix jbt-server otherOS test cases: take 2 > ----------------------------------------- > > Key: JBIDE-23868 > URL: https://issues.jboss.org/browse/JBIDE-23868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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