January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10319) Need to have more explicit form to handle -b 0.0.0.0

by Max Rydahl Andersen (Created) (JIRA)

Need to have more explicit form to handle -b 0.0.0.0 ---------------------------------------------------- Key: JBIDE-10319 URL: https://issues.jboss.org/browse/JBIDE-10319 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.3.0.Beta1 currently the workaround is to set host to 0.0.0.0 but then run as does not work since it doesn't know which server that is. Should be an option on the server/launch editor to control this. Default to host, but also have a way to set it explicitly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

8
10
0 / 0

[JBoss JIRA] (JBIDE-10478) Support -b for AS7

by Max Rydahl Andersen (Created) (JIRA)

Support -b for AS7 ------------------ Key: JBIDE-10478 URL: https://issues.jboss.org/browse/JBIDE-10478 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.Beta1 AS7 supports -b but we do not pass host on. we should do that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBIDE-10476) AS7.1 has no default java facets set

by Rob Stryker (Created) (JIRA)

AS7.1 has no default java facets set ------------------------------------ Key: JBIDE-10476 URL: https://issues.jboss.org/browse/JBIDE-10476 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta1 AS7.1 shows the java 1.7 facet by default because it does not set a hard-coded default facet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] (JBIDE-10463) Regression for JBossAS 7.1: Runtime detection doesn't consider additions to "Default Classpath Entries"

by Juergen Zimmermann (Created) (JIRA)

Regression for JBossAS 7.1: Runtime detection doesn't consider additions to "Default Classpath Entries" ------------------------------------------------------------------------------------------------------- Key: JBIDE-10463 URL: https://issues.jboss.org/browse/JBIDE-10463 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M4, 3.3.0.M5 Reporter: Juergen Zimmermann Assignee: Rob Stryker I tried build 2011-12-12_16-41-07-H58. However, when I invoke Preferences > JBoss Tools > JBoss Tools Runtime Detection the resulting server config doesn't contain JARs that are configured in Preferences > Server > Runtime Environments > Default Classpath Entries. For instance I added: Name: JBoss EJB3 Extensions Root Directory: modules/org/jboss/ejb3/main Includes: **/*.jar The resulting classpath should contain jboss-ejb3-ext-api-2.0.0-beta-1.jar being located in $JBOSS_HOME/modules/org/jboss/ejb3/main. I'll attach a screenshot to illustrate the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

8
10
0 / 0

[JBoss JIRA] (JBIDE-10735) The new OpenShift wizards (import and create new) are not named consistently with the rest of the Eclipse

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-10735: ---------------------------------------- Summary: The new OpenShift wizards (import and create new) are not named consistently with the rest of the Eclipse Key: JBIDE-10735 URL: https://issues.jboss.org/browse/JBIDE-10735 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Attachments: create-new-openshift-wizard.png, import-openshift.png Both new wizards, the one to import and the one to create a new OpenShift application, use very long and explicit labels in the wizard listings (and in central). This naming scheme is usefull but is not matching the rest of Eclipse and the other wizards listed in Central. Import: !import-openshift.png! Create new: !create-new-openshift-wizard.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
13
0 / 0

[JBoss JIRA] (JBIDE-10727) application details dialog: table tree has no margin and no scrollbars

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-10727: ---------------------------------------- Summary: application details dialog: table tree has no margin and no scrollbars Key: JBIDE-10727 URL: https://issues.jboss.org/browse/JBIDE-10727 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 The application details dialog now displays the application details in a tree table (new implementation, replaces the former). This dialog has 2 minor flaws UI-wise: * the table has no margins to the left and to the right. * the table has no scroll-bars. This is quite annoying since the git url is too long and it gets cut. !git-url-gets-cut-off.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (JBIDE-10725) Cannot copy the git url of an existing app

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-10725: ---------------------------------------- Summary: Cannot copy the git url of an existing app Key: JBIDE-10725 URL: https://issues.jboss.org/browse/JBIDE-10725 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Xavier Coulon Fix For: 3.3.0.Beta1 There's currently no way to copy the git-url (and the web-url) of an OpenShift application. There's no context menu in the details dialog. !cannot-copy-git-url.png! Furthermore I'd add some margin to the right and left of the -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9630) Sometimes getting 'Already publishing' error

by Libor Zoubek (JIRA)

Sometimes getting 'Already publishing' error -------------------------------------------- Key: JBIDE-9630 URL: https://issues.jboss.org/browse/JBIDE-9630 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Libor Zoubek Assignee: Rob Stryker Fix For: 3.3.0.M4 I' facing 'Already publishing' error dialog when working on web apps using AS7. I still did not found exact steps to reproduce. Right now I've once reproduced doing following: Have stated AS7.0.1 Have deployed web app (which currenly caused deployment error on AS) Imported jboss-as demos (5 projects) using 'Import Existing maven projects' right after that, I got 'Already publishing' Another thing I've noticed is that the deployed project is in state : 'Started, Republish' is this state correct? What does it mean? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

13
27
0 / 0

[JBoss JIRA] (JBIDE-10347) Invalid menu location for the 'Explore' item

by Xavier Coulon (Created) (JIRA)

Invalid menu location for the 'Explore' item -------------------------------------------- Key: JBIDE-10347 URL: https://issues.jboss.org/browse/JBIDE-10347 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Rob Stryker Priority: Minor Fix For: 3.3.0.Beta1 The following stack trace appears at startup (I already have servers configured in the servers view): !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator". !STACK 0 java.lang.IllegalArgumentException: can't find ID org.eclipse.wst.server.ui.internal.cnf.serverEtcSectionEnd at org.eclipse.jface.action.ContributionManager.insertBefore(ContributionManager.java:359) at org.eclipse.jface.action.ContributionManager.insertBefore(ContributionManager.java:350) at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:123) at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:221) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:216) at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:173) at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:260) at org.eclipse.ui.navigator.CommonNavigatorManager$4.menuAboutToShow(CommonNavigatorManager.java:275) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:342) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:473) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:469) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:495) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:247) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1461) at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:805) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5525) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:73) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:277) at org.eclipse.swt.widgets.Display.runPopups(Display.java:4051) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3606) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] (JBIDE-10194) Exception after changing view-id attribute of page tag in pages.xml file

by Daniel Azarov (Created) (JIRA)

Exception after changing view-id attribute of page tag in pages.xml file ------------------------------------------------------------------------ Key: JBIDE-10194 URL: https://issues.jboss.org/browse/JBIDE-10194 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.M4 Reporter: Daniel Azarov Assignee: Alexey Kazakov Test Case: EXECUTE: 1. Import jboss-seam-jpa project. 2. Open pages.xml file 3. Change view-id="/confirm.xhtml" to view-id="/coirm.xhtml" 4. Save file 5. Change view-id="/coirm.xhtml" to view-id="/confirm.xhtml" 6. Save file FAIL: Exception: org.eclipse.core.runtime.AssertionFailedException: null argument:The dialog should be created in UI thread at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.jface.dialogs.IconAndMessageDialog.getSWTImage(IconAndMessageDialog.java:282) at org.eclipse.jface.dialogs.IconAndMessageDialog.getErrorImage(IconAndMessageDialog.java:233) at org.eclipse.jface.dialogs.MessageDialog.<init>(MessageDialog.java:179) at org.jboss.tools.common.model.ui.wizards.one.ServiceDialogImpl.showDialog(ServiceDialogImpl.java:62) at org.jboss.tools.common.model.impl.RegularObjectImpl.elementExists(RegularObjectImpl.java:151) at org.jboss.tools.common.model.impl.RegularObjectImpl.set(RegularObjectImpl.java:134) at org.jboss.tools.seam.pages.xml.model.impl.ReferenceObjectImpl.set(ReferenceObjectImpl.java:98) at org.jboss.tools.common.meta.impl.adapters.XAdapterModelElement.setProperty(XAdapterModelElement.java:26) at org.jboss.tools.common.model.impl.XModelObjectImpl.set_0(XModelObjectImpl.java:162) at org.jboss.tools.common.model.impl.XModelObjectImpl.setAttributeValue(XModelObjectImpl.java:188) at org.jboss.tools.seam.pages.xml.model.helpers.SeamPagesDiagramHelper.updateDiagram0(SeamPagesDiagramHelper.java:96) at org.jboss.tools.seam.pages.xml.model.helpers.SeamPagesDiagramHelper.updateDiagram(SeamPagesDiagramHelper.java:68) at org.jboss.tools.seam.pages.xml.model.FileSeamPagesImpl.mergeAll(FileSeamPagesImpl.java:47) at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.edit(AbstractExtendedXMLFileImpl.java:261) at org.jboss.tools.jst.web.model.AbstractWebDiagramLoader.update(AbstractWebDiagramLoader.java:57) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.reload(FolderImpl.java:686) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:597) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateAuxiliary(FolderImpl.java:557) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:381) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:582) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:405) at org.jboss.tools.common.model.filesystems.impl.FileSystemFolderLoader.update(FileSystemFolderLoader.java:28) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.update(FileSystemsLoader.java:68) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.doUpdate(FileSystemsImpl.java:343) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.access$4(FileSystemsImpl.java:337) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl$UpdateRunnable.run(FileSystemsImpl.java:326) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:178) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
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 January 2012