August 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2115) Include JBoss Java Formatter and Code cleanup

by Karel Piwko (JIRA)

Karel Piwko created JBDS-2115: --------------------------------- Summary: Include JBoss Java Formatter and Code cleanup Key: JBDS-2115 URL: https://issues.jboss.org/browse/JBDS-2115 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Beta2 Reporter: Karel Piwko It would be great if JBoss Java Code style formatter and code cleanup are installed out of the box in JBDS. It is not required for them to be default, but user can select them easily. Here are the sources: https://github.com/jbossas/jboss-as/tree/master/ide-configs/eclipse This would make developers using JBDS produce properly formatted code an easier way. -- 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

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Libor Zoubek (JIRA)

AS7 does not pick hot-deployed jsp files ---------------------------------------- Key: JBIDE-9563 URL: https://issues.jboss.org/browse/JBIDE-9563 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 Reporter: Libor Zoubek Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M3 When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2183) Ctrl+shift+G binding causing warnings - can it be avoided ?

by Max Rydahl Andersen (JIRA)

Ctrl+shift+G binding causing warnings - can it be avoided ? ----------------------------------------------------------- Key: JBIDE-2183 URL: http://jira.jboss.com/jira/browse/JBIDE-2183 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.0.CR1 Reporter: Max Rydahl Andersen Fix For: 2.1.0.GA in latest cr1 I get the following in the Error log at startup: eclipse.buildId=1.1.0.CR1 java.version=1.6.0_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK Command-line arguments: -os win32 -ws win32 -arch x86 Warning Tue May 06 15:03:32 CEST 2008 Keybinding conflicts occurred. They may interfere with normal accelerator operation. Warning Tue May 06 15:03:32 CEST 2008 A conflict occurred for CTRL+SHIFT+G: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
26
0 / 0

[JBoss JIRA] Created: (JBIDE-1674) Hibernate Properties - like was in Exadel ORM

by Vitali Yemialyanchyk (JIRA)

Hibernate Properties - like was in Exadel ORM --------------------------------------------- Key: JBIDE-1674 URL: http://jira.jboss.com/jira/browse/JBIDE-1674 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Reporter: Vitali Yemialyanchyk Assigned To: Vitali Yemialyanchyk Priority: Minor Attachments: screenshot-1.jpg Hibernate Configuration Wizard (screenshot1) has very convinient way to setup properties for hibernate.cfg.xml (screenshot2). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
38
0 / 0

[JBoss JIRA] (JBDS-2227) fix jmx versions

by Max Rydahl Andersen (JIRA)

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] (JBDS-2226) fix projectarchives versioning

by Max Rydahl Andersen (JIRA)

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] (JBIDE-11383) Replace the unpack attribute in the feature.xml files by the Eclipse-BundleShape header in manifest.mf files

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-11383: ---------------------------------------- Summary: Replace the unpack attribute in the feature.xml files by the Eclipse-BundleShape header in manifest.mf files Key: JBIDE-11383 URL: https://issues.jboss.org/browse/JBIDE-11383 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Visual Page Editor core, Visual Page Editor Templates, XULRunner Affects Versions: 3.3.0.Beta2 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.0.Beta3 All the {{unpack}} attributes should be replaced by the {{Eclipse-BundleShape}} headers in all plugins in vpe and xulrunner components. The {{Eclipse-BundleShape}} header of manifest.mf allows to define will be or not be a given plugin unpacked. It is simpler than specifying of the {{unpack}} attribute in all features, which contain this plugin. More details: [OSGi Bundle Manifest Headers Reference|http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pl...] > The Eclipse-BundleShape Header. *Note:* xulrunner for Beta2 is building directly from trunk. Do not perform these changes in xulrunner component until 3.3.0.Beta2 is shipped (see JBIDE-11353)! -- 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

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] (JBIDE-12126) Inform user that the selected project does not contain portlet.xml file

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12126: --------------------------------------- Summary: Inform user that the selected project does not contain portlet.xml file Key: JBIDE-12126 URL: https://issues.jboss.org/browse/JBIDE-12126 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Portal/GateIn Affects Versions: 3.3.0.CR1 Reporter: Lucia Jelinkova Assignee: Snjezana Peco Fix For: 3.3.1 When I try to create a Java portlet for a Dynamic web project that does not have the portlet.xml file, the error is logged into Error log. {code} java.lang.RuntimeException: The portlet.xml file doesn't exist at org.jboss.tools.portlet.ui.PortletUIActivator.getPortletXmlFile(PortletUIActivator.java:90) at org.jboss.tools.portlet.ui.internal.wizard.NewPortletClassDataModelProvider.validate(NewPortletClassDataModelProvider.java:353) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.validate(DataModelImpl.java:377) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.isValid(DataModelImpl.java:423) at org.eclipse.jst.servlet.ui.internal.wizard.NewWebArtifactWizard.canFinish(NewWebArtifactWizard.java:66) at org.eclipse.jface.wizard.WizardDialog.updateButtons(WizardDialog.java:1345) at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1334) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1265) at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239) at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1226) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:257) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) {code} However, if user does not have error log displayed he / she has no clue what has happened. Could you provide a warning in the wizard about missing portlet.xml file (and that it won't be generated automatically)? In that case the message's severity in Error log can be changed from error to warning too. -- 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

12 years, 1 month

4
17
0 / 0

[JBoss JIRA] Created: (JBIDE-6072) rich:panel do not render its surplus tags in VPE

by Denis Maliarevich (JIRA)

rich:panel do not render its surplus tags in VPE ------------------------------------------------ Key: JBIDE-6072 URL: https://jira.jboss.org/jira/browse/JBIDE-6072 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.1.0.GA Reporter: Denis Maliarevich Assignee: Denis Maliarevich Priority: Minor Fix For: 3.2.next Problem: On server rich:panel renders unwanted elements for instance additional footer facet in panel's content. But VPE does NOT show elements that are not allowed by richfaces tag specification. Solution: Show surplus tags in VPE for rich:panel. Example: <rich:panel> <f:facet name="header"> PHead111 <h:outputText>PanelHeader1</h:outputText> <h:outputText>PanelHeader2</h:outputText> <h:outputText>PanelHeader3</h:outputText> <span>P1Head</span> PHead </f:facet> <f:facet name="footer"> <h:outputText>Col 1 footer3</h:outputText> <span>COL1FOOT</span> C1FText FooterFacet </f:facet> Panel Content </rich:panel> Behaviour: Text "COL1FOOT C1FText FooterFacet" should be rendered in the panel's content. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3225) Components should render usual text inside

by Yura Zhishko (JIRA)

Components should render usual text inside ------------------------------------------ Key: JBIDE-3225 URL: https://jira.jboss.org/jira/browse/JBIDE-3225 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Minor 1) DND or create any component from the list below 2) Print usual text inside component ASSERT: Text should be rendered in VPE RESULT: Text isn't rendered Here is list of components with the same behavior: <rich:inplaceInput> <rich:inplaceSelect> <rich:inputNumberSlider> <rich:inputNumberSpinner> <rich:paint2D> <rich:spacer> <a4j:actionparam> <a4j:commandButton> <a4j:push> <a4j:log> <h:commandButton> <h:inputHidden> <h:inputText> <h:inputTextarea> <h:messages> <h:selectBooleanCheckbox> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2012