[jbosstools-dev] Re: Freezing in the build unit tests
Sergey Vasilyev
svasilyev at exadel.com
Fri Oct 19 03:46:50 EDT 2007
Denis Golovin wrote:
> It looks like you should override plugin_customization.ini file in
> eclipse that is used for JUnit testing with another one file that
> contains
>
> # To enable Use External Browser preference
> org.eclipse.ui.browser/browser-choice = 1
>
> I found eclipse has two files in plugins/org.eclipse.platform_3.3.1
> and plugins/org.eclipse.sdk_3.3.1.r331.
>
> I'm not sure if the used during running JUnit tests, but only you can
> try it because my local build is always failed with error below
>
>
> BUILD FAILED
> c:\exadel-projects\rhds\plugins\releng\org.jboss.ide.eclipse.releng\builders\build.xml:64:
> The following error occurred while executing this line:
> c:\exadel-projects\rhds\plugins\releng\org.jboss.ide.eclipse.releng\builders\build.xml:27:
> The following error occurred while executing this line:
> c:\exadel-projects\rhds\plugins\releng\org.jboss.ide.eclipse.releng\builders\build.xml:45:
> The following error occurred while executing this line:
> c:\exadel-projects\rhds\plugins\releng\org.jboss.ide.eclipse.releng\builders\product\productBuild.xml:69:
> The following error occurred while executing this line:
> c:\exadel-projects\rhds\plugins\releng\org.jboss.ide.eclipse.releng\builders\product\productBuild.xml:251:
> The following error occurred while executing this line:
> c:\exadel-projects\rhds\plugins\releng\org.jboss.ide.eclipse.releng\builders\product\productBuild.xml:253:
> The following error occurred while executing this line:
> c:\exadel-projects\rhds\plugins\releng\org.jboss.ide.eclipse.releng\builders\product\productBuild.xml:228:
> C:\build\rhds\eclipse\N-build not found.
>
>
> Thanks
> Denis
>
> Marshall Culpepper wrote:
>> Is this something I can do automatically for build? you'll have to
>> remind me..
>>
>> Denis Golovin wrote:
>>> Can you try switch to external browser as we did before for RHDS?
>>>
>>> Marshall Culpepper wrote:
>>>> Looks like this error may have just been a fluke locally. The real
>>>> error is the "Can't find internal browser" .. error. Is there
>>>> anyway we can turn that off so it doesn't freeze the build??
>>>>
>>>> Marshall Culpepper wrote:
>>>>> Hey guys..
>>>>>
>>>>> The freezing in the build's unit tests is reproducing every build
>>>>> now. The culprit seems to be the "JSP Semantics Validator (JSF)".
>>>>> Right now my workspace is showing it being stuck @ 1% on
>>>>> WebContent/pages/inputname.jsp. I've pasted the relevant part of
>>>>> the console log here:
>>>>>
>>>>> http://pastebin.ca/741394
>>>>>
>>>>> Looks like this might be related org.jboss.tools.common.model?
>>>>> Denis any ideas?
>>>>>
>>>>
>>>>
>>>
>>
>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
Eclipse uses the code is situated below to recognize is there internal
browser or not.
// WebBrowserUtil.canUseInternalWebBrowser()
// try loading it
Shell shell = null;
try {
shell = new Shell(PlatformUI.getWorkbench().getDisplay());
new Browser(shell, SWT.NONE);
isInternalBrowserOperational = new Boolean(true);
return true;
} catch (Throwable t) {
WebBrowserUIPlugin.getInstance().getLog().log(
new Status(IStatus.WARNING,
WebBrowserUIPlugin.PLUGIN_ID,
0, "Internal browser is not available: " +
t.getMessage(), null)); //$NON-NLS-1$
isInternalBrowserOperational = new Boolean(false);
return false;
} finally {
if (shell != null)
shell.dispose();
}
Setting in preferences (and as I think in plugin_customization.ini)
External Browser as Default Browser doesn't help.
Sergey
More information about the jbosstools-dev
mailing list