[JBoss JIRA] (JBIDE-13866) openshift-java-client: remove hard coded (standalone) cartridges from tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13866?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13866:
------------------------------------------
pushed new client code to master
> openshift-java-client: remove hard coded (standalone) cartridges from tests
> ---------------------------------------------------------------------------
>
> Key: JBIDE-13866
> URL: https://issues.jboss.org/browse/JBIDE-13866
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
>
> We currently still have hard coded (standalone) cartridges in our integration tests (not the client code which is not depending on specific cartridges). If we want to have the OpenShift team running our integration test we have to remove those. This is because they may replace existing by new cartridges and therefore can't run our integration tests against new DEVENVs (ex. a dev pinged me and told me he was working on upgrading the php cartridge to a higher version).
--
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
13 years
[JBoss JIRA] (JBIDE-13898) Update ESB tests to support latest SOA-P 5.3.x and new SOA-P 6 Alpha runtimes
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13898?page=com.atlassian.jira.plugi... ]
Len DiMaggio reassigned JBIDE-13898:
------------------------------------
Assignee: Len DiMaggio (was: Brian Fitzpatrick)
> Update ESB tests to support latest SOA-P 5.3.x and new SOA-P 6 Alpha runtimes
> -----------------------------------------------------------------------------
>
> Key: JBIDE-13898
> URL: https://issues.jboss.org/browse/JBIDE-13898
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 4.0.0.Alpha1-SOA, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
>
> Found two test classes which refer to SOA-P 5. They should be updated to refer to the latest 5.3.x *AND* new 6.0.0.Alpha bits, so both are available for testing.
> {code:title=jbosstools-esb/tests/org.jboss.tools.esb.project.core.test/pom.xml}
> <configuration>
> <url>http://***********/soa-5.3.0.ER5/soa-p-5.3.0.ER5.zip</url>
> <md5>**********</md5>
> <unpack>true</unpack>
> {code}
> {code:title=jbosstools-integration-tests/tests/org.jboss.tools.esb.ui.bot.test/pom.xml}
> <configuration>
> <url>http://***********/soa-5.3.0.GA/soa-p-5.3.0.GA.zip</url>
> <md5>**********</md5>
> <unpack>true</unpack>
> {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
13 years
[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13856:
-----------------------------------------------
We use swt's widget org.eclipse.swt.browser.Browser. It's implementation (at least in Ubuntu) can create either Mozilla or WebKit browser, nothing else. We should study what other options we have in environments where neither Mozilla nor WebKit start. And, sure, if browser cannot start, wizard should just work without it.
> Test jQuery Mobile Palette Wizards on different platforms
> ---------------------------------------------------------
>
> Key: JBIDE-13856
> URL: https://issues.jboss.org/browse/JBIDE-13856
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
> Attachments: ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png
>
>
> If system font size is set to large, wizard should take it into account.
> For instance:
> !ubuntu_64_large_font_toggle.png!
> Windows 8 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 8 64bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4373)
> at org.eclipse.swt.SWT.error(SWT.java:4288)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4399)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:431)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:790)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> Windows 8 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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: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: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: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> MacOs 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> and
> MacOs 64 bit (Eclipse+Java) Base+JST:
> jQuery Mobile Palette Widget Wizards work fine.
--
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
13 years
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-13768:
-----------------------------------
Assignee: Martin Malina (was: Rob Stryker)
hey martin: do you have an environment to test this? Thanks.
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Reporter: Burr Sutter
> Assignee: Martin Malina
> Attachments: Error_Failed_to_start.png, failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.png)
--
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
13 years
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-13599:
-------------------------------------------
Assignee: Fred Bricon (was: Snjezana Peco)
Fred is looking and applying this.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years
[JBoss JIRA] (JBIDE-13899) Update Server tests to support latest EAP 6.0.x and 6.1.0.x
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13899?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13899:
-------------------------------
Assignee: Rob Stryker (was: Snjezana Peco)
> Update Server tests to support latest EAP 6.0.x and 6.1.0.x
> -----------------------------------------------------------
>
> Key: JBIDE-13899
> URL: https://issues.jboss.org/browse/JBIDE-13899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, JBossAS/Servers
> Affects Versions: 4.0.2.Final, 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
>
> Found test classes which refer to JBEAP 6.0 and/or 6.1. They should be updated to refer to the latest 6.0.x AND new 6.1.0.x bits, so both are available for testing.
> {code:title=contains ref to only 6.0. Should it contain 6.1 too?}
> jbosstools-integration-tests/tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml
> jbosstools-integration-tests/tests/org.jboss.tools.central.test.ui.bot/pom.xml{code}
> {code:title=contains refs to both 6.0 and 6.1}
> jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml{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
13 years
[JBoss JIRA] (JBIDE-13899) Update Server tests to support latest EAP 6.0.x and 6.1.0.x
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13899?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13899 at 4/2/13 11:20 AM:
-------------------------------------------------------------
While you're at it, I see some tests that refer to jboss-as 7.1.1, and some that refer to jboss-as 7.1.0. Should everything ref the latest?
JBoss AS 7.1.1: http://download.jboss.org/jbossas/7.1/jboss-as-7.1.1.Final/jboss-as-7.1.1...
{code}
jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml
{code}
was (Author: nickboldt):
While you're at it, I see some tests that refer to jboss-as 7.1.1, and some that refer to jboss-as 7.1.0. Should everything ref the latest?
{code}
jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml
{code}
> Update Server tests to support latest EAP 6.0.x and 6.1.0.x
> -----------------------------------------------------------
>
> Key: JBIDE-13899
> URL: https://issues.jboss.org/browse/JBIDE-13899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, JBossAS/Servers
> Affects Versions: 4.0.2.Final, 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
>
> Found test classes which refer to JBEAP 6.0 and/or 6.1. They should be updated to refer to the latest 6.0.x AND new 6.1.0.x bits, so both are available for testing.
> {code:title=contains ref to only 6.0. Should it contain 6.1 too?}
> jbosstools-integration-tests/tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml
> jbosstools-integration-tests/tests/org.jboss.tools.central.test.ui.bot/pom.xml{code}
> {code:title=contains refs to both 6.0 and 6.1}
> jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml{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
13 years
[JBoss JIRA] (JBIDE-13899) Update Server tests to support latest EAP 6.0.x and 6.1.0.x
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13899?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13899 at 4/2/13 11:21 AM:
-------------------------------------------------------------
While you're at it, I see that some tests still refer to jboss-as 7.1.0, while all the integration tests are already using 7.1.1. as.test.core ref the latest too?
{code}
jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml
{code}
JBoss AS 7.1.1: http://download.jboss.org/jbossas/7.1/jboss-as-7.1.1.Final/jboss-as-7.1.1...
was (Author: nickboldt):
While you're at it, I see some tests that refer to jboss-as 7.1.1, and some that refer to jboss-as 7.1.0. Should everything ref the latest?
JBoss AS 7.1.1: http://download.jboss.org/jbossas/7.1/jboss-as-7.1.1.Final/jboss-as-7.1.1...
{code}
jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml
{code}
> Update Server tests to support latest EAP 6.0.x and 6.1.0.x
> -----------------------------------------------------------
>
> Key: JBIDE-13899
> URL: https://issues.jboss.org/browse/JBIDE-13899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, JBossAS/Servers
> Affects Versions: 4.0.2.Final, 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
>
> Found test classes which refer to JBEAP 6.0 and/or 6.1. They should be updated to refer to the latest 6.0.x AND new 6.1.0.x bits, so both are available for testing.
> {code:title=contains ref to only 6.0. Should it contain 6.1 too?}
> jbosstools-integration-tests/tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml
> jbosstools-integration-tests/tests/org.jboss.tools.central.test.ui.bot/pom.xml{code}
> {code:title=contains refs to both 6.0 and 6.1}
> jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml{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
13 years