April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19671) Aerogear New and Noteworthy for 4.3.0.Alpha2

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19671?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-19671: ------------------------------------ Assignee: Gorkem Ercan > Aerogear New and Noteworthy for 4.3.0.Alpha2 > -------------------------------------------- > > Key: JBIDE-19671 > URL: https://issues.jboss.org/browse/JBIDE-19671 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Alexey Kazakov > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Aerogear is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Aerogear by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19709) Deadlock when trying to stop multiple containers at the same time

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19709: ------------------------------------- Summary: Deadlock when trying to stop multiple containers at the same time Key: JBIDE-19709 URL: https://issues.jboss.org/browse/JBIDE-19709 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Affects Versions: 4.3.0.Alpha2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.0.Beta1 When selecting multiple containers (mix of running and stopped or all running) and call the 'stop' method, the UI freezes after the fist container is stopped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ Yes. For simple projects (base, server, ..., central) we can use `mvn deploy -Pdeploy-to-jboss.org`. For everyone else we can use `mvn deploy -Pdeploy-to-jboss.org -Doverride=this -Doverride=that -Doverride=the-other ...` We might also need a "copy-or-rename stuff after it's built before calling rsync" step. Otherwise the staging & release processes can handle renames as required (eg., when we have to strip qualifiers off JBDS artifacts so they use Beta1 instead of Beta1-v20150623-1234-B456). > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19605: ------------------------------------ Remove it, rebuild it, and see what happens? > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBDS-3249: ----------------------------- Fix Version/s: (was: 8.1.0.GA) > As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps > ------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3249 > URL: https://issues.jboss.org/browse/JBDS-3249 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer, integration-platform, requirements, updatesite > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find. > Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276) > From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19683) Create a user visible location for downloading tutorial metadata

by Petr Penicka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19683?page=com.atlassian.jira.plugi... ] Petr Penicka commented on JBIDE-19683: -------------------------------------- Hi Max, let me provide the context first. The Fuse Tooling Tutorials book Jane is talking about is this [1]. It is different from a quickstart in that it does not provide a prefabricated deployable app, but goes one step back and demonstrates how to create one from scratch. Because the tutorial chapters go in a sequence, each utilizing code created in the previous one, we recently enhanced the book with downloadable files of the code created in each chapter. The primary delivery mechanism of this book has been the Customer Portal and as a side product, it has also been provided in Fuse Tooling embedded help. While it's easy to provide the downloads on the portal, it's not the case in the embedded help, so we were considering to provide the downloads on jboss.org. Though your suggested approach seems interesting in the long run, we don't have the resources to make that happen for the upcoming Fuse release. Because of that, we decided to drop the tutorial from the Fuse Tooling embedded help and only provide it on the Customer Portal. I hope this clarifies what was originally asked in this issue and as the request is not longer valid, I believe you can close the issue. Regards, Petr Penicka, Documentation Program Manager - Red Hat JBoss Fuse and A-MQ [1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1... > Create a user visible location for downloading tutorial metadata > ---------------------------------------------------------------- > > Key: JBIDE-19683 > URL: https://issues.jboss.org/browse/JBIDE-19683 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Reporter: Jane Murphey > > Need to modify jbosstools-download.jboss.org to establish a directory to be used by documentation tutorials. Fuse Tooling will be the first. I will generate a PR soon. Please assign to me (jmurphey). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19443) java.lang.NoClassDefFoundError in Reveng editor when using Hibernate 3.6

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19443?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19443: ------------------------------ Sprint: Sprint #2 April 2015 > java.lang.NoClassDefFoundError in Reveng editor when using Hibernate 3.6 > ------------------------------------------------------------------------ > > Key: JBIDE-19443 > URL: https://issues.jboss.org/browse/JBIDE-19443 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.cfg.reveng.OverrideRepository > at org.jboss.tools.hibernate.proxy.ServiceProxy.newOverrideRepository(ServiceProxy.java:198) > at org.hibernate.eclipse.mapper.editors.ReverseEngineeringEditor.getLazyDatabaseSchema(ReverseEngineeringEditor.java:207) > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock.doAdd(TablePropertiesBlock.java:172) > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock$1.widgetSelected(TablePropertiesBlock.java:128) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47) > 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:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19431) Cannot generate ddl when hibernate console is used

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19431?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19431: ------------------------------ Sprint: Sprint #2 April 2015 > Cannot generate ddl when hibernate console is used > -------------------------------------------------- > > Key: JBIDE-19431 > URL: https://issues.jboss.org/browse/JBIDE-19431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Environment: JBDS 8.1.0.Beta1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > Cannot generate ddl when hibernate console is used. I will investigate further, it worked for 4.3 (and didn't work for lower hibernate versions) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19605: --------------------------------------- I have no idea how it's used on {{org.jboss.tools.ws.ui}}. But it's not used at all on JAX-RS. > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19535) Cannot generate ddl when hibernate console is NOT used

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19535?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19535: ------------------------------ Sprint: Sprint #2 April 2015 > Cannot generate ddl when hibernate console is NOT used > ------------------------------------------------------ > > Key: JBIDE-19535 > URL: https://issues.jboss.org/browse/JBIDE-19535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Environment: JBDS 8.1.0.GA > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > Cannot generate ddl when hibernate console is NOT used. It actually works when Hibernate 3.5, 3.6, 4.0 is used but not for 4.3. Found by extended automated tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 April 2015