June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23574) Integration tests global refactoring: org.jboss.tools.cdi.seam3.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23574?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23574: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.cdi.seam3.bot.test > ------------------------------------------------------------------------ > > Key: JBIDE-23574 > URL: https://issues.jboss.org/browse/JBIDE-23574 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: cdi, integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.cdi.seam3.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23571) Integration tests global refactoring: org.jboss.tools.arquillian.ui.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23571?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23571: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.arquillian.ui.bot.test > ---------------------------------------------------------------------------- > > Key: JBIDE-23571 > URL: https://issues.jboss.org/browse/JBIDE-23571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: arquillian, integration, integration-test > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.arquillian.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23577) Integration tests global refactoring: org.jboss.tools.deltaspike.ui.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23577?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23577: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.deltaspike.ui.bot.test > ---------------------------------------------------------------------------- > > Key: JBIDE-23577 > URL: https://issues.jboss.org/browse/JBIDE-23577 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: deltaspike, integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.deltaspike.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23572) Integration tests global refactoring: org.jboss.tools.batch.ui.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23572?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23572: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.batch.ui.bot.test > ----------------------------------------------------------------------- > > Key: JBIDE-23572 > URL: https://issues.jboss.org/browse/JBIDE-23572 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: batch, integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.batch.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23573) Integration tests global refactoring: org.jboss.tools.cdi.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23573?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23573: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.cdi.bot.test > ------------------------------------------------------------------ > > Key: JBIDE-23573 > URL: https://issues.jboss.org/browse/JBIDE-23573 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: cdi, integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.cdi.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23579) Integration tests global refactoring: org.jboss.tools.easymport.ui.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23579?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23579: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.easymport.ui.bot.test > --------------------------------------------------------------------------- > > Key: JBIDE-23579 > URL: https://issues.jboss.org/browse/JBIDE-23579 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: easymport > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.easymport.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23578) Integration tests global refactoring: org.jboss.tools.dummy.ui.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23578?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23578: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.dummy.ui.bot.test > ----------------------------------------------------------------------- > > Key: JBIDE-23578 > URL: https://issues.jboss.org/browse/JBIDE-23578 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.dummy.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23006: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.5.0.Final > > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24439) Block PRs for merge untill the Jenkins build is successful

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24439?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24439: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Block PRs for merge untill the Jenkins build is successful > ---------------------------------------------------------- > > Key: JBIDE-24439 > URL: https://issues.jboss.org/browse/JBIDE-24439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.Final > > > As discussed in this thread [1], we'd like to implement *Protected Branches* and > *Required Status Checks* [2] for some jbosstools-* projects. > [1] http://lists.jboss.org/pipermail/jbosstools-dev/2017-May/011948.html > [2] https://help.github.com/articles/defining-the-mergeability-of-pull-requests/ > We will therefore need to document some requirements in jbosstools-devdoc about how to properly submit PRs when version-bumping is required: > {quote}Make sure if your PR requires a version bump that the PR includes TWO commits. One for the change, and one for the version bump. That way the pair of commits can be built in the PR build and verify it works, AND when cherry picking the commit across branches, you can pick only the change and not the version-bump commit too. > {quote} > And we need to decide if we want to do what Fuse Tools does and require that PRs be reviewed before they can be merged, if we're ready to have that additional overhead on every PR. > [~jeffmaury] as project lead can you state which project(s) you'd like to see changed in github, and which ones should be changed as such: > * jbosstools-_____ > ** Protected Branch = master > ** Required Status Check(s) = ....? (which checks do we want) > ** PR reviews required = [true/false] > From that list of projects / requirements, we can then create subtask JIRAs to track the workj & the changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24020) set better defaults for jbosstools.test.jre.* in parent pom?

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24020?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24020: ------------------------------------ [~nickboldt] should be this one at least resolved ? > set better defaults for jbosstools.test.jre.* in parent pom? > ------------------------------------------------------------ > > Key: JBIDE-24020 > URL: https://issues.jboss.org/browse/JBIDE-24020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.AM1 > > > A few builds, such as jbosstools-server and jbosstools-webservices, rely on some ancient JREs which are not actually available on the machines on which builds or tests are run. > These JREs are defined in the parent pom here: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > Then in Jenkins, the actual paths are defined. > But to run locally & not have tests fail, you therefore need set these via commandline or in your settings.xml file. > So, why not set a better default that works on Windows/Linux/MacOS? How about this? > {code} > -Djbosstools.test.jre.5=${JAVA_HOME} > -Djbosstools.test.jre.6=${JAVA_HOME} > -Djbosstools.test.jre.7=${JAVA_HOME} > -Djbosstools.test.jre.8=${JAVA_HOME}{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017