May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24514) org.jboss.tools.tests version not bumped in master

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24514?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24514: ---------------------------------- Assignee: Nick Boldt > org.jboss.tools.tests version not bumped in master > -------------------------------------------------- > > Key: JBIDE-24514 > URL: https://issues.jboss.org/browse/JBIDE-24514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common, foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > This has been failing for several days. Does no one every compile locally and see these failures? Or check the server for failing builds? [~jeffmaury] [~rob.stryker] > {code} > 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943) > 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:178) > 08:48:11 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > 08:48:11 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > 08:48:11 ... 20 more > 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943) > 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:172) > 08:48:11 ... 22 more{code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Working on a PR to fix this now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1057) Fuse: Fix Project creation test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1057?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1057: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.2.Final) > Fuse: Fix Project creation test > ------------------------------- > > Key: JBTIS-1057 > URL: https://issues.jboss.org/browse/JBTIS-1057 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.1.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.4.3.Final > > > Timeout exceeded -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1057) Fuse: Fix Project creation test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1057?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1057. ------------------------------------ Pushed to master > Fuse: Fix Project creation test > ------------------------------- > > Key: JBTIS-1057 > URL: https://issues.jboss.org/browse/JBTIS-1057 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.1.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.4.3.Final > > > Timeout exceeded -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1115) Fuse: Extend 'FuseProjectTestLong'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1115?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1115: ------------------------------------- Fix Version/s: 4.4.3.Final > Fuse: Extend 'FuseProjectTestLong' > ---------------------------------- > > Key: JBTIS-1115 > URL: https://issues.jboss.org/browse/JBTIS-1115 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.4.3.Final > > > _FuseProjectTest_ has more test methods than _FuseProjectTestLong_. Extend _FuseProjectTestLong_ to be the same as _FuseProjectTest_. > + take into account time needed for test execution (>10 hrs.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1115) Fuse: Extend 'FuseProjectTestLong'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1115?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1115. ------------------------------------ Pushed to master > Fuse: Extend 'FuseProjectTestLong' > ---------------------------------- > > Key: JBTIS-1115 > URL: https://issues.jboss.org/browse/JBTIS-1115 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.4.3.Final > > > _FuseProjectTest_ has more test methods than _FuseProjectTestLong_. Extend _FuseProjectTestLong_ to be the same as _FuseProjectTest_. > + take into account time needed for test execution (>10 hrs.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24514) org.jboss.tools.tests version not bumped in master

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24514: ---------------------------------- Summary: org.jboss.tools.tests version not bumped in master Key: JBIDE-24514 URL: https://issues.jboss.org/browse/JBIDE-24514 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, foundation Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt This has been failing for several days. Does no one every compile locally and see these failures? Or check the server for failing builds? [~jeffmaury] [~rob.stryker] {code} 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943) 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:178) 08:48:11 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) 08:48:11 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) 08:48:11 ... 20 more 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943) 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:172) 08:48:11 ... 22 more{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... Working on a PR to fix this now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24473) Arquillian New and Noteworthy for 4.5.0.AM1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24473?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-24473. ----------------------------------- Resolution: Rejected No changes for N&N. > Arquillian New and Noteworthy for 4.5.0.AM1 > --------------------------------------------------- > > Key: JBIDE-24473 > URL: https://issues.jboss.org/browse/JBIDE-24473 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > > Snjezana Peco, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian 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 Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian 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 Arquillian 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 Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24473) Arquillian New and Noteworthy for 4.5.0.AM1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24473?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-24473. --------------------------------- > Arquillian New and Noteworthy for 4.5.0.AM1 > --------------------------------------------------- > > Key: JBIDE-24473 > URL: https://issues.jboss.org/browse/JBIDE-24473 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > > Snjezana Peco, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian 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 Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian 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 Arquillian 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 Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23784) WF 11 / EAP 7.1 Incremental MGMT publishing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23784?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23784: --------------------------------------- [~rob.stryker], I finally took a look at this and I have a question: How do I tell if incremental deployment is at play here? I tried to deploy a dynamic web project to WF11. Then I added a new jsp file and this was the immediate result of the server console: {code} 13:39:11,370 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /Users/rasp/jbossqa/runtimes/wildfly-11.0.0.Alpha1/standalone/data/content/ae/0320b5903d1dd07069ae74bb950d03400dfa13/content 13:39:11,378 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 68) WFLYUT0022: Unregistered web context: '/dynproj1' from server 'default-server' 13:39:11,400 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment dynproj1.war (runtime-name: dynproj1.war) in 26ms 13:39:11,407 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "dynproj1.war" (runtime-name: "dynproj1.war") 13:39:11,443 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0021: Registered web context: '/dynproj1' for server 'default-server' 13:39:11,466 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0013: Redeployed "dynproj1.war" 13:39:11,467 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /Users/rasp/jbossqa/runtimes/wildfly-11.0.0.Alpha1/standalone/data/content/69/43e98fd2e1031e0028da195332acabc8f3785b/content 13:39:14,724 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /Users/rasp/jbossqa/runtimes/wildfly-11.0.0.Alpha1/standalone/data/content/18/21a534d3e01bf789ee7ef93e35c66ea20b8eeb/content 13:39:14,727 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0022: Unregistered web context: '/dynproj1' from server 'default-server' 13:39:14,734 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment dynproj1.war (runtime-name: dynproj1.war) in 7ms 13:39:14,738 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "dynproj1.war" (runtime-name: "dynproj1.war") 13:39:15,219 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 68) WFLYUT0021: Registered web context: '/dynproj1' for server 'default-server' 13:39:15,228 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0013: Redeployed "dynproj1.war" 13:39:15,230 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /Users/rasp/jbossqa/runtimes/wildfly-11.0.0.Alpha1/standalone/data/content/ae/0320b5903d1dd07069ae74bb950d03400dfa13/content {code} (The first portion is just adding the new jsp file and the second part is when I saved it.) Looking at it it does not seem right to me. It seems that it did an undeploy and then a new deploy. > WF 11 / EAP 7.1 Incremental MGMT publishing > ------------------------------------------- > > Key: JBIDE-23784 > URL: https://issues.jboss.org/browse/JBIDE-23784 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.4.Final, 4.5.0.AM2 > > > WF 11 and EAP 7.1 will have support for management deployment in an incremental fashion. > WF 11 nightly builds for the pre-alpha are here: https://developer.jboss.org/thread/224262 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24500) Create smaller slaves for some integration tests

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24500?page=com.atlassian.jira.plugi... ] Josef Kopriva resolved JBIDE-24500. ----------------------------------- Resolution: Done > Create smaller slaves for some integration tests > ------------------------------------------------ > > Key: JBIDE-24500 > URL: https://issues.jboss.org/browse/JBIDE-24500 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > > Create smaller slaves for some integration tests to save resources on OpenStack. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017