[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:
------------------------------------
Hi [~fbricon], I'm having troubles with veryfiying this JIRA.
I've created jbosstools-directory.xml and org.jboss.tools.central.directory.jar (I just took the one from JBT updatesite and modified its plugin.xml and plugin.properties). I just changed few labels to see if those changes will be propagated to JBT (to verify that my setup is correct).
I have jbosstools-directory.xml and org.jboss.tools.central.directory.jar located in my root www folder and both are accesible via http (http://localhost/jbosstools-directory.xml, http://localhost/org.jboss.tools.central.discovery.jar)
{noformat:title=jbosstools-directory.xml}
<?xml version='1.0' encoding='UTF-8'?>
<directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<entry url="org.jboss.tools.central.discovery.jar" permitCategories="true"/>
</directory>
{noformat}
{noformat:title=eclipse.ini}
$ cat eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20130327-1440
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Djboss.discovery.directory.url=http://localhost/jbosstools-directory.xml
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
{noformat}
But after these steps, the changes I made are not reflected in JBT. Am I missing something?
> 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
>
>
> 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-14736) JQuery html page looks broken in Internal Web Browser when VPE is installed
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14736?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-14736:
-------------------------------------
Summary: JQuery html page looks broken in Internal Web Browser when VPE is installed (was: JQuery html page looks broken in Inetnal Web Browser when VPE is installed)
> JQuery html page looks broken in Internal Web Browser when VPE is installed
> ---------------------------------------------------------------------------
>
> Key: JBIDE-14736
> URL: https://issues.jboss.org/browse/JBIDE-14736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.1.0.Beta1
> Environment: Linux, x86_64
> Reporter: Denis Golovin
> Assignee: Yahor Radtsevich
> Fix For: 4.1.0.Beta2
>
> Attachments: jquery-internal-browser.png
>
>
> Internal Web Browser cannot load JQuery pages if VPE editor is installed.
> !jquery-internal-browser.png!
> works fine for plain eclipse
--
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-13289) Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13289?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-13289.
------------------------------
Verified in jbt 4.1.0.Beta1b build.
> Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-13289
> URL: https://issues.jboss.org/browse/JBIDE-13289
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: testing-tools
> Reporter: Lukáš Fryč
> Assignee: Snjezana Peco
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> {{-Darquillian.debug=true}} allow more insight into test lifecycle and drastically improves debugging experience by outputting call tree of Arquillian event system.
> There is sample call tree for debugging Warp client-side [full tree|https://gist.github.com/4270739]:
> {code}
> ...
> (E) Before
> (I) TestContextHandler.createSuiteContext
> (I) TestContextHandler.createClassContext
> (E) TestClass
> (I) TestContextHandler.createTestContext
> (I) ContainerEventController.createBeforeContext
> (O) DroneConfigurator.configureDrone
> (O) TestInstanceEnricher.enrich
> (E) BeforeEnrichment
> (E) RequireProxy
> (O) ProxyObserver.requireProxy
> (E) StartProxy
> (O) ProxyObserver.startProxy
> (E) AfterEnrichment
> (O) ClientBeforeAfterLifecycleEventExecuter.on
> (E) Test
> (I) TestContextHandler.createSuiteContext
> ...
> {code}
> Similarly for container.
> ----
> The problem with debugging is that people need to setup VM arguments in Container Configuration
> and then setup JUnit/TestNG VM arguments for each *executed test specifically*.
> ----
> This button switch in toolbar should allow to add {{-Darquillian.debug=true}} to executed test (either JUnit or TestNG) and also into container configuration.
--
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-14789) CordovaSim: remember cordovasim size/window position.
by Konstantin Marmalyukov (JIRA)
Konstantin Marmalyukov created JBIDE-14789:
----------------------------------------------
Summary: CordovaSim: remember cordovasim size/window position.
Key: JBIDE-14789
URL: https://issues.jboss.org/browse/JBIDE-14789
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: browsersim
Affects Versions: 4.1.0.Beta2
Reporter: Konstantin Marmalyukov
Assignee: Konstantin Marmalyukov
Fix For: 4.1.0.Beta2
BrowserSim remember its window position. Need to do the same for CordovaSim.
--
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-14755) Closing Selection Tag Bar in VPE throws NullPointerException
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14755?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-14755.
--------------------------------------------
Resolution: Duplicate Issue
> Closing Selection Tag Bar in VPE throws NullPointerException
> ------------------------------------------------------------
>
> Key: JBIDE-14755
> URL: https://issues.jboss.org/browse/JBIDE-14755
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Beta2
>
>
> {code}java.lang.NullPointerException
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$12.propertyChange(MozillaEditor.java:510)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:375)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:372)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.setValue(ScopedPreferenceStore.java:813)
> at org.eclipse.jface.preference.BooleanFieldEditor.doStore(BooleanFieldEditor.java:178)
> at org.eclipse.jface.preference.FieldEditor.store(FieldEditor.java:680)
> at org.eclipse.jface.preference.FieldEditorPreferencePage.performOk(FieldEditorPreferencePage.java:343)
> at org.jboss.tools.vpe.editor.preferences.VpePreferencesPage.performOk(VpePreferencesPage.java:171)
> at org.eclipse.jface.preference.PreferencePage.performApply(PreferencePage.java:432)
> at org.eclipse.jface.preference.PreferencePage$2.widgetSelected(PreferencePage.java:281)
> 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.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> 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){code}
--
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-13473) Should provide "Runtime Container" option if none are apecified
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13473?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-13473.
------------------------------
Verified in jbt 4.1.0.Beta1b build.
> Should provide "Runtime Container" option if none are apecified
> ---------------------------------------------------------------
>
> Key: JBIDE-13473
> URL: https://issues.jboss.org/browse/JBIDE-13473
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: testing-tools
> Affects Versions: 4.0.0.Final
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> Steps
> new Maven project
> configure Arquillian
> create new Arquillian Test Case
> Run As Arquillian Test case
> 'Launching MyBeanTestCase has encountered and error. Arquillian tests require at least one container on classpath"
> If no profiles are active and/or none are defined as default, the plugin should suggest which profiles/containers to run this test with.
--
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