November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25428) Get/POST type for Jolokia connection on invoke method is not respected

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25428?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-25428: ------------------------------------ Summary: Get/POST type for Jolokia connection on invoke method is not respected (was: Respect Get/POST type for Jolokia connection on invoke method) > Get/POST type for Jolokia connection on invoke method is not respected > ---------------------------------------------------------------------- > > Key: JBIDE-25428 > URL: https://issues.jboss.org/browse/JBIDE-25428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25428) Get/POST type for Jolokia connection on invoke method is not respected

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25428?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-25428: ------------------------------------ Description: currently it is always a GET > Get/POST type for Jolokia connection on invoke method is not respected > ---------------------------------------------------------------------- > > Key: JBIDE-25428 > URL: https://issues.jboss.org/browse/JBIDE-25428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Fix For: 4.5.2.AM2 > > > currently it is always a GET -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25428) Get/POST type for Jolokia connection on invoke method is not respected

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25428?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-25428: --------------------------------------- Assignee: Aurélien Pupier > Get/POST type for Jolokia connection on invoke method is not respected > ---------------------------------------------------------------------- > > Key: JBIDE-25428 > URL: https://issues.jboss.org/browse/JBIDE-25428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.5.2.AM2 > > > currently it is always a GET -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25334) OpenShift New and Noteworthy for 4.5.2.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25334?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25334. ------------------------------ Resolution: Done > OpenShift New and Noteworthy for 4.5.2.AM1 > --------------------------------------------------- > > Key: JBIDE-25334 > URL: https://issues.jboss.org/browse/JBIDE-25334 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.5.2.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-25323 #comment Create N&N for OpenShift 4.5.2.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.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25304) In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25304?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25304. --------------------------------- Verified on devstudio Version: 11.2.0.AM1-v20171116-2226-B1644. > In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25304 > URL: https://issues.jboss.org/browse/JBIDE-25304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Minor > Labels: cdk_server_adapter_wizard, openshift_v3 > Fix For: 4.5.2.AM1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1190) Teiid throwns an AssertionFailedException when running against Devstudio RPM

by Lukáš Valach (JIRA)

Lukáš Valach created JBTIS-1190: ----------------------------------- Summary: Teiid throwns an AssertionFailedException when running against Devstudio RPM Key: JBTIS-1190 URL: https://issues.jboss.org/browse/JBTIS-1190 Project: JBoss Tools Integration Stack Issue Type: Bug Components: teiid Affects Versions: 11.1.0.Beta1b Environment: * Devstudio repo: https://devstudio.redhat.com/11/staging/builds/devstudio-11.2.0.AM1-build... * DevTools repo: http://brewweb.engineering.redhat.com/brewroot/repos/devtools-2.1-rh-ecli... * RHEL7 Reporter: Lukáš Valach Fix For: 11.1.0.CR1 Attachments: Teiid_AssertionFailedException.log I installed Devstudio RPM 11.2.0.AM1 and then "JBoss Data Virtualization Development" from RH Central. After restart this error appeared in the log: {code} !ENTRY org.eclipse.equinox.p2.publisher 4 0 2017-11-20 04:45:17.459 !MESSAGE An error occured while parsing advice file: basePath=/home/hudson/.eclipse/org.eclipse.platform_1565164387_linux_gtk_x86_64/features/org.teiid.designer.teiid.client.feature_11.1.1.v20171023-1407, adviceFilePath=p2.inf. !STACK 0 org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) at org.eclipse.equinox.internal.p2.metadata.RequiredCapability.<init>(RequiredCapability.java:104) at org.eclipse.equinox.p2.metadata.MetadataFactory.createRequirement(MetadataFactory.java:465) at org.eclipse.equinox.p2.publisher.AdviceFileParser.createRequirement(AdviceFileParser.java:318) at org.eclipse.equinox.p2.publisher.AdviceFileParser.parseRequired(AdviceFileParser.java:292) at org.eclipse.equinox.p2.publisher.AdviceFileParser.parseRequires(AdviceFileParser.java:244) at org.eclipse.equinox.p2.publisher.AdviceFileParser.parse(AdviceFileParser.java:110) at org.eclipse.equinox.p2.publisher.AdviceFileAdvice.<init>(AdviceFileAdvice.java:78) at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.createAdviceFileAdvice(FeaturesAction.java:166) at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.generateFeatureIUs(FeaturesAction.java:407) at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.perform(FeaturesAction.java:605) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.publish(RepositoryListener.java:160) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.processFeature(RepositoryListener.java:155) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.process(RepositoryListener.java:133) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.added(RepositoryListener.java:117) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.processFile(DirectoryWatcher.java:197) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.scanDirectories(DirectoryWatcher.java:160) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(DirectoryWatcher.java:108) at org.eclipse.equinox.internal.p2.extensionlocation.SiteListener.synchronizeRepositories(SiteListener.java:111) at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationArtifactRepository.ensureInitialized(ExtensionLocationArtifactRepository.java:66) at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationArtifactRepository.getProperties(ExtensionLocationArtifactRepository.java:259) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.addRepository(AbstractRepositoryManager.java:129) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:674) at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:104) at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:100) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getRunnableRepositories(Util.java:161) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getAggregatedBundleRepository(Util.java:153) at org.eclipse.equinox.internal.p2.extensionlocation.Activator.getBundlePoolRepository(Activator.java:88) at org.eclipse.equinox.internal.p2.extensionlocation.BundlePoolFilteredListener.<init>(BundlePoolFilteredListener.java:29) at org.eclipse.equinox.internal.p2.extensionlocation.SiteListener.synchronizeRepositories(SiteListener.java:109) at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationMetadataRepository.ensureInitialized(ExtensionLocationMetadataRepository.java:65) at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationMetadataRepository.getProperties(ExtensionLocationMetadataRepository.java:193) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.addRepository(AbstractRepositoryManager.java:129) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.addRepository(MetadataRepositoryManager.java:37) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.createExtensionLocationMetadataRepository(Activator.java:81) at org.eclipse.equinox.internal.p2.reconciler.dropins.PlatformXmlListener.synchronizeConfiguration(PlatformXmlListener.java:236) at org.eclipse.equinox.internal.p2.reconciler.dropins.PlatformXmlListener.stopPoll(PlatformXmlListener.java:132) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.stopPoll(DirectoryWatcher.java:171) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(DirectoryWatcher.java:109) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.watchConfiguration(Activator.java:519) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:175) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772) at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729) at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:933) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309) at org.eclipse.osgi.container.Module.doStart(Module.java:581) at org.eclipse.osgi.container.Module.start(Module.java:449) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1608) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522) 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) Starting application: 85414 {code} Log: [^Teiid_AssertionFailedException.log] CC: [~apodhrad] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24975) cdk3.devstudio.it.weekly and smoke tests fail on most OS combos

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24975?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-24975. --------------------------------- > cdk3.devstudio.it.weekly and smoke tests fail on most OS combos > --------------------------------------------------------------- > > Key: JBIDE-24975 > URL: https://issues.jboss.org/browse/JBIDE-24975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Ondrej Dockal > Fix For: 4.5.1.Final > > Attachments: cdk3.devstudio.it.smoke.png, cdk3.devstudio.it.weekly.png > > > cdk3.devstudio.it.weekly and smoke tests are failing pretty much everywhere. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !cdk3.devstudio.it.weekly.png|thumbnail! > !cdk3.devstudio.it.smoke.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25163) Extends CDK 3 integration tests to support minishift's profile feature

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25163?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25163. --------------------------------- > Extends CDK 3 integration tests to support minishift's profile feature > ----------------------------------------------------------------------- > > Key: JBIDE-25163 > URL: https://issues.jboss.org/browse/JBIDE-25163 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.5.1.AM3 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.AM1 > > > https://issues.jboss.org/browse/JBIDE-25055 has brought new adapter and featured new widgets in CDK tooling. > ITests should get extended to work with this features. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-25303: ------------------------------------ Description: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": - there is a SpringBoot app deployed on OpenSHift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. was: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case: - there is a SpringBoot app deployed on OpenSHift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM2 > > Attachments: spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenSHift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-25303: ------------------------------------ Description: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": - there is a SpringBoot app deployed on OpenShift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. was: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": - there is a SpringBoot app deployed on OpenSHift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM2 > > Attachments: spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017