[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21815:
-------------------------------------
Summary: Image metadata not refreshed after name change
Key: JBIDE-21815
URL: https://issues.jboss.org/browse/JBIDE-21815
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Xavier Coulon
Steps to reproduce:
- open the *Deploy Docker Image* wizard
- input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}}
- go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again.
- ASSERT: the metadata should have been updated
- FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3660) Unable to download ssh-rsync from the provided URL
by Jan Richter (JIRA)
Jan Richter created JBDS-3660:
---------------------------------
Summary: Unable to download ssh-rsync from the provided URL
Key: JBDS-3660
URL: https://issues.jboss.org/browse/JBDS-3660
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Reporter: Jan Richter
Assignee: Denis Golovin
Priority: Blocker
The URL ssh-rsync should be downloaded from points to google drive, which won't let anyone download it without about two more confirmations. The installer just cant cope with this.
As a result of the installs now being chained, it now blocks vagrant and cdk installs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3660) Unable to download ssh-rsync from the provided URL
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3660?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3660:
------------------------------
Fix Version/s: 9.1.0.CR1
> Unable to download ssh-rsync from the provided URL
> --------------------------------------------------
>
> Key: JBDS-3660
> URL: https://issues.jboss.org/browse/JBDS-3660
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> The URL ssh-rsync should be downloaded from points to google drive, which won't let anyone download it without about two more confirmations. The installer just cant cope with this.
> As a result of the installs now being chained, it now blocks vagrant and cdk installs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21765) HQL queries doesn't work with Hibernate 5
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21765?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-21765:
------------------------------------------
I've checked your PR but Im not sure if this is a proper fix. Event though it makes HQL queries work, it disables classpath validation.
For example:
1. create maven war and add dependency
{code}
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-search-orm</artifactId>
<version>5.0.0.Final</version>
</dependency>
{code}
2. create Hibernate configuration (JPA with Hibernate Version 5.0) -> this should result in error since dependecy on hibernate-search-orm.5.0.0.Final is actually Hibernate 4.3 but it wont
[~koen.aers] please take a look at https://github.com/jbosstools/jbosstools-hibernate/pull/90
> HQL queries doesn't work with Hibernate 5
> -----------------------------------------
>
> Key: JBIDE-21765
> URL: https://issues.jboss.org/browse/JBIDE-21765
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: ar.tar.gz, Edit Configuration _002.bmp, Properties for ar _001.bmp
>
>
> {code}
> org.hibernate.hql.internal.ast.QuerySyntaxException: Actor is not mapped [from Actor]
> at org.hibernate.hql.internal.ast.QuerySyntaxException.generateQueryException(QuerySyntaxException.java:79)
> at org.hibernate.QueryException.wrapWithQueryString(QueryException.java:103)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:218)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:142)
> at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:115)
> at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:76)
> at org.hibernate.engine.query.spi.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:150)
> at org.hibernate.internal.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:302)
> at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:240)
> at org.hibernate.internal.SessionImpl.createQuery(SessionImpl.java:1894)
> 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:497)
> at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:43)
> at org.jboss.tools.hibernate.runtime.common.AbstractSessionFacade.createQuery(AbstractSessionFacade.java:47)
> at org.hibernate.eclipse.console.common.HQLQueryPage.setSession(HQLQueryPage.java:133)
> at org.hibernate.eclipse.console.common.HibernateExtension$2.execute(HibernateExtension.java:115)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189)
> at org.hibernate.eclipse.console.common.HibernateExtension.executeHQLQuery(HibernateExtension.java:111)
> at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:306)
> at org.hibernate.eclipse.hqleditor.HQLEditor.executeQuery(HQLEditor.java:447)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:88)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: org.hibernate.hql.internal.ast.QuerySyntaxException: Actor is not mapped
> at org.hibernate.hql.internal.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:171)
> at org.hibernate.hql.internal.ast.tree.FromElementFactory.addFromElement(FromElementFactory.java:91)
> at org.hibernate.hql.internal.ast.tree.FromClause.addFromElement(FromClause.java:76)
> at org.hibernate.hql.internal.ast.HqlSqlWalker.createFromElement(HqlSqlWalker.java:321)
> at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3701)
> at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:3590)
> at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:716)
> at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:572)
> at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:309)
> at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:257)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:262)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:190)
> ... 54 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3659) Regression: VirtualBox installation interrupts ongoing downloads
by Jan Richter (JIRA)
Jan Richter created JBDS-3659:
---------------------------------
Summary: Regression: VirtualBox installation interrupts ongoing downloads
Key: JBDS-3659
URL: https://issues.jboss.org/browse/JBDS-3659
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Reporter: Jan Richter
Assignee: Denis Golovin
Priority: Blocker
Since the last changes, virtualbox can again start installing while other components are downloading, which fiddles with the network setting, which interrupts the ongoing downloads, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21744) cdk-created docker connection can have wrong name if you have multiple cdk server adapters
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21744?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21744:
-------------------------------------
If the host / port are the same, do you really need an additional connection with the same host/port? It's clear you can't have two cdk's started responding on the same host/port, and so only one of the connections would be valid.
Take the following situation: same two cdk's (raw / hardys). Imagine the tools code creates two separate connections upon startup of the respective cdks. We now have 'hardys cdk docker connection' and 'raw cdk docker connection'.
Both connections in the docker explorer would be able to be expanded, even if only one cdk is started. If raw cdk is started, both 'raw cdk docker connection' and 'hardys cdk docker connection' can be expanded.
The user may notice his 'hardys cdk docker connection' can expand, even when the 'hardys cdk' isn't started. Users may then get confused, and think they're inspecting the hardys cdk docker containers, when in fact they're inspecting the raw cdk.
So this also doesn't make the situation better.
> cdk-created docker connection can have wrong name if you have multiple cdk server adapters
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21744
> URL: https://issues.jboss.org/browse/JBIDE-21744
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> I noticed that if I have two cdk server adapters, start the first one, stop it, start the second, then docker explorer will only show a connection of the first server name, not the second.
> This is probably because the connection will stay there after the first server start and on second server start, the tooling only checks if the docker host url matches. If it does, it will just reuse it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month