June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23995) Eclipse Hibernate Connection Password Issue Reverse Code Generation

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23995?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23995: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Eclipse Hibernate Connection Password Issue Reverse Code Generation > -------------------------------------------------------------------- > > Key: JBIDE-23995 > URL: https://issues.jboss.org/browse/JBIDE-23995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.2.Final > Environment: Eclipse is Neon.2 > MySQL is 5.6.35 > Connector/J is 5.1.40 > Hibernate Tools 5.1.2.v20161121-1143 org.hibernate.eclipse.feature.feature.group JBoss by Red Hat > Reporter: Adam J. Griff, PhD > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.5.x > > Attachments: hibernate_1.png, hibernate_2.png > > > Password is corrupted resulting in a password error when attempting to connect to the database to perform Reverse Code Generation POJO > [Here is a link to the description on the Hibernate Forum|https://forum.hibernate.org/viewtopic.php?f=1&t=1044013&p=2491457#p...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23427) Broken icon in hibernate properties editor

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23427?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23427: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Broken icon in hibernate properties editor > ------------------------------------------ > > Key: JBIDE-23427 > URL: https://issues.jboss.org/browse/JBIDE-23427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.2.AM2 > Environment: Fedora 24 w/ JDK 8u65: > {code} > $➔ uname -a; java -version > Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > {code} > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.5.x > > Attachments: Schermafbeelding 2017-03-20 om 17.31.45.png, hib-missing-icon-more.png, hib-missing-icon.log.txt, hib-missing-icon.png, hibernate-menu-missing-icon-property-editor.png > > > There appears to be a missing icon in the properties editor for the Hibernate config file. > Steps to repro: > 0. install devstudio from installer jar, devstudio-10.2.0.AM2-v20161014-1657-B6205-installer-standalone.jar > 1. create a project from File > New > Other > General > Project > 2. select the project then create a hibernate.cfg.xml file using the File > New > Other > Hibernate > Hibernate Configuration File (cfg.xml). > Note the error in the view. > !hibernate-menu-missing-icon-property-editor.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24560) Server adapter very slow to restart in debug

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24560?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24560: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Server adapter very slow to restart in debug > --------------------------------------------- > > Key: JBIDE-24560 > URL: https://issues.jboss.org/browse/JBIDE-24560 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.x > > > When the server adapter has been created and just started, if you restart in debug, it is very slow to restart. It seems to happen only the first time after you created it and started. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24314) OpenShift client migration plan

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24314?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24314: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > OpenShift client migration plan > ------------------------------- > > Key: JBIDE-24314 > URL: https://issues.jboss.org/browse/JBIDE-24314 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > > In order to move from the OpenShift REST client to the fabric8, we should have a clear understanding of the impacts and publish a document -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23811) ZipException in CDICoreBuilder when indexing some Maven artifacts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23811?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23811: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > ZipException in CDICoreBuilder when indexing some Maven artifacts > ----------------------------------------------------------------- > > Key: JBIDE-23811 > URL: https://issues.jboss.org/browse/JBIDE-23811 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 4.5.x > > Attachments: org.apache.aries.blueprint.core-1.7.1.jar > > > it would be nice to provide more information in log such as the classes in inspection by CDI Core Builder. > Also if there are some issues with those jars, please report bugs to them. > {noformat} > !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815 > !MESSAGE invalid LOC header (bad signature) > !STACK 0 > java.util.zip.ZipException: invalid LOC header (bad signature) > at java.util.zip.ZipFile.read(Native Method) > at java.util.zip.ZipFile.access$1400(ZipFile.java:60) > at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717) > at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419) > at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at java.io.DataInputStream.readFully(DataInputStream.java:195) > at java.io.DataInputStream.readFully(DataInputStream.java:169) > at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433) > at org.jboss.jandex.Indexer.index(Indexer.java:689) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56) > at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > {noformat} > !ENTRY org.jboss.tools.common.model 4 0 2017-01-25 16:11:53.722 > !MESSAGE Exception occurs when reading C:\Users\Aurelien Pupier\.m2\repository\org\apache\aries\blueprint\org.apache.aries.blueprint.core\1.7.1\org.apache.aries.blueprint.core-1.7.1.jar > !STACK 0 > java.util.zip.ZipException: invalid LOC header (bad signature) > at java.util.zip.ZipFile.read(Native Method) > at java.util.zip.ZipFile.access$1400(Unknown Source) > at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source) > at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source) > at java.util.zip.InflaterInputStream.read(Unknown Source) > at java.io.BufferedInputStream.fill(Unknown Source) > at java.io.BufferedInputStream.read1(Unknown Source) > at java.io.BufferedInputStream.read(Unknown Source) > at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:235) > at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:266) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:95) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:78) > at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:159) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:152) > at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:347) > at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:352) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.readRuntimes(ClassPathMonitor.java:286) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:103) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.jboss.tools.cdi.core.CDICoreBuilder.<init>(CDICoreBuilder.java:101) > at org.jboss.tools.cdi.core.CDICoreNature.load(CDICoreNature.java:420) > at org.jboss.tools.cdi.core.CDICoreNature.resolveStorage(CDICoreNature.java:393) > at org.jboss.tools.cdi.core.CDICoreNature.resolve(CDICoreNature.java:406) > at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:165) > at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:104) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152) > at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374) > at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24217) Deployment config is not shown in OpenshiftExplorer, when service is deleted.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24217?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24217: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Deployment config is not shown in OpenshiftExplorer, when service is deleted. > ----------------------------------------------------------------------------- > > Key: JBIDE-24217 > URL: https://issues.jboss.org/browse/JBIDE-24217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.5.x > > > When service is deleted (in Openshift Explorer), the whole tree node is removed (even though other resources still exist in openshift). > The Deployment config node is not even shown when "refresh" is used. Only thing that helps is removing whole Openshift connection and adding it back again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20569: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: explorer, ux > Fix For: 4.5.x > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20262) Explorer: Manually trigger builds from the connection or project level

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20262?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20262: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Explorer: Manually trigger builds from the connection or project level > ---------------------------------------------------------------------- > > Key: JBIDE-20262 > URL: https://issues.jboss.org/browse/JBIDE-20262 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Labels: explorer, help_wanted, openshift_v3 > Fix For: 4.5.x > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Add selection dialog to allow you to choose a build config from which to start a build by right-clicking on a connection or project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23666) Update quickstarts on Central Home Page

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23666: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Update quickstarts on Central Home Page > --------------------------------------- > > Key: JBIDE-23666 > URL: https://issues.jboss.org/browse/JBIDE-23666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.3.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 10.3.0.AM1 > Build id: AM1-v20161225-1238-B6761 > Build date: 20161225-1238 > Reporter: Josef Kopriva > Assignee: Fred Bricon > Fix For: 4.5.x > > > Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur: > {code:java} > Description Resource Path Location Type > Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem > No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem > No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem > No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem > {code} > For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21627) As a user I want to be able to expose services (create a route to an existing service)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21627?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21627: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > As a user I want to be able to expose services (create a route to an existing service) > --------------------------------------------------------------------------------------- > > Key: JBIDE-21627 > URL: https://issues.jboss.org/browse/JBIDE-21627 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.5.x > > > It would be nice if we would have something similar as oc binary to expose an existing resource. To expose existing pods or services. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017