July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22687) Include Hibernate Core 5.2.1.Final in the 5.2 runtime plugin

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22687?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22687. ------------------------------------ verified in Devstudio 10.0.1.v20160720-1632 > Include Hibernate Core 5.2.1.Final in the 5.2 runtime plugin > ------------------------------------------------------------ > > Key: JBIDE-22687 > URL: https://issues.jboss.org/browse/JBIDE-22687 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22811) Dont log exception when getting hibernate version

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-22811: ---------------------------------------- Summary: Dont log exception when getting hibernate version Key: JBIDE-22811 URL: https://issues.jboss.org/browse/JBIDE-22811 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: hibernate Affects Versions: 4.4.1.AM2 Reporter: Rastislav Wagner Fix For: 4.4.1.AM3 This is a follow up on JBIDE-21769 Create JPA project and set Platform to Hibernate, JPA implementation to Disable library Configuration. When you open Hibernate Configrations view an exception is logged in error log {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$5.run(FacetedProject.java:1099) 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.mergeChanges(FacetedProject.java:1109) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:400) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:282) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331) 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.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) {code} I dont think its necessary to log it. - nothing went wrong, JPA project just doesnt specify hibernate version - AERI kicks in and user might think this is an actual bug in code -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21769) Default hibernate configuration is set to 4.3 - should be 5.0

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21769?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-21769. ------------------------------------ Verified in Devstudio 10.0.1.v20160720-1632 > Default hibernate configuration is set to 4.3 - should be 5.0 > ------------------------------------------------------------- > > Key: JBIDE-21769 > URL: https://issues.jboss.org/browse/JBIDE-21769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.1.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18697: --------------------------------------- I just tried this again and it still works fine for me :( I wish we could reproduce this, then we could do something about it, but we still can't. I have Windows 10 64-bit, Eclipse Neon, WildFly 10 and a simple dynamic web project deployed as exploded war. It still seems to me that the error indicates that eclipse cannot write to that deployment directory for some reason. Have you tried unzipping a new WildFly server in a new directory? Somebody wrote this on the stackoverflow post: {quote} I was getting the same error message, turns out it was because something went wrong in the deployments folder of JBoss, it wasn't even allowing me to delete my project ear folder from deployments. My solution was, unzipped another instance of JBoss and pointed my Eclipse to this JBoss and then it worked fine. {quote} > Error deploying exploded war on windows; fs / copy error > -------------------------------------------------------- > > Key: JBIDE-18697 > URL: https://issues.jboss.org/browse/JBIDE-18697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.1.Final > > > https://developer.jboss.org/message/907562 > A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3840) Installer: upgrade electon-packager to latest version (security fix)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3840?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3840: ------------------------------ Sprint: (was: devex #118 July 2016) > Installer: upgrade electon-packager to latest version (security fix) > -------------------------------------------------------------------- > > Key: JBDS-3840 > URL: https://issues.jboss.org/browse/JBDS-3840 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Component Upgrade > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Jan Richter > Priority: Critical > Labels: havoc > Fix For: 10.1.0.AM2 > > > The version of electron-packager that we use doesn't check SSL certificates by default because of this issue \[1]. We should upgrade to latest version ASAP (now 7.0.0). > \[1] https://github.com/electron-userland/electron-packager/issues/333 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3840) Installer: upgrade electon-packager to latest version (security fix)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3840?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3840. ----------------------------- Resolution: Done Correct, this issue was resolved by the said commit. Closing. > Installer: upgrade electon-packager to latest version (security fix) > -------------------------------------------------------------------- > > Key: JBDS-3840 > URL: https://issues.jboss.org/browse/JBDS-3840 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Component Upgrade > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Jan Richter > Priority: Critical > Labels: havoc > Fix For: 10.1.0.AM2 > > > The version of electron-packager that we use doesn't check SSL certificates by default because of this issue \[1]. We should upgrade to latest version ASAP (now 7.0.0). > \[1] https://github.com/electron-userland/electron-packager/issues/333 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3840) Installer: upgrade electon-packager to latest version (security fix)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3840?page=com.atlassian.jira.plugin.... ] Jan Richter reassigned JBDS-3840: --------------------------------- Assignee: Jan Richter > Installer: upgrade electon-packager to latest version (security fix) > -------------------------------------------------------------------- > > Key: JBDS-3840 > URL: https://issues.jboss.org/browse/JBDS-3840 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Component Upgrade > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Jan Richter > Priority: Critical > Labels: havoc > Fix For: 10.1.0.AM2 > > > The version of electron-packager that we use doesn't check SSL certificates by default because of this issue \[1]. We should upgrade to latest version ASAP (now 7.0.0). > \[1] https://github.com/electron-userland/electron-packager/issues/333 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3951: -------------------------------- Story Points: 1 > Installer needs to add the VirtualBox install directory to the PATH > ------------------------------------------------------------------- > > Key: JBDS-3951 > URL: https://issues.jboss.org/browse/JBDS-3951 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.1.0.AM3 > > > The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found. > As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3978?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3978: -------------------------------- Story Points: 8 > Getting started page shows guide for Devstudio 9.x > -------------------------------------------------- > > Key: JBDS-3978 > URL: https://issues.jboss.org/browse/JBDS-3978 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.AM3 > > > The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview > The very fact that it is named > {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} > looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3947: -------------------------------- Story Points: 5 > Some older versions of vagrant skip version validation > ------------------------------------------------------ > > Key: JBDS-3947 > URL: https://issues.jboss.org/browse/JBDS-3947 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > Attachments: vagrant.png > > > Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though. > !vagrant.png|thumbnail! > The issue might be connected to the fact that with these versions the command > {noformat}where vagrant{noformat} > in fact returns 2 files -- 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 July 2016