July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17936: --------------------------------------- [~rob.stryker] that's in the Deployment page of the server editor. I recorded a screencast but it failed to upload :-\ Screenshot here: https://www.dropbox.com/s/5d61keexic63uw2/Screenshot%202014-07-22%2021.26... The problem is that both fields contain the same dir. But I didn't set them up to be the same. > Remote deploy only server has wrong temp dir and unreadable entries in server editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-17936 > URL: https://issues.jboss.org/browse/JBIDE-17936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png > > > This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one: > When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems: > 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big. > !deploy-only-crop.png! > See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before. > 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17936: ------------------------------------- I've made an (unapproved) commit to set a minimal width for the section, which fixes the widgets all crashing into each other. However I'm not able to replicate the incorrect deploy folder being used and your screenshots don't really show that... =/ Please get back with more info if possible. > Remote deploy only server has wrong temp dir and unreadable entries in server editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-17936 > URL: https://issues.jboss.org/browse/JBIDE-17936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png > > > This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one: > When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems: > 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big. > !deploy-only-crop.png! > See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before. > 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17894) Generate Entities From Tables is blocked

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17894?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17894: ------------------------------------ Rebuilt: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Generate Entities From Tables is blocked > ---------------------------------------- > > Key: JBIDE-17894 > URL: https://issues.jboss.org/browse/JBIDE-17894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Blocker > Labels: respin-c > Fix For: 4.2.0.Beta3, 4.2.0.CR1 > > Attachments: jstack.txt > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17936: ------------------------------------- Ignore that previous comment. I wasn't using deploy-only server. So dumb. > Remote deploy only server has wrong temp dir and unreadable entries in server editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-17936 > URL: https://issues.jboss.org/browse/JBIDE-17936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png > > > This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one: > When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems: > 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big. > !deploy-only-crop.png! > See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before. > 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17936: -------------------------------- Attachment: JBIDE-17936.png This is pretty strange. I can't replicate this, no matter how small I shrink the editor portion of the window. Can you give me some more environment details? > Remote deploy only server has wrong temp dir and unreadable entries in server editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-17936 > URL: https://issues.jboss.org/browse/JBIDE-17936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png > > > This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one: > When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems: > 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big. > !deploy-only-crop.png! > See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before. > 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2991) Non-fatal error logged when starting JBDS 8.0.beta1

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2991?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-2991. ------------------------------ No longer reproducible - closing. > Non-fatal error logged when starting JBDS 8.0.beta1 > --------------------------------------------------- > > Key: JBDS-2991 > URL: https://issues.jboss.org/browse/JBDS-2991 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 8.0.0.Beta1 > Environment: JBDS 8.0.beta1 > Java7 or Java8 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Fix For: 8.0.0.Beta3 > > > !ENTRY org.eclipse.core.runtime 2 0 2014-03-27 14:37:10.053 > !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed. > !STACK 0 > java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by osgi.identity; osgi.identity="org.eclipse.core.runtime"; type="osgi.bundle"; version:Version="3.10.0.v20140221-2027"; singleton:="true" > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:416) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:336) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:328) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:259) > at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48) > at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69) > at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231) > at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590) > at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89) > at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60) > at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3748) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3396) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1462) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17619: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.x) > Console for remote server disappears when workspace is switched > --------------------------------------------------------------- > > Key: JBIDE-17619 > URL: https://issues.jboss.org/browse/JBIDE-17619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped. > The only thing that helped me here was to delete the server and create a new one. > I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17952) remove the org.hibernate.tools.temp plugin before CR1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17952?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17952: ----------------------------------- Fix Version/s: 4.2.0.CR1 > remove the org.hibernate.tools.temp plugin before CR1 > ----------------------------------------------------- > > Key: JBIDE-17952 > URL: https://issues.jboss.org/browse/JBIDE-17952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.2.0.CR1 > > > .temp plugin should be gone before we reach CR1. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17947) Java Model Exception occurs while typing

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17947?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17947: -------------------------------------- Assignee: Xavier Coulon (was: Alexey Kazakov) > Java Model Exception occurs while typing > ---------------------------------------- > > Key: JBIDE-17947 > URL: https://issues.jboss.org/browse/JBIDE-17947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Labels: respin-c > Fix For: 4.2.0.Beta3 > > Attachments: JBIDE-17947 (2).ogv, stack trace, video.ogv > > > While editing JAX-RS resource class, the following exception shows up in Error log > {code} > Java Model Exception: Java Model Status [post() {key=LResource;.post()V} [in Resource [in [Working copy] Resource.java [in <default> [in src [in DynamicWebProject]]]]] does not exist] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17952) remove the org.hibernate.tools.temp plugin before CR1

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-17952: ------------------------------------------- Summary: remove the org.hibernate.tools.temp plugin before CR1 Key: JBIDE-17952 URL: https://issues.jboss.org/browse/JBIDE-17952 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Reporter: Max Rydahl Andersen Priority: Blocker .temp plugin should be gone before we reach CR1. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 July 2014