[JBoss JIRA] (TOOLSDOC-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-345:
------------------------------------------
[~rob.stryker]: I have a couple of statements about server instances, server adapters, and remote servers that I need you to verify. These derive from the understanding I am piecing together and might be woefully incorrect.
Local servers:
1. You have a server runtime environment (e.g., EAP 6.0).
2. From this you can create many server instances (e.g., my_EAP1, my_EAP2).
3. The IDE needs a server adapter for each server instance so that the IDE and server instance can communicate.
4. The new server wizard creates both the server instance and server adapter for local servers.
5. Server adapters are listed in the servers tab. But for the main part local server instances and their adapters can be considered as one within the IDE.
Remote servers:
6. Instead of a local server instance, you can have an existing remote server.
7. As with local server instances, the IDE needs a server adapter to communicate with remote servers.
8. To create a server adapter for a remote server, the server runtime environment of the remote system must be installed on the local system where the IDE is running. [Basically so they can share a common language/API/instruction set.]
9. The new server wizard only creates the server adapter for remote servers.
10. Again the server adapter is listed in the servers tab.
> NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
> ---------------------------------------------------------------
>
> Key: TOOLSDOC-345
> URL: https://issues.jboss.org/browse/TOOLSDOC-345
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Server Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> I am trying to distinguish which features are provided by Eclipse and which are provided by JBoss Server Tools so that I can accurately document JBoss Server Tools.
> The unique JBoss Server Tools features I have are:
> * automatic runtime detection
> * ability to download and install a JBoss runtime
> * JBoss Server Editor - lots of the panes in the overview tab are unique and * the deployment tab is completely unique
> * set a default server icon
> * set default filesets
> * set default classpath entries
> * create new server wizard also seems different for JBoss enterprise and community servers than in the wizard in Eclipse alone
> What have I missed?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13003) No support for inheritance in JAX-RS API scan
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13003?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-13003:
----------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.1.0.Beta2)
> No support for inheritance in JAX-RS API scan
> ---------------------------------------------
>
> Key: JBIDE-13003
> URL: https://issues.jboss.org/browse/JBIDE-13003
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.0.0.Alpha2
> Reporter: Ron Ratovsky
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha1
>
>
> Assume:
> class BaseRest {
> @POST
> public Response save(Object o) {
> ....
> }
> }
> @Path("/url")
> class RealRest extends BaseRest {}
> The JAX-RS tools won't add a "POST /url" entry to the JAX-RS calls overview.
> While not tested (due to another bug) - they may also apply to definitions of @PathParam's in the parent class.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13987) Improve project wizards in JBoss Central : Proxy Wizards
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13987?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-13987:
------------------------------------
I tried in with JBDS yesterday, but with no luck.
> Improve project wizards in JBoss Central : Proxy Wizards
> --------------------------------------------------------
>
> Key: JBIDE-13987
> URL: https://issues.jboss.org/browse/JBIDE-13987
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy, respin-b
> Fix For: 4.1.0.Beta1
>
> Attachments: www.tar.gz
>
>
> The "Start from scratch" section (formerly known as Project section) in JBoss Central needs to support the following requirements :
> - wizard list (label/order/description) must be updateable remotely
> - show wizards (including the proper icon) even if their contributing plugins are missing
> - when clicking on the wizard link in JBoss Central, if the wizard is available then open it, else, install the required plugins
> The general idea here is to use some kind of proxy wizard. A proxy wizard model should have the following attributes :
> - id : the proxy wizard id
> - label : the proxy wizard label shown in JBoss Central
> - wizardId : the real wizard id used by Central to open the wizard dialog
> - iconPath : the path to the wizard icon (independent of required connector)
> - description : the description shown in Central when hovering over the wizard link
> - requiredConnectorIds : the connector ids to install if the real wizard is not available
> - priority : order in which the wizard is displayed in JBoss Central
> The proxy wizards will be declared in the jboss-discovery.jar plugin.xml (to minimize build / maintenance overhead). The jar will also include the required icons.
> The jar will be fetched remotely by the discovery mechanism but a cached version must be kept for offline usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14790) Unable to create Seam Web Project
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14790?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-14790.
------------------------------
> Unable to create Seam Web Project
> ---------------------------------
>
> Key: JBIDE-14790
> URL: https://issues.jboss.org/browse/JBIDE-14790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1 installed from eclipse marketplace
> Reporter: Radim Hopp
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta2
>
>
> I'm unable to create Seam Web Project (File->New->Other->Seam->Seam Web Project)
> This exception appears immediately, when New Seam Project wizard is shown:
> {noformat}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.seam.ui.internal.project.facet.SeamInstallWizardPage)
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
> 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:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
> 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:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.seam.ui.internal.project.facet.SeamInstallWizardPage
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at java.lang.Class.newInstance0(Class.java:374)
> at java.lang.Class.newInstance(Class.java:327)
> at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.create(ProjectFacetsUiManagerImpl.java:170)
> at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:148)
> at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:108)
> at org.eclipse.wst.common.project.facet.ui.ProjectFacetsUiManager.getWizardPages(ProjectFacetsUiManager.java:30)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.handleSelectedFacetsChangedEvent(ModifyFacetedProjectWizard.java:712)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.access$0(ModifyFacetedProjectWizard.java:670)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$1$1.run(ModifyFacetedProjectWizard.java:166)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 51 more
> {noformat}
> And this one when clicking on Finish button:
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:340)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> 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.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
> 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:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
> 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:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14791) cannot rename deployed modules in AS7 server adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14791?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14791:
-------------------------------------
This behavior is expected as currently implemented. You cannot modify a deploy location once the file is added to the server. You may only modify the deploy locations when a server has NO elements deployed to it AND the server is stopped.
Otherwise, you are potentially modifying the deploy location of a running module, and thsi will lead to deploys in two concurrent locations. WTP lacks a delta model, so changing this property on the server will only alert me that a new deploy location is set, and I will be unable to access the PREVIOUS deploy location to properly clean up.
Because of this, users may only modify the deploy location BEFORE deploying.
Here is the workflow of a proper usecase:
1) Create server
2) Create dynamic web project
3) Open server editor, go to deployment page, set your project to be named 'test.war'
4) Add your module to the server, either via drag and drop, or the add/remove module wizard
5) Ensure a publish is executed
6) Right-click the server, select show-in, select file browser.
7) Verify that the module was properly published as test.war.
This use case works 100% for me. Any other workflow is incorrect as currently implemented.
If you already have a module added to your server, and wish to change its deploy location, execute the following steps:
1) Remove the module from the server
2) Ensure a publish is executed
3) Stop the server
4) Open the server editor deployment tab, verify the editor is enabled.
5) Modify the deploy location
6) Add the module to server, publish, and start server.
This is the only valid workflow, and HAS BEEN the only valid workflow, for several months. This workflow still functions and has not changed at all.
> cannot rename deployed modules in AS7 server adapter
> ----------------------------------------------------
>
> Key: JBIDE-14791
> URL: https://issues.jboss.org/browse/JBIDE-14791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: deployments-greyed-out.png
>
>
> The as7 server adapter seem not to allow one to rename deployed modules.
> i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in /
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13965) Wrong datasource driver when EAP 6.1 server is present
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13965?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13965:
-------------------------------------
I've reviewed the PR, but decided to do a bit more cleanup here in this internal code. The original structure was clean, but over the past few releases the class got messy and disorganized, specifically with the introduction of as7.
I can't move these properties to extendedProperties yet, because it seems I'd be adding a dependencey and i'm not ready to do that, but, I can definitely organize the clsas better.
Will attach a new PR and push it in.
> Wrong datasource driver when EAP 6.1 server is present
> ------------------------------------------------------
>
> Key: JBIDE-13965
> URL: https://issues.jboss.org/browse/JBIDE-13965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Environment: JBDS 7.0.0.Alpha B135
> Seam 2.3.1.Final (WFK 2.2.0)
> EAP 6.1.0.ER4
> EAP 6.0.1.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta2
>
> Attachments: scr.png
>
>
> When you try to create a Seam Web Project, but have EAP 6.1 defined in the workspace (along with EAP 6.0.1 that I wanted to use for the seam project), the generated project has this in the ds.xml inside resources:
> <driver>jboss-eapnull</driver>
> Also, there is no driver jar in the resources folder.
> This is probably because both servers created their DefaultDS connection profile in Eclipse with the same name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months