May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11616) When a new ESB project is created, the jboss-esb.xml file is displayed as raw XML, not in the ESB editor

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-11616: ------------------------------------ Summary: When a new ESB project is created, the jboss-esb.xml file is displayed as raw XML, not in the ESB editor Key: JBIDE-11616 URL: https://issues.jboss.org/browse/JBIDE-11616 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.0.Beta3-SOA Environment: Version: Indigo Service Release 2 Build id: 20120208-2150 http://download.jboss.org/jbosstools/updates/nightly/trunk/ http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/ Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Priority: Critical Fix For: 3.3.0.Beta3-SOA File->New->Other->ESB->ESB Project When a new ESB project is created, the jboss-esb.xml file is displayed as raw XML, not in the ESB editor. This problem is not being seen in the beta3 JBDS builds. -- 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

13 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-1778) JBDS50_0430: [COMMIT] (Dev) Document/QA Maven Archetypes

by mark yarborough (JIRA)

JBDS50_0430: [COMMIT] (Dev) Document/QA Maven Archetypes -------------------------------------------------------- Key: JBDS-1778 URL: https://issues.jboss.org/browse/JBDS-1778 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough Fix For: 5.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1769) JBDS50_0425: [COMMIT] (Dev) Modular Delivery (eg. SOA plug-ins)

by mark yarborough (JIRA)

JBDS50_0425: [COMMIT] (Dev) Modular Delivery (eg. SOA plug-ins) --------------------------------------------------------------- Key: JBDS-1769 URL: https://issues.jboss.org/browse/JBDS-1769 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] (JBDS-2160) Starting (and not even completing) an install of SOA tooling from JBoss Central inserts a download site into the 'Available Software Sites'

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2160: ---------------------------------- Summary: Starting (and not even completing) an install of SOA tooling from JBoss Central inserts a download site into the 'Available Software Sites' Key: JBDS-2160 URL: https://issues.jboss.org/browse/JBDS-2160 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 5.0.0.Beta3 Environment: Version: 5.0.0.Beta3 Build id: v20120514-2058-H159-Beta3 Build date: 20120514-2058 Reporter: Len DiMaggio Assignee: Douglas Palmer Priority: Blocker Fix For: 5.0.0.CR1 To recreate: 1) Install beta3 2) Select JBoss Central/Install - select SOA tooling - then cancel the install 3) This site is added to the 'Available Software Sites': JBoss Developer Studio Central Update Site - SOA Tooling http://devstudio.jboss.com/updates/5.0/staging/central/soa-tooling/ This happens regardless of any edits made to studio/jbdevstudio.ini -- 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

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-11906) import.xml should publish/run without needing to delete the application and then republish it

by Jim Tyrrell (JIRA)

Jim Tyrrell created JBIDE-11906: ----------------------------------- Summary: import.xml should publish/run without needing to delete the application and then republish it Key: JBIDE-11906 URL: https://issues.jboss.org/browse/JBIDE-11906 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jim Tyrrell Using the jboss-javaee6-webapp sample application. Once I have published the application, I need to delete the webapplication when I am making only changes to the import.sql file. This should be "published" without me needing to do so many keystrokes. -- 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

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] (JBDS-2162) CLONE - should maven.apt feature be included in JBDS or JBDS Extras?

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2162: -------------------------------- Summary: CLONE - should maven.apt feature be included in JBDS or JBDS Extras? Key: JBDS-2162 URL: https://issues.jboss.org/browse/JBDS-2162 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Components: central, maven, updatesite Affects Versions: 5.0.0.CR1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.CR1 Noticed that while maven.gwt is on the JBT Nightly site (http://download.jboss.org/jbosstools/updates/nightly/core/trunk/features/...), it's not in JBDS Product, JBDS Extras, or JBDS Central. Should it be? -- 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

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] (JBIDE-10588) Installing JBoss Maven Seam Integration plugin breaks Maven integration for WTP

by Rafal Krzewski (Created) (JIRA)

Installing JBoss Maven Seam Integration plugin breaks Maven integration for WTP ------------------------------------------------------------------------------- Key: JBIDE-10588 URL: https://issues.jboss.org/browse/JBIDE-10588 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.M5 Environment: Eclipse 3.7.1.20110916-0149, m2e 1.0.100.20110804-1717, m2e-wtp 0.14.0.20110928-2045 Reporter: Rafal Krzewski Assignee: Fred Bricon After installing istalling JBoss Maven Seam Integration plugin from http://download.jboss.org/jbosstools/updates/development/indigo/ m2e-wtp configurator stopped working. Running Maven > Update Configuration produces to following error on any project that is using war or ejb packaging (ear is OK): Project configurator "org.jboss.tools.maven.seam.configurator" is not available. To enable full functionality, install the project configurator and run Maven->Update Project Configuration. Additionally, maven-ejb-plugin and maven-war-plugin executions are reported as not covered by by lifecycle configuration. I've checked with OSGi host console and org.jboss.tools.maven.seam bundle is deployed: osgi> ss org.jboss.tools.maven.seam id State Bundle 774 ACTIVE org.jboss.tools.maven.seam_1.3.0.v20111209-0524-H40-M5 The configurator extension is also deployed: osgi> pt -v org.eclipse.m2e.core.projectConfigurators Extension(s): ------------------- null [from org.jboss.tools.maven.seam] <configurator> id = org.jboss.tools.maven.seam.configurator class = org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator name = Seam secondaryTo = org.maven.ide.eclipse.configuration.wtp.configurator </configurator> Alas, the configurator class cannot be instantiated. Eclipse error log contains the following: Plug-in "org.jboss.tools.maven.seam" was unable to instantiate class "org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator". An exception stack trace is not available. -- 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

13 years, 10 months

9
28
0 / 0

[JBoss JIRA] (JBIDE-10120) find a way to display a project example once when several versions targeted for different runtimes exist

by Fred Bricon (Created) (JIRA)

find a way to display a project example once when several versions targeted for different runtimes exist -------------------------------------------------------------------------------------------------------- Key: JBIDE-10120 URL: https://issues.jboss.org/browse/JBIDE-10120 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M3 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.0.Beta1 Given the upcoming (40+) new quickstart projects, we'll most likely have duplicates between the community and enterprise versions. In order to reduce the amount of quickstarts in the Project Examples UI, in addtion to adding a Runtime filter (JBIDE-10119), we could also regroup similar projects under one entry. So, for example, instead of seeing 2 entries for kitchensink (community) and kitchensink (eap6) We could display only one kitchensink entry in the UI, and upon selection, choose the actual version / target runtime we want to create. -- 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

13 years, 10 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-11853) NPE when deleting program arguments in launch configuration with EAP5

by Martin Malina (JIRA)

Martin Malina created JBIDE-11853: ------------------------------------- Summary: NPE when deleting program arguments in launch configuration with EAP5 Key: JBIDE-11853 URL: https://issues.jboss.org/browse/JBIDE-11853 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Environment: jbdevstudio-product-universal-5.0.0.v201205101833M-H138-Beta3.jar JBoss EAP 5.1.2 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.0.CR1 When you delete all the Program arguments in launch configuration of a EAP5 server, you get a NPE. This is in the error log: {code} !ENTRY org.eclipse.ui 4 4 2012-05-14 15:22:38.224 !MESSAGE An internal error has occurred. !STACK 0 java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.util.ArgsUtil.parse(ArgsUtil.java:34) at org.jboss.ide.eclipse.as.core.util.ArgsUtil.getValue(ArgsUtil.java:106) at org.jboss.ide.eclipse.as.ui.launch.JBossLaunchConfigurationTabGroup$JavaArgumentsTabExtension.isValid(JBossLaunchConfigurationTabGroup.java:189) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.refresh(LaunchConfigurationTabGroupViewer.java:463) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.updateButtons(LaunchConfigurationPropertiesDialog.java:185) at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.updateLaunchConfigurationDialog(AbstractLaunchConfigurationTab.java:107) at org.eclipse.debug.ui.AbstractLaunchConfigurationTab$1.runInUIThread(AbstractLaunchConfigurationTab.java:430) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1132) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:203) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:629) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:606) at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:588) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) 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:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) 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: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) {code} -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11488) Configuration folder is not selected by default

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11488: --------------------------------------- Summary: Configuration folder is not selected by default Key: JBIDE-11488 URL: https://issues.jboss.org/browse/JBIDE-11488 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Environment: The nightly build from 5th April 2012 Reporter: Lucia Jelinkova Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta3 Attachments: server.jpeg When creating a new server runtime for e. g. EAP 5, the configuration directory is not selected by default (see attached screenshot). -- 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

13 years, 10 months

5
23
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 May 2012