May 2017 - jbosstools-issues - Jboss List Archives

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23574?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23574: ---------------------------------- Assignee: Jeff MAURY > 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.AM1 > > > 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)

8 years, 10 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23573?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23573: ---------------------------------- Assignee: Jeff MAURY > 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.AM1 > > > 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)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23567) Integration tests global refactoring

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23567?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23567: ---------------------------------- Assignee: Jeff MAURY > Integration tests global refactoring > ------------------------------------ > > Key: JBIDE-23567 > URL: https://issues.jboss.org/browse/JBIDE-23567 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration-test, integration_tests > Fix For: 4.4.4.Final > > > We should done some work on integration tests so that we can rely on them to improve our code quality and reduce the technical debt. > A sprint will be dedicated. > Here are the tasks we should work on: > * run tests from Maven and document how to run them if specific steps are required > * If failure, fix the failed tests > * Refactor / move tests to the components repository > * Fix/make sure tests are run in PR check > This huge task should be done component per component. Sub-tasks JIRA will be created for each component. > You can use this document as a starting point:[https://docs.google.com/document/d/1bl8pJ2aW65UpyGpr3qxoAUREDWL26N... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1098) Update Neon Target Platform to fix stand-alone installers

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1098?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1098. ------------------------------------ Verified with the standalone installers - devstudio-integration-stack-10.3.0.CR2-standalone-installer.jar - devstudio-integration-stack-10.3.0.CR2-fuse-tooling-installer.jar - devstudio-integration-stack-10.3.0.CR2-fuse-installer-runtime.jar > Update Neon Target Platform to fix stand-alone installers > --------------------------------------------------------- > > Key: JBTIS-1098 > URL: https://issues.jboss.org/browse/JBTIS-1098 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.3.CR1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.4.3.CR2-TP > > > *Reason:* The standalone installers fail because > <unit id="org.sonatype.tycho.m2e.feature.feature.group" version="0.8.1.201704211436"/> > has been pushed down to the Devstudio core TP. We need it back (duplicated) to get the standalone installer sto be stand-alone. > *Project page/sources:* m2eclipse-tycho > *Version:* .0.8.1 > *License and owner:* EPL > *Original p2 repo:* http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho... > *JBoss mirror:* same > *Include Sources:* Yes > *Affected JBoss Tools components:* .IS > *Include in JBDS:* Yes DevstudioIS > *Type of dependency:* |distribution > *List of bundles added/removed:* > {code} >  > <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type=" > InstallableUnit"> > <unit id="org.sonatype.tycho.m2e.feature.feature.group" version="0.8.1.201704211436"/> > <repository id="jbt-m2eclipse-tycho" location="http://download.jboss.org/jbosstools/updates/requirements/m2eclips > e-tycho/"/> > </location> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1108) JBTIS 4.4.3.CR1 refers to JBTIS TP 4.4.3.CR1 instead of 4.4.3.CR2

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1108?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1108. ------------------------------------ Verified. Now, the composite files refer to 4.4.3.Final-SNAPSHOT. > JBTIS 4.4.3.CR1 refers to JBTIS TP 4.4.3.CR1 instead of 4.4.3.CR2 > ----------------------------------------------------------------- > > Key: JBTIS-1108 > URL: https://issues.jboss.org/browse/JBTIS-1108 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.4.3.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 4.4.3.CR1 > > > The file at http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... contains > {code} > <children size="2"> >  > <child location="4.4.3.CR1/"/> > <child location="../../../../targetplatforms/jbtistarget/4.4.3.CR1/jbtis/REPO/"/> > </children> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1101) Cannot install reddeer feature

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1101?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1101. ------------------------------------ Verified with Devstudio IS 10.3.0.CR2 > Cannot install reddeer feature > ------------------------------ > > Key: JBTIS-1101 > URL: https://issues.jboss.org/browse/JBTIS-1101 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.3.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 4.4.2.Final-SNAPSHOT-TP > > > The following feature cannot be installed > - org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final > The error is > {code} > Your original request has been modified. > "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed. > Cannot complete the install because one or more required items could not be found. > Software being installed: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final) > Missing requirement: RedDeer GEF Component 1.2.1.Final (org.jboss.reddeer.gef 1.2.1.Final) requires 'bundle org.jboss.reddeer.workbench [1.2.0,1.3.0)' but it could not be found > Cannot satisfy dependency: > From: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final) > To: org.jboss.reddeer.gef [1.2.1.Final] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24449) Make sure that we can run helloworld-msa

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24449?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24449: ------------------------------------- Sprint: devex #132 May 2017 > Make sure that we can run helloworld-msa > ---------------------------------------- > > Key: JBIDE-24449 > URL: https://issues.jboss.org/browse/JBIDE-24449 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.0.Final > > > [helloworld-msa|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-ms...], the reference architecture that Red Hat publicizes is currently using the cmd-line (aka oc). We should make sure that one can run [helloworld-msa|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-ms...] from our tooling. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24445) OpenShift server adapter is not working, when rsync is not on path (Upstream issue)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24445?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24445: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > OpenShift server adapter is not working, when rsync is not on path (Upstream issue) > ----------------------------------------------------------------------------------- > > Key: JBIDE-24445 > URL: https://issues.jboss.org/browse/JBIDE-24445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.4.Final > Environment: Windows 10 > Reporter: Radim Hopp > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > Using server adapter, when rsync is not on path results in errors like: > {noformat} > Could not sync C:\Users\jbossqa\rhopp\workspace-sidnfiweun\.metadata\.plugins\org.jboss.ide.eclipse.as.core\dfgdfg@eap-app\deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Download cwRsync for Windows and add it to your PATH. > Ignoring the following flags because they only apply to rsync: --exclude > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: command terminated with exit code 2 > {noformat} > More info in upstream issue: https://github.com/openshift/origin/issues/14075 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24445) OpenShift server adapter is not working, when rsync is not on path (Upstream issue)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24445?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24445: ------------------------------------- Fix Version/s: 4.5.0.AM1 > OpenShift server adapter is not working, when rsync is not on path (Upstream issue) > ----------------------------------------------------------------------------------- > > Key: JBIDE-24445 > URL: https://issues.jboss.org/browse/JBIDE-24445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.4.Final > Environment: Windows 10 > Reporter: Radim Hopp > Fix For: 4.5.0.AM1 > > > Using server adapter, when rsync is not on path results in errors like: > {noformat} > Could not sync C:\Users\jbossqa\rhopp\workspace-sidnfiweun\.metadata\.plugins\org.jboss.ide.eclipse.as.core\dfgdfg@eap-app\deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Download cwRsync for Windows and add it to your PATH. > Ignoring the following flags because they only apply to rsync: --exclude > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: command terminated with exit code 2 > {noformat} > More info in upstream issue: https://github.com/openshift/origin/issues/14075 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24449) Make sure that we can run helloworld-msa

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24449?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24449: ------------------------------------- Issue Type: Epic (was: Feature Request) Epic Name: Make sure we can run helloworld-msa Epic Status: To Do > Make sure that we can run helloworld-msa > ---------------------------------------- > > Key: JBIDE-24449 > URL: https://issues.jboss.org/browse/JBIDE-24449 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.0.Final > > > [helloworld-msa|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-ms...], the reference architecture that Red Hat publicizes is currently using the cmd-line (aka oc). We should make sure that one can run [helloworld-msa|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-ms...] from our tooling. -- 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