November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13445: --------------------------------------- Regardless of the issue I described above, what's the status of this? Maybe it has now been superseeded by JBIDE-17180 ? In JBDS 8.0.0.GA, when I have a remote server with fs operations, even if I exposed management port, the custom deploy fields were still disabled :( > Enable possibility of deployment scanner additions for remote servers > --------------------------------------------------------------------- > > Key: JBIDE-13445 > URL: https://issues.jboss.org/browse/JBIDE-13445 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.x > > > Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc. There is a lack of api here, and that will need to be fixed before this issue can work. > Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17180: ---------------------------------- Attachment: wide-window.png Here's how it looks: !wide-window.png! > Disable custom deployment settings for remote servers without management port exposed > ------------------------------------------------------------------------------------- > > Key: JBIDE-17180 > URL: https://issues.jboss.org/browse/JBIDE-17180 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: wide-window.png > > > JBIDE-13445 added the possibility to use custom deploy dir on remote server. > {quote} > Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. > {quote} > We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3240) JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes

by Marek Novotny (JIRA)

Marek Novotny created JBDS-3240: ----------------------------------- Summary: JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes Key: JBDS-3240 URL: https://issues.jboss.org/browse/JBDS-3240 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 8.0.0.GA Reporter: Marek Novotny JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. For instance I click on HTML5 project in Start from Scratch in JBoss Central: it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3240) JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3240: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? Target Release: 8.0.1.GA > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes > ------------------------------------------------------------------ > > Key: JBDS-3240 > URL: https://issues.jboss.org/browse/JBDS-3240 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. > For instance I click on HTML5 project in Start from Scratch in JBoss Central: > it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18816) Ensure features and plugins have upversioned since 4.2.0.Final release [Freemarker]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18816?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18816. ------------------------------------ verified in JBDS 8.0.0.CR1-v20141124-0632-B334 > Ensure features and plugins have upversioned since 4.2.0.Final release [Freemarker] > ----------------------------------------------------------------------------------- > > Key: JBIDE-18816 > URL: https://issues.jboss.org/browse/JBIDE-18816 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions > Affects Versions: 4.2.1.CR1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.1.CR1 > > > You have commits in your 4.2.x branch which happened AFTER 4.2.0.Final. Yet your root pom is still at version 4.2.0, and your affected plugins' versions are not incremented. > https://github.com/jbosstools/jbosstools-freemarker/commits/jbosstools-4.2.x > Please bump your stuff to a .1 version to reflect the fact you're doing maintenance in the 4.2.x branch. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18773) Ensure features and plugins have upversioned since 4.2.0.Final release [JavaEE]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18773?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18773. ------------------------------------ verified in JBDS 8.0.0.CR1-v20141124-0632-B334 > Ensure features and plugins have upversioned since 4.2.0.Final release [JavaEE] > ------------------------------------------------------------------------------- > > Key: JBIDE-18773 > URL: https://issues.jboss.org/browse/JBIDE-18773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.2.1.CR1 > > > You have commits in your 4.2.x branch which happened AFTER 4.2.0.Final. Yet your root pom is still at version 4.2.0, and your affected plugins are still at 1.6.0: > https://github.com/jbosstools/jbosstools-javaee/blob/c7a07c9a31955213c2bc... > Please bump your stuff to a .1 version to reflect the fact you're doing maintenance in the 4.2.x branch. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18769) ResourceException when generating hbm.xml

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18769?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18769: ------------------------------ Fix Version/s: 4.2.x 4.3.x (was: 4.3.0.Alpha1) (was: 4.2.1.Final) > ResourceException when generating hbm.xml > ----------------------------------------- > > Key: JBIDE-18769 > URL: https://issues.jboss.org/browse/JBIDE-18769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Final > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.x, 4.3.x > > > {code} > org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee6-webapp/org/jboss/tools/examples/model' does not exist. > at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341) > at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215) > at org.eclipse.core.internal.resources.File.create(File.java:115) > at org.eclipse.core.internal.resources.File.create(File.java:188) > at org.eclipse.jdt.internal.corext.refactoring.nls.changes.CreateFileChange.perform(CreateFileChange.java:165) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingPreviewPage.performFinish(NewHibernateMappingPreviewPage.java:299) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.performFinish(NewHibernateMappingFileWizard.java:408) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > 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.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) > 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$5.handleEvent(ActionContributionItem.java:420) > 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.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) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18796) Openshift build fails with mars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18796?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18796: ------------------------------------------ merged and pushed to upstream/master > Openshift build fails with mars > ------------------------------- > > Key: JBIDE-18796 > URL: https://issues.jboss.org/browse/JBIDE-18796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Fix For: 4.3.0.Alpha1 > > > There are changes in internal API -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18575) Unable to generate entities for JPA 2.0 project when moving project from JPA 2.1 to JPA 2.0

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18575?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18575: ------------------------------ Fix Version/s: 4.2.x 4.3.x (was: 4.3.0.Alpha1) (was: 4.2.1.Final) > Unable to generate entities for JPA 2.0 project when moving project from JPA 2.1 to JPA 2.0 > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18575 > URL: https://issues.jboss.org/browse/JBIDE-18575 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.CR2 > Environment: JBDS 8.0.0.CR2 > Reporter: Jiri Peterka > Labels: respin-a > Fix For: 4.2.x, 4.3.x > > > org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.tool.Version > Could not initialize class org.hibernate.tool.Version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18796) Openshift build fails with mars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18796?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18796: ------------------------------------- Fix Version/s: 4.3.0.Alpha1 > Openshift build fails with mars > ------------------------------- > > Key: JBIDE-18796 > URL: https://issues.jboss.org/browse/JBIDE-18796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Fix For: 4.3.0.Alpha1 > > > There are changes in internal API -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2014