October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21026?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-21026. ------------------------------- Resolution: Done > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-21026 > URL: https://issues.jboss.org/browse/JBIDE-21026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.3.1.Beta1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

Koen Aers created JBIDE-21026: --------------------------------- Summary: New hibernate configuration wizard controls invisible in Unix Key: JBIDE-21026 URL: https://issues.jboss.org/browse/JBIDE-21026 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.3.0.CR1 Reporter: Dmitry Bocharov Assignee: Koen Aers Priority: Minor Fix For: 4.4.0.Alpha1 Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-20801: ------------------------------ Fix Version/s: 4.4.0.Alpha1 > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-508: ---------------------------------- Since this is ALSO the latest content for the JBT & JBDS development sites (the latest stable milestone = 9.0.0.GA / 4.3.0.Final = latest release too) should you not also update these four /development/ URLs too? [1] https://devstudio.redhat.com/9.0/development/updates/ composite*.xml [2] https://devstudio.redhat.com/9.0/development/updates/earlyaccess/ composite*.xml [3] http://download.jboss.org/jbosstools/mars/development/updates/ composite*.xml [4] http://download.jboss.org/jbosstools/mars/development/updates/earlyaccess/ composite*.xml Are all these manual changes reflected in your updated release guide, so that you'll update BOTH stable and development as appropriate when you release your next Alpha or Beta bits? Can you link to that document here? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20764 at 10/27/15 10:17 AM: --------------------------------------------------------------------- In a 1st batch we'll try to implement "oc rsync" for incremental deployment. The [PR|https://github.com/openshift/origin/pull/4787] for "oc rsync" unveils the details of the implementation. It's using rsync if the client OS is linux, *tar* on windows. An additonal [PR|https://github.com/openshift/origin/pull/5351] replaces *tar* with *rsync* on windows. For windows users would then be required to install cygwin or rsync from https://www.itefix.net/cwrsync An exemplary usage can be read here: https://github.com/openshift/origin/blob/master/docs/generated/oc_by_exam... was (Author: adietish): In a 1st batch we'll try to implement "oc rsync" for incremental deployment. The [PR|https://github.com/openshift/origin/pull/4787] for "oc rsync" unveils the details of the implementation. It's using rsync if the client OS is linux, *tar* on windows. An exemplary usage can be read here: https://github.com/openshift/origin/blob/master/docs/generated/oc_by_exam... > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: server adapter wizard.bmml, server adapter wizard.png > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-508: ---------------------------------- Agreed - consistency demands merged IS composites: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/aac2cd... > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21024) webservice tester "forgets" parameterized url

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21024?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21024: ----------------------------------- Assignee: Xavier Coulon > webservice tester "forgets" parameterized url > --------------------------------------------- > > Key: JBIDE-21024 > URL: https://issues.jboss.org/browse/JBIDE-21024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > use html5 kitchensink example and one of the urls you can run is "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/{id:..." > When you run this webservice tester will ask you about id - great. > But when executing the first time it will reset the url to "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/" meaning it is not possible to run again without manually typing it in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21025) hibernate querying nor content assist is broken

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21025?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-21025: --------------------------------- Assignee: Koen Aers > hibernate querying nor content assist is broken > ----------------------------------------------- > > Key: JBIDE-21025 > URL: https://issues.jboss.org/browse/JBIDE-21025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > > using html5-kitchensink I cannot get basic content assist to work. > "from Member m where m.|" gives no content assist at all. > And trying to run the query results in: > {code} > java.lang.NullPointerException > at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1888) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845) > at org.jboss.tools.hibernate.runtime.v_4_3.internal.ConfigurationFacadeImpl.buildTargetSessionFactory(ConfigurationFacadeImpl.java:24) > at org.jboss.tools.hibernate.runtime.common.AbstractConfigurationFacade.buildSessionFactory(AbstractConfigurationFacade.java:169) > at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108) > at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81) > 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:4230) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > 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:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > 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:483) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ] David Hladky commented on JBDS-3547: ------------------------------------ Every link, that goes to www.jboss.org/download-manager/.... is tracked in Download manager. This means old downloads as well. The reason is you can add the link to the file anywhere including 3rd party forums and the downloads are tracked. > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-529: ---------------------------------- [~fbricon] - Looks like you're ahead of the pack in investigating this - assigning to you initially, > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 October 2015