July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22799: --------------------------------------- Here's my first shot at the PR job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... I'm sure it will fail once it starts the tests because I didn't configure the jre properties. But at least I wanna see if it gets there. I will create an experimental PR. > Create integration tests PR check job for server > ------------------------------------------------ > > Key: JBIDE-22799 > URL: https://issues.jboss.org/browse/JBIDE-22799 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24535) itests are not run for server in Jenkins

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24535?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24535. --------------------------------- Tests are now run here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... I created a followup issue for the current failures: JBIDE-24763 > itests are not run for server in Jenkins > ---------------------------------------- > > Key: JBIDE-24535 > URL: https://issues.jboss.org/browse/JBIDE-24535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > I wanted to verify JBIDE-24483 which added itests for incremental deployment via management. But it turns out none of the itests are run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Shouldn't they be run? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1153) Missing Fuse category in Devstudio IS standalone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1153?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1153: --------------------------------- Assignee: Paul Leacu > Missing Fuse category in Devstudio IS standalone installer > ---------------------------------------------------------- > > Key: JBTIS-1153 > URL: https://issues.jboss.org/browse/JBTIS-1153 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: devstudio_vs_devstudiois.png > > > The Devstudio installer contains a category for installing Fuse tooling but Devstudio IS installer doesn't. IMHO the Devstudio IS installer should contain everything from Devstudio, wdyt? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22799: --------------------------------------- Thanks for looking at this, [~nickboldt]. I created a dedicated JIRA for server itests failing: JBIDE-24763 I guess it first needs to work there and then we'll want to run exactly the same tests in the PR check, is that correct, [~rob.stryker]? Or perhaps a subset? What do you think? > Create integration tests PR check job for server > ------------------------------------------------ > > Key: JBIDE-22799 > URL: https://issues.jboss.org/browse/JBIDE-22799 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24763: ---------------------------------- Description: 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 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} > 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 > > 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.2.3#72005)

8 years, 8 months

1
0
0 / 0

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

by Martin Malina (JIRA)

Martin Malina created JBIDE-24763: ------------------------------------- Summary: 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 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} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24454) Configure jbosstools-server project to have test files recognize as such by Sonar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24454?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24454. --------------------------------- The local path is now removed. Closing. > Configure jbosstools-server project to have test files recognize as such by Sonar > --------------------------------------------------------------------------------- > > Key: JBIDE-24454 > URL: https://issues.jboss.org/browse/JBIDE-24454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.4.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > it will avoid to have "Define and throw a dedicated exception instead of using a generic one." issues reported on test methods for which it is perfectly normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1154) SY - Apply oxygen changes in debugger tests

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1154: ---------------------------------------- Summary: SY - Apply oxygen changes in debugger tests Key: JBTIS-1154 URL: https://issues.jboss.org/browse/JBTIS-1154 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE, switchyard Affects Versions: 4.5.0.CR2 Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.5.0.CR2 The known Oxygen change, again :( {code} OK -> Apply and Close {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1152) Update Drools tests for the new devstudio Drools plugin - 7.0.1.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1152?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1152: ------------------------------------- Affects Version/s: 4.5.0.CR2 (was: 11.0.0.CR2) > Update Drools tests for the new devstudio Drools plugin - 7.0.1.Final > --------------------------------------------------------------------- > > Key: JBTIS-1152 > URL: https://issues.jboss.org/browse/JBTIS-1152 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.5.0.CR2 > Environment: DevstudioIS 11.0.0.CR2 > Drools plugin 7.0.1.Final > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.5.0.CR2 > > > The version of drools plugin contains some fixes and the new version of devstudio brings some changes which have to be updated in current drools plugin tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1152) Update Drools tests for the new devstudio Drools plugin - 7.0.1.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1152?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1152. ------------------------------------ Pushed to master > Update Drools tests for the new devstudio Drools plugin - 7.0.1.Final > --------------------------------------------------------------------- > > Key: JBTIS-1152 > URL: https://issues.jboss.org/browse/JBTIS-1152 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.5.0.CR2 > Environment: DevstudioIS 11.0.0.CR2 > Drools plugin 7.0.1.Final > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.5.0.CR2 > > > The version of drools plugin contains some fixes and the new version of devstudio brings some changes which have to be updated in current drools plugin tests. -- 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 July 2017