October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23029: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.Final) > Integration tests: Tests should be able to run individually > ----------------------------------------------------------- > > Key: JBIDE-23029 > URL: https://issues.jboss.org/browse/JBIDE-23029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.2.AM3 > > > We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need). > This is even more true since running the whole suite is a lengthy task. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-956) Update the pom.xml to contain only neccessary versions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-956?page=com.atlassian.jira.plugin.... ] Jozef Marko resolved JBTIS-956. ------------------------------- Fix Version/s: 4.4.0.Alpha2-TP Resolution: Done Please include also into jbtis-4.3.0 > Update the pom.xml to contain only neccessary versions > ------------------------------------------------------ > > Key: JBTIS-956 > URL: https://issues.jboss.org/browse/JBTIS-956 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Alpha2-TP > > > Currently the pom.xml contains declaration of versions which are in fact overridden by versions declared in integration stack update site. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-956) Update the pom.xml to contain only neccessary versions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-956?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-956: ------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/826 > Update the pom.xml to contain only neccessary versions > ------------------------------------------------------ > > Key: JBTIS-956 > URL: https://issues.jboss.org/browse/JBTIS-956 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Jozef Marko > > Currently the pom.xml contains declaration of versions which are in fact overridden by versions declared in integration stack update site. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4138) Remove setting VAGRANT_DETECTED_OS from vagrant setup

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4138?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4138: ------------------------------ Affects Version/s: 10.2.0.AM3 (was: 10.3.0.AM1) > Remove setting VAGRANT_DETECTED_OS from vagrant setup > ----------------------------------------------------- > > Key: JBDS-4138 > URL: https://issues.jboss.org/browse/JBDS-4138 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > > In vagrant setup the installer calls > {code}setx VAGRANT_DETECTED_OS "cygwin"{code} > We can remove that since the very same code is run in cdk setup and it isn't really necessary unless cdk is being installed anyway. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-956) Update the pom.xml to contain only neccessary versions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-956?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-956: ------------------------------ Description: Currently the pom.xml contains declaration of versions which are in fact overridden by versions declared in integration stack update site. > Update the pom.xml to contain only neccessary versions > ------------------------------------------------------ > > Key: JBTIS-956 > URL: https://issues.jboss.org/browse/JBTIS-956 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Jozef Marko > > Currently the pom.xml contains declaration of versions which are in fact overridden by versions declared in integration stack update site. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-956) Update the pom.xml to contain only neccessary versions

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-956: --------------------------------- Summary: Update the pom.xml to contain only neccessary versions Key: JBTIS-956 URL: https://issues.jboss.org/browse/JBTIS-956 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPMN2, QE Affects Versions: 4.4.0.Alpha1, 4.3.0.Final Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4138) Remove setting VAGRANT_DETECTED_OS from vagrant setup

by Jan Richter (JIRA)

Jan Richter created JBDS-4138: --------------------------------- Summary: Remove setting VAGRANT_DETECTED_OS from vagrant setup Key: JBDS-4138 URL: https://issues.jboss.org/browse/JBDS-4138 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: platform-installer Affects Versions: 10.3.0.AM1 Reporter: Jan Richter Assignee: Denis Golovin Priority: Minor In vagrant setup the installer calls {code}setx VAGRANT_DETECTED_OS "cygwin"{code} We can remove that since the very same code is run in cdk setup and it isn't really necessary unless cdk is being installed anyway. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4136) Uses constraint violation - org.slf4j.api vs. slf4j.api

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4136?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4136: ---------------------------------- Package name remains the same, but bundle name was changed in slf4j on April 10, 2015: http://jira.qos.ch/browse/SLF4J-262 > Uses constraint violation - org.slf4j.api vs. slf4j.api > ------------------------------------------------------- > > Key: JBDS-4136 > URL: https://issues.jboss.org/browse/JBDS-4136 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm, target-platform > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Fix For: 10.2.0.AM3 > > > Latest bit of rpm madness... > This conflict occurred: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931] > Bundle was not resolved because of a uses contraint violation. > org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains. > Chain 1: > org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] > require: (osgi.wiring.bundle=org.slf4j.api) > | > provide: osgi.wiring.bundle: org.slf4j.api > org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] > Chain 2: > org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] > require: (osgi.wiring.bundle=org.slf4j.api) > | > provide: osgi.wiring.bundle; bundle-version:Version="1.7.2.v20121108-1250"; osgi.wiring.bundle="org.slf4j.api" > org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] > require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bundle-version>=1.0.7)(!(bundle-version>=1.0.8)))) > | > provide: osgi.wiring.bundle; bundle-version:Version="1.0.7.v20121108-1250"; osgi.wiring.bundle="ch.qos.logback.classic" > ch.qos.logback.classic [osgi.identity; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"; osgi.identity="ch.qos.logback.classic"] > import: (&(osgi.wiring.package=org.slf4j)(version>=1.7.0)) > | > export: osgi.wiring.package: org.slf4j > slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] > at org.eclipse.osgi.container.Module.start(Module.java:444) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340){code} > So, since slf4j.api is installed via 5 upstream projects (5 symlinks, actually, to rh-java-common): > {code} > $➔ find . -name "*slf4j.api*jar" -exec ls -l {} \; > lrwxrwxrwx 1 root root 81 Oct 11 13:00 ./share/eclipse/droplets/jgit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar > lrwxrwxrwx 1 root root 81 Oct 12 05:19 ./share/eclipse/droplets/linuxtools-docker/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar > lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-egit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar > lrwxrwxrwx 1 root root 75 Oct 21 09:58 ./share/eclipse/droplets/mylyn-versions-git/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/api.jar > lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar > {code} > ... I removed it from the RPM in favour of the other bundle, which was already installed into the fedora/rhel eclipse. > BUT... since this jar exports a different, incompatible bundle name: > {code}Bundle-SymbolicName: slf4j.api{code} > than the one in devstudio's update site > {code}Bundle-SymbolicName: org.slf4j.api{code} > NOW, I'm getting this: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931] > Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2" > {code} > Snjezana got this too in m2e.core: > {code}BundleException: Could not resolve module: org.eclipse.m2e.core.ui [866] > Unresolved requirement: Require-Bundle: org.eclipse.m2e.maven.runtime; bundle-version="[1.7.0,1.8.0)" > -> Bundle-SymbolicName: org.eclipse.m2e.maven.runtime; bundle-version="1.7.0.20160603-1931"; singleton:="false" > org.eclipse.m2e.maven.runtime [876] > Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"{code} > So... not sure what to do to solve this. :( > I suppose the best case would be for the m2e and w2e-wtp bundles to depend on the slf4j.api PACKAGES instead of BUNDLES, so that they can run on the fedora/rhel versions instead of those from the devstudio update site / target platform. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23387) enable jiralint nagging for CDK project JIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23387?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23387: ------------------------------------ Blocked by me getting admin access to CDK JIRA. Note too that if we want bzira-like functionality (ie., generating a matching CDK JIRA for upstream CDK BZ) that can be enabled too. Please open a separate JIRA if you would like this. > enable jiralint nagging for CDK project JIRAs > --------------------------------------------- > > Key: JBIDE-23387 > URL: https://issues.jboss.org/browse/JBIDE-23387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > As discussed on the sprint retrospective, CDK devs are not properly cleaning up their JIRAs (eg., completed issues not marked resolved/closed). > So, we should enable jiralint [1] to also nag those devs about their jiras. > [1] https://github.com/jbosstools/jiralint -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

by Rick Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Rick Wagner commented on JBDS-4070: ----------------------------------- [~rob.stryker] That might be a clue! EAP 6 uses 'deployments' directory. EAP 5 had 'deploy'. I wonder if the user had an EAP5 server adapter set up. (I've reviewed the case, the artifacts don't tell.) No objections to closing this JIRA, it doesn't seem like something that's going to be a problem very often (if ever again). > DevStudio / external OpenShift fails deployment > ----------------------------------------------- > > Key: JBDS-4070 > URL: https://issues.jboss.org/browse/JBDS-4070 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: DevStudio as used with an external OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 10.2.0.AM3 > > Attachments: eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png > > > If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result. > The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports: > 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 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 October 2016