[JBoss JIRA] (JBIDE-23409) Server editor should allow 'edit...' option for selected username - followup
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23409?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23409:
----------------------------------
Attachment: runtimes.png
credentials.png
> Server editor should allow 'edit...' option for selected username - followup
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23409
> URL: https://issues.jboss.org/browse/JBIDE-23409
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, server
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: credentials.png, runtimes.png
>
>
> Today while creating a cdk server adapter, I noticed there is a new Edit button when selecting credentials for the adapter. This was recently added here: JBIDE-23382
> I would like to propose a change to make it consistent with other things like JREs when creating a server adapter.
> So in the server editor, we used to have just Add.. and now we also have Edit...:
> Similar thing in the New Server adapter.
> Now look at the New Runtime dialog:
> I think it would be nice to do it similarly, wdyt?
> Meaning, instead of Edit.. and Add.., we would simply have a button for "Credentials..." which would open the appropriate Preference page (and upon closing, you would need to update the content on the page to show any added credentials).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23409) Server editor should allow 'edit...' option for selected username - followup
by Martin Malina (JIRA)
Martin Malina created JBIDE-23409:
-------------------------------------
Summary: Server editor should allow 'edit...' option for selected username - followup
Key: JBIDE-23409
URL: https://issues.jboss.org/browse/JBIDE-23409
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk, server
Affects Versions: 4.4.2.AM3
Reporter: Martin Malina
Assignee: Rob Stryker
Today while creating a cdk server adapter, I noticed there is a new Edit button when selecting credentials for the adapter. This was recently added here: JBIDE-23382
I would like to propose a change to make it consistent with other things like JREs when creating a server adapter.
So in the server editor, we used to have just Add.. and now we also have Edit...:
Similar thing in the New Server adapter.
Now look at the New Runtime dialog:
I think it would be nice to do it similarly, wdyt?
Meaning, instead of Edit.. and Add.., we would simply have a button for "Credentials..." which would open the appropriate Preference page (and upon closing, you would need to update the content on the page to show any added credentials).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23010) landrush plugin prevents CDK server adapter from starting
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23010.
---------------------------------
Closing.
> landrush plugin prevents CDK server adapter from starting
> ---------------------------------------------------------
>
> Key: JBIDE-23010
> URL: https://issues.jboss.org/browse/JBIDE-23010
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Martin Malina
> Priority: Critical
> Fix For: 4.4.1.Final
>
>
> Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.)
> Then I stopped it, set up in devstudio and start there. Everything looks fine, but the server adapter is stuck at "Starting...".
> This is the console output:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: [landrush] virtualbox requires an additional private network; adding it
> ==> default: [landrush] starting dns server
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> ==> default: Machine booted and ready!
> ==> default: Registering box with vagrant-registration...
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Setting hostname...
> ==> default: Configuring and enabling network interfaces...
> [landrush] Using eth1 (172.28.128.3)
> ==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3
> ==> default: [landrush] adding static DNS entry: cdk => cdk.vm
> [landrush] Using eth1 (172.28.128.3)
> [landrush] Host DNS resolver config looks good.
> ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Mounting SSHFS shared folder...
> ==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp
> ==> default: Checking Mount..
> ==> default: Checking Mount..
> ==> default: Folder Successfully Mounted!
> ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always will still run.
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://openshift.cdk:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
> These are my plugins:
> {code}
> $ vagrant plugin list
> landrush (1.1.1)
> - Version Constraint: 1.1.1
> vagrant-registration (1.2.3)
> - Version Constraint: 1.2.3
> vagrant-service-manager (1.3.0)
> - Version Constraint: 1.3.0
> vagrant-share (1.1.5, system)
> vagrant-sshfs (1.2.0)
> - Version Constraint: 1.2.0
> {code}
> [1] http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23311) Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23311?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23311.
---------------------------------
OK, thanks for the comments, Rob. I'm satisfied :)
> Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1
> -----------------------------------------------------------------
>
> Key: JBIDE-23311
> URL: https://issues.jboss.org/browse/JBIDE-23311
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> Rather than reopening JBIDE-23161 to ask you about some discrepancies that I found, I am opening this JIRA.
> I compared the contents of org.jboss.tools.as.catalog_3.2.2.v20160923-0424.jar and what's in the wildfly 10.1.0 zip. And there are some diffs. I understand that there will always be more in the plugin - we keep some previous versions. But there are many xsd files missing in the plugin:
> {code}
> $ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> nattura:jar rasp$ find . -name javaee_7.xsd
> nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> {code}
> But I randomly checked one and it was visible in Preferences -> XML -> XML Catalog. My guess is that these are not ours so they will be present in some Eclipse plugin and we don't need to add them. Can you confirm this?
> And in that case, what would you recommend as the best option to verify that our catalog is correct and also that the jboss.org.schema git repo is correct?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (ERT-438) Nullpointer in JavaScript Development Tools Chromium/V8 Remote Debugger: BreakpointAdapterFactory [EBZ#496914]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-438?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny resolved ERT-438.
---------------------------------
Fix Version/s: Neon.2 (4.6)
(was: Oxygen (4.7))
Resolution: Done
Labels: 3.8.2 Debug bzira (was: 3.9 Debug bzira)
> Nullpointer in JavaScript Development Tools Chromium/V8 Remote Debugger: BreakpointAdapterFactory [EBZ#496914]
> --------------------------------------------------------------------------------------------------------------
>
> Key: ERT-438
> URL: https://issues.jboss.org/browse/ERT-438
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: Debug, bzira, 3.8.2
> Fix For: Neon.2 (4.6)
>
>
> Fresh installation of Eclipse Neon for Java EE Developers (contains the plugin 'JavaScript Development Tools Chromium/V8 Remote Debugger').
> Installed ResourceBundle Editor V1.0.5 via Eclipse marketplace.
> A Nullpointer occurs when opening any ResourceBundle file with ResourceBundle Editor. Stacktrace see end of post. After deinstalling the Chromium Debugger plugin, the nullpointer is not reproducable anymore and ResourceBundle Editor is working again.
> NPE probably caused by empty editorinput?
> IResource resource = (IResource) editorPart.getEditorInput().getAdapter(IResource.class);
> java.lang.NullPointerException
> at org.eclipse.wst.jsdt.chromium.debug.core.model.BreakpointAdapterFactory.getAdapter(BreakpointAdapterFactory.java:25)
> at org.eclipse.core.internal.adapter.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:82)
> at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:294)
> at org.eclipse.ui.part.WorkbenchPart.getAdapter(WorkbenchPart.java:143)
> at org.eclipse.ui.texteditor.AbstractTextEditor.getAdapter(AbstractTextEditor.java:6185)
> at com.essiembre.eclipse.rbe.ui.editor.i18n.I18nPageEditor.getAdapter(I18nPageEditor.java:90)
> at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:59)
> at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:100)
> at org.eclipse.ui.part.MultiPageEditorPart.getAdapter(MultiPageEditorPart.java:1199)
> at com.essiembre.eclipse.rbe.ui.editor.ResourceBundleEditor.getAdapter(ResourceBundleEditor.java:208)
> at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager$ToggleBreakpointsTargetAdapterFactory.canGetToggleBreakpointsTarget(ToggleBreakpointsTargetManager.java:318)
> at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager$ToggleBreakpointsTargetAdapterFactory.isEnabled(ToggleBreakpointsTargetManager.java:361)
> at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getEnabledFactories(ToggleBreakpointsTargetManager.java:502)
> at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getPreferredToggleBreakpointsTargetID(ToggleBreakpointsTargetManager.java:542)
> at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getToggleBreakpointsTarget(ToggleBreakpointsTargetManager.java:549)
> at org.eclipse.debug.internal.ui.actions.breakpoints.RetargetBreakpointAction.getAdapter(RetargetBreakpointAction.java:49)
> at org.eclipse.debug.internal.ui.actions.RetargetAction.partActivated(RetargetAction.java:169)
> at org.eclipse.ui.internal.PartService$1.run(PartService.java:84)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81)
> at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3002)
> at org.eclipse.ui.internal.WorkbenchPage$14.run(WorkbenchPage.java:4977)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4974)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4962)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:210)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:250)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:247)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:757)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682)
> at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:95)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$4.handleEvent(StackRenderer.java:1077)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349)
> at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1817)
> at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3215)
> at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3151)
> at org.eclipse.swt.widgets.Composite.gtk_button_press_event(Composite.java:750)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1979)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5819)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5490)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4141)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-814) Extend the scope of projects used for testing deployment/undeployment
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-814?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík commented on JBTIS-814:
------------------------------------
This issue is covered by _QuickStartsTest_. Unfortunately this tests are broken and need to be fixed! I'm working on it.
> Extend the scope of projects used for testing deployment/undeployment
> ---------------------------------------------------------------------
>
> Key: JBTIS-814
> URL: https://issues.jboss.org/browse/JBTIS-814
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 4.3.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.3.1.Final
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Extend the scope of projects used for testing deployment/undeployment. It seems that projects which were imported a an existing maven project cannot be successfully deployed/undeployed. Please see FUSETOOLS-1997
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-814) Extend the scope of projects used for testing deployment/undeployment
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-814?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík updated JBTIS-814:
-------------------------------
Original Estimate: 2 hours
Remaining Estimate: 2 hours
> Extend the scope of projects used for testing deployment/undeployment
> ---------------------------------------------------------------------
>
> Key: JBTIS-814
> URL: https://issues.jboss.org/browse/JBTIS-814
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 4.3.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.3.1.Final
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Extend the scope of projects used for testing deployment/undeployment. It seems that projects which were imported a an existing maven project cannot be successfully deployed/undeployed. Please see FUSETOOLS-1997
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months