June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24518) change github check frequency for CI builds from 8hrs to 20 mins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24518?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24518: ---------------------------------- Assignee: Nick Boldt > change github check frequency for CI builds from 8hrs to 20 mins > ---------------------------------------------------------------- > > Key: JBIDE-24518 > URL: https://issues.jboss.org/browse/JBIDE-24518 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Currently the jbosstools-* component project builds run every 8hrs, with a nightly buildflow also triggering a rebuild. But since breaking changes are frequently NOT fixed quickly enough as devs cannot or will not kick their own builds, we need to implement a better strategy to check github for changes more often. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24519) Ensure SAP tooling is available from within JBT/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24519?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24519: ------------------------------- Fix Version/s: 4.5.0.AM1 > Ensure SAP tooling is available from within JBT/devstudio > ---------------------------------------------------------- > > Key: JBIDE-24519 > URL: https://issues.jboss.org/browse/JBIDE-24519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Fix For: 4.5.0.AM1 > > > Need to make sure that whatever magic happens today in the IS for supporting the SAP Tooling gets migrated to JBT/devstudio. > {quote} > Github = https://github.com/jbosstools/jbosstools-fuse-extras > CCI PR Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > CCI Update SIte Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > Update Site CI: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1126) Use existing RedDeer implementation for opening views/preferences/editors

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1126?page=com.atlassian.jira.plugin... ] Tomáš Sedmík closed JBTIS-1126. ------------------------------- PR was pushed to master > Use existing RedDeer implementation for opening views/preferences/editors > ------------------------------------------------------------------------- > > Key: JBTIS-1126 > URL: https://issues.jboss.org/browse/JBTIS-1126 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.3.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Priority: Blocker > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24465) OpenShift New and Noteworthy for 4.5.0.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24465?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24465: ------------------------------- Fix Version/s: 4.5.0.AM1 > OpenShift New and Noteworthy for 4.5.0.AM1 > --------------------------------------------------- > > Key: JBIDE-24465 > URL: https://issues.jboss.org/browse/JBIDE-24465 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.0.AM1 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift 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 OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift 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 OpenShift 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 OpenShift 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] (ERT-511) com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-511?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-511. --------------------------------- Resolution: Done > com.google.javascript and com.google.guava plugins not added to org.eclipse.wst.jsdt.feature [EBZ#517659] > --------------------------------------------------------------------------------------------------------- > > Key: ERT-511 > URL: https://issues.jboss.org/browse/ERT-511 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.9_RC3, General, bzira > Fix For: Oxygen (4.7) RC3 > > > com.google.javascript and com.google.guava plugins are required by org.eclipse.wst.jsdt.core plugin but not added to org.eclipse.wst.jsdt.feature. > The unsatisfied p2 requirements result in p2 install error. This should be fixed in WTP 3.9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1128) Cannot install Integration Stack using a standalone installer

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1128: ---------------------------------------- Summary: Cannot install Integration Stack using a standalone installer Key: JBTIS-1128 URL: https://issues.jboss.org/browse/JBTIS-1128 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 11.0.0.AM1 Environment: devstudio-integration-stack-11.0.0.AM1-SNAPSHOT-standalone-installer.jar Reporter: Andrej Podhradsky Priority: Blocker I'm getting the following error {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Integration and SOA Development 11.0.0.AM1-SNAPSHOT-v20170608-1902-B13 (com.jboss.devstudio.integration-stack.soa.feature.feature.group 11.0.0.AM1-SNAPSHOT-v20170608-1902-B13) Missing requirement: Fuse Project Plugin 10.0.0.v20170523-0654 (org.fusesource.ide.project 10.0.0.v20170523-0654) requires 'bundle org.sonatype.tycho.m2e 0.8.1' but it could not be found Cannot satisfy dependency: From: JBoss Integration and SOA Development 11.0.0.AM1-SNAPSHOT-v20170608-1902-B13 (com.jboss.devstudio.integration-stack.soa.feature.feature.group 11.0.0.AM1-SNAPSHOT-v20170608-1902-B13) To: org.switchyard.tools.feature.feature.group 0.0.0 Cannot satisfy dependency: From: JBoss Fuse Tooling Apache Camel Editor 10.0.0.v20170526-0921 (org.fusesource.ide.camel.editor.feature.feature.group 10.0.0.v20170526-0921) To: org.fusesource.ide.project [10.0.0.v20170523-0654] Cannot satisfy dependency: From: SwitchYard 2.4.0.CI-v20170605-1802-B12 (org.switchyard.tools.feature.feature.group 2.4.0.CI-v20170605-1802-B12) To: org.fusesource.ide.camel.editor.feature.feature.group [10.0.0,11.0.0) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1127) Remove org.springframework.aspects and org.springframework.osgi from the IS TP

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1127: --------------------------------- Summary: Remove org.springframework.aspects and org.springframework.osgi from the IS TP Key: JBTIS-1127 URL: https://issues.jboss.org/browse/JBTIS-1127 Project: JBoss Tools Integration Stack Issue Type: Task Components: target-platform Affects Versions: 4.5.0.AM1-TP Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.5.0.AM1-TP remove {code} <unit id="org.springframework.aspects" version="3.1.4.RELEASE"/> <unit id="org.springframework.osgi.core" version="1.2.1"/> <unit id="org.springframework.osgi.extender" version="1.2.1"/> <unit id="org.springframework.osgi.extensions.annotations" version="1.2.1"/> <unit id="org.springframework.osgi.io" version="1.2.1"/> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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: ------------------------------------ [~nickboldt], I know that it's easy to define (and override) the settings in the root pom of the given folder-of-tests. However it's a bit unpractical, because with every change in the settings (plugin customization, some special property etc) we will need to maintain the settings in multiple places. Which is not much desired. We were thinking if maybe we can use maven phases and set different settings based on the phase. Not sure if that is even possible, will need to investigate a bit. [~rob.stryker] I do not assume all UI / reddeer tests are integration tests. But I assume that the reddeer tests run with useUIThread = false. However your junit tests probably useUIThread = true. I haven't checked that in your (AS) plugins. But it's the case in e.g. hibernate tests. > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24481) Deploy Image wizard: new project is not selected nor available in projects combo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24481?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24481: ------------------------------------------ fix works for me, merged into master. > Deploy Image wizard: new project is not selected nor available in projects combo > -------------------------------------------------------------------------------- > > Key: JBIDE-24481 > URL: https://issues.jboss.org/browse/JBIDE-24481 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24140?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-24140: ------------------------------------- Assignee: Jeff MAURY (was: Ondrej Dockal) > Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24140 > URL: https://issues.jboss.org/browse/JBIDE-24140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.4.4.Final > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:* > http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig 0.56 sec 5 > org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments 15 ms 11 > {code} > {code} > Failed > org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments (from org.jboss.tools.jst.web.test.JstWebAllTests) > Failing for the past 11 builds (Since #69 ) > Took 15 ms. > add description > Error Message > Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9 > Stacktrace > junit.framework.AssertionFailedError: Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9 > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:200) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:413) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:409) > at org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments(WebXMLValidationTest.java:55){code} > {code} > Failed > org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig (from org.jboss.tools.jst.web.test.JstWebAllTests) > Failing for the past 5 builds (Since Unstable#75 ) > Took 0.56 sec. > add description > Stacktrace > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig(WebXMLValidationTest.java:103){code} -- 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 June 2017