June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-792) Remove deprecated VDB, WAR framework and update tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-792?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-792: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/752 > Remove deprecated VDB, WAR framework and update tests > ----------------------------------------------------- > > Key: JBTIS-792 > URL: https://issues.jboss.org/browse/JBTIS-792 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-792) Remove deprecated VDB, WAR framework and update tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-792?page=com.atlassian.jira.plugin.... ] stanislav kaleta resolved JBTIS-792. ------------------------------------ Resolution: Done > Remove deprecated VDB, WAR framework and update tests > ----------------------------------------------------- > > Key: JBTIS-792 > URL: https://issues.jboss.org/browse/JBTIS-792 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22589) versionwatch reports sapphire version dropped from 10.0 to 9.0.5

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22589?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22589. ------------------------------- Closing as rejected then. > versionwatch reports sapphire version dropped from 10.0 to 9.0.5 > ---------------------------------------------------------------- > > Key: JBIDE-22589 > URL: https://issues.jboss.org/browse/JBIDE-22589 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, versionwatch > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > Attachments: org.eclipse.sapphire-backleveled.png > > > {code} > Version Watch - Summary Report: devstudio-10.0.0.GA > Version decreased issues > Feature Problem Reference Version(s) > org.eclipse.sapphire.java Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.ui Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.platform Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.java.jdt Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.osgi Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.modeling.xml Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > Plugin Problem Reference Version(s) > org.eclipse.sapphire.java.jdt Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.ui.swt.xml.editor Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.osgi Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.java Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.osgi.fragment Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.workspace.ui Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.ui.swt.gef Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.workspace Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.platform Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.java.jdt.ui Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.ui Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.modeling Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > org.eclipse.sapphire.modeling.xml Version 9.0.5.201605181639 must be higher than 10.0.0.201510151906 10.0.0.201510151906 > > 20 issues found.{code} > https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.versionwatch_... > https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.versionwatch_... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-792) Remove deprecated VDB, WAR framework and update tests

by stanislav kaleta (JIRA)

stanislav kaleta created JBTIS-792: -------------------------------------- Summary: Remove deprecated VDB, WAR framework and update tests Key: JBTIS-792 URL: https://issues.jboss.org/browse/JBTIS-792 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: QE, teiid Affects Versions: 4.3.0.Final Reporter: stanislav kaleta Assignee: Andrej Podhradsky Fix For: 4.3.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-792) Remove deprecated VDB, WAR framework and update tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-792?page=com.atlassian.jira.plugin.... ] stanislav kaleta reassigned JBTIS-792: -------------------------------------- Assignee: stanislav kaleta (was: Andrej Podhradsky) > Remove deprecated VDB, WAR framework and update tests > ----------------------------------------------------- > > Key: JBTIS-792 > URL: https://issues.jboss.org/browse/JBTIS-792 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22594: ----------------------------------------- Comment about "I should always be able to select my OpenShift connection, I should always have the connection page presented" : the connection page is always presented and it is possble to select any existing OpenShift connection. The only thing is that you need to press "< Back" button to return to the connection page, when any OpenShift connection is selected, because deploy image page appears right away. Question: what connection to use if no one was selected (for example we just started eclipse and just opened the Openshift Explorer view)? > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22593: ------------------------------------------ It turns out that the above steps wont work, it looks like a very specific case triggers this. I have to investigate further, I cant reproduce it even though I tried with v2 connections etc. > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.S116 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22175. --------------------------------- Quickstart is imported without issues. Verified in: Version: 10.0.0.GA Build id: GA-v20160615-1853-B33 Build date: 20160615-1853 > Warnings in JBDS after importing kitchensink-jsp quickstart > ----------------------------------------------------------- > > Key: JBIDE-22175 > URL: https://issues.jboss.org/browse/JBIDE-22175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, upstream > Reporter: Sande Gilda > Assignee: Victor Rubezhny > Fix For: 4.4.0.Final > > > After importing the quickstart into JBDS, the following warnings are produced > * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path > * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-3953. ------------------------------- Workarounds for JBoss Developer Studio 9.1.0.GA are working on Fedora 24, eg.: export SWT_GTK3=0 ./jbdevstudio -vmargs -Dorg.eclipse.swt.browser.DefaultType=mozilla (Verified in: Version: 9.1.0.GA Build id: GA-v20160414-0124-B497 Build date: 20160414-0124) 10.0.0 is working without any issues on Fedora 24 with GTK3. (Verified in: Version: 10.0.0.GA Build id: GA-v20160615-1853-B33 Build date: 20160615-1853) Closing issue. > JBoss Studio Developer crash at startup on Fedora 24 > ---------------------------------------------------- > > Key: JBDS-3953 > URL: https://issues.jboss.org/browse/JBDS-3953 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.GA > Environment: Fedora 24 > openjdk full version "1.8.0_92-b14" > Reporter: Donato Marrazzo > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.0.0.GA > > Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip, Selection_003.png > > > After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash. > Despite the console message, no core dump is generated. > This is the cmd line output: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml] > openjdk version "1.8.0_92" > OpenJDK Runtime Environment (build 1.8.0_92-b14) > OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) > 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml] > 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700 > # > # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e > # > # Core dump written. Default location: /home/donato/core or core.12689 > # > # An error report file with more information is saved as: > # /home/donato/hs_err_pid12689.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22362: --------------------------------------- I have created an issue in upstream https://github.com/projectatomic/adb-utils/issues/151 In the mean time, we can either wait, till it's resolved (there are some issues with higher priority, but this should get done in some meaningful time). Or we can change DEV_MODE to true. [~ibuziuk] what I find different between starting debugging and just setting DEV_MODE is the fact that starting debugging also set debug port and should start port forwarding etc. So from user point of view, there will be slight difference between having only DEV_MODE set to true and having an application in debug mode via server adapter. > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.S116 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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