August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22784) Create integration tests PR check job for docker

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22784?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-22784: ---------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.x) > Create integration tests PR check job for docker > ------------------------------------------------ > > Key: JBIDE-22784 > URL: https://issues.jboss.org/browse/JBIDE-22784 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Josef Kopriva > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22727: ------------------------------------ Description: The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in ConnectionWrapper, but there is no such element in WatchManager's array. See discussion [here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...] was:The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. > Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22727 > URL: https://issues.jboss.org/browse/JBIDE-22727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Jeff MAURY > Assignee: Dmitry Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.1.AM3 > > > The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. > The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in ConnectionWrapper, but there is no such element in WatchManager's array. See discussion [here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3948: -------------------------------- > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer > ------------------------------------------------------------------------------------------ > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3948: ----------------------------- > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer > ------------------------------------------------------------------------------------------ > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3948: -------------------------------- Target Release: 10.1.0.GA > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer > ------------------------------------------------------------------------------------------ > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3948: -------------------------------- > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer > ------------------------------------------------------------------------------------------ > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-827) Update site for JBDS-IS 9.0.1.GA-EA still refers to JBDS-IS 9.0.1.CR2-EA

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-827?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-827. ------------------------------ Fix Version/s: 9.0.1.GA Assignee: Paul Leacu Resolution: Done Sorry - missed that one. Is now fixed. > Update site for JBDS-IS 9.0.1.GA-EA still refers to JBDS-IS 9.0.1.CR2-EA > ------------------------------------------------------------------------ > > Key: JBTIS-827 > URL: https://issues.jboss.org/browse/JBTIS-827 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.1.GA > > > The composite files are not consistent > {code:title=compositeArtifacts.xml} > <children size='2'> >  > <child location='../9.0.1.GA/earlyaccess/'/> > <child location='../9.0.1.GA/earlyaccess/targetplatform/'/> > </children> > {code} > {code:title=compositeContent.xml} > <children size='2'> >  > <child location='../9.0.1.CR3/earlyaccess/'/> > <child location='../9.0.1.CR3/earlyaccess/targetplatform/'/> > </children> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22913: ------------------------------------ Which platform are you running because I thought the problem was only visible on Windows and MacOSX ? > Server Adapter: Publish does not work > ------------------------------------- > > Key: JBIDE-22913 > URL: https://issues.jboss.org/browse/JBIDE-22913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > > When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error. > {code} > Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it. > Ignoring the following flags because they only apply to rsync: --exclude, --no-perms > 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: error executing remote command: Error executing command in container: Error executing in Docker Container: 2 > {code} > I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22874) ide-config.properties needs updating for 10.1.0.AM3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22874?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22874: --------------------------------------- [~nickboldt], current devstudio 10.1.0.AM3 build works fine now. But this will fail as soon as we move to GA/Final, unless a change to ide-config.properties is made at the same time. Is that intentional? > ide-config.properties needs updating for 10.1.0.AM3 > --------------------------------------------------- > > Key: JBIDE-22874 > URL: https://issues.jboss.org/browse/JBIDE-22874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > Today I installed a new build of devstudio (devstudio-10.1.0.AM3-v20160802-1710-B5682-installer-standalone.jar) and immediately after launching it, I got these in the error log view: > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > {code} > {code} > All attempts to discover connectors have failed > {code} > {code} > Failed to get connectors from RemoteProxyWizardDiscoveryStrategy > java.lang.NullPointerException > at java.net.URI$Parser.parse(URI.java:3042) > at java.net.URI.<init>(URI.java:588) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90) > at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117) > at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68) > at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > {code} > This is probably happening because [1] doesn't have any lines that would apply for devstudio 10.1.0.AM3. > At first I thought it's something that was overlooked when changing product version from 10.0.1 to 10.1.0, but it seems 10.0.1.AM3 would have no match either as there is currently only 10.0.1.AM2 there. Shouldn't we have also have lines for a more general version like 10.1.0, so that a match is guaranteed? > On the other hand, JBoss Tools should be fine - I can see lines for both 4.4.1 and 4.4.1.AM3. > Feel free to move this to JBDS if you think that's more appropriate. > [1] http://download.jboss.org/jbosstools/configuration/ide-config.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22963) NPE when creating a html5 project

by Martin Malina (JIRA)

Martin Malina created JBIDE-22963: ------------------------------------- Summary: NPE when creating a html5 project Key: JBIDE-22963 URL: https://issues.jboss.org/browse/JBIDE-22963 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.4.1.AM3 Reporter: Martin Malina I get this NPE when I create the HTML5 project from Central: {code} java.lang.NullPointerException at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.lookupHibernateVersion(JPAPostInstallFasetListener.java:222) at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.buildConsoleConfiguration(JPAPostInstallFasetListener.java:182) at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.handleEvent(JPAPostInstallFasetListener.java:79) at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:152) at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:108) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:830) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:758) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:382) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:377) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:419) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) {code} I was using devstudio-10.1.0.AM3-v20160808-1833-B5724-installer-standalone.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016