That sounds good to me. The only qualification I would have is that
the OS version be optional, such that if it's not included, the OS
family applies to all versions.
-Nathan
On 3/19/07, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
No, "hy.os" has semantics of OS family name and is used accordingly,
let's leave it as is.
You might want to introduce a *new* property for that, like
"hy.os.version" or "hy.os.flavor", and perform *additional* lookup for
x-list using that property. IIRC we already had different failures on
WinXP and Win2003 server, but our x-list machinery was not so advanced
at that time. So let's add such feature now ;)
2007/3/19, Alexei Zakharov <[EMAIL PROTECTED]>:
> Well, I see. But the current scheme for exclude lists' names is:
> exclude.${hy.os}.${hy.arch}.${hy.test.vm.name}
>
> So the last portion of the name is "hy.test.vm.name" - (originally)
> the name of JVM to be run. In fact, if we like to add special support
> for Windows 2000 we can encapsulate it in "hy.os" property. It is
> "windows" for all windows platforms currently. However, it seems
> Windows 2K can be detected through ant's condition:
> <os name="Windows 2000">
> since System.getProperty("os.name") returns "Windows 2000", at least
> on all modern version of RI :) [1]. This way, we may choose some value
> like "win2000" or "windows2k" and the resulted exclude list name will
> look like:
> exclude.windows2k.x86.ibm
>
> Thoughts?
>
> [1] http://tolstoy.com/samizdat/sysprops-windows.html
>
> Regards,
>
> 2007/3/17, Nathan Beyer <[EMAIL PROTECTED]>:
> > Note, the IBM VM works perfectly well on Windows 2000. It's just the
> > class library code that doesn't. I think it would be more appropriate
> > to be something like "exclude.x86.windows.2000"
> >
> > -Nathan
> >
> > On 3/16/07, Alexei Zakharov <[EMAIL PROTECTED]> wrote:
> > > > Is there a means of excluding tests for win 2000?
> > >
> > > Well, we may add it. For example choose some exotic vm name -
> > > "ibm2000", "ibm2" or like it. The corresponding exclude list will have
> > > name "exclude.windows.x86.ibm2000".
> > >
> > > Regards,
> > >
> > > 2007/3/15, Nathan Beyer <[EMAIL PROTECTED]>:
> > > > I think win 2000 is going to be a needed platform.
> > > >
> > > > Is there a means of excluding tests for win 2000? The build files are
> > > > little deceiving as they indicate working for all win32 sdks.
> > > >
> > > > -Nathan
> > > >
> > > >
> > > > On 3/15/07, Alexey Petrenko <[EMAIL PROTECTED]> wrote:
> > > > > 2007/3/15, Alexey Varlamov <[EMAIL PROTECTED]>:
> > > > > > It should be possible to made the dependency dynamic?
> > > > > As I said before I'm not sure for now.
> > > > > But yes, it is probably possible.
> > > > >
> > > > > And I do not think that this is very important task for now.
> > > > >
> > > > > SY, Alexey
> > > > >
> > > > > > Re Win2000 build in general - it might be of little interest right
> > > > > > now, yet apparently has its niche and could be worth to address in
> > > > > > some future (IMO).
> > > > > >
> > > > > > --
> > > > > > Alexey
> > > > > >
> > > > > > 2007/3/15, Alexey Petrenko <[EMAIL PROTECTED]>:
> > > > > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp
from awt
> > > > > module.
> > > > > > > I'm not sure can we remove this dependency or not.
> > > > > > >
> > > > > > > SY, Alexey
> > > > > > >
> > > > > > > 2007/3/15, Nathan Beyer <[EMAIL PROTECTED]>:
> > > > > > > > The current gl.dll that's part of the build with AWT has a
dependency
> > > > > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently
it's a
> > > > > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing
to load
> > > > > > > > because this dependency is missing.
> > > > > > > >
> > > > > > > > I'm not familiar with what's going on in the 'gl' library, but
is this
> > > > > > > > dependency a requirement? Do we just need a Windows 2000 build?
>
>
> --
> Alexei Zakharov,
> Intel ESSD
>
