[eclipse-poky] Eclipse plugin development on timo/maven

[Tim Orling]

> On Jan 24, 2018, at 6:56 PM, Paul Eggleton <paul.eggleton at linux.intel.com> wrote:
> 
>>>> One thing I realized, however, is that this launch config won't work on
>>>> windows.   This is not an immediate concern, but we will need to deal with
>>>> it.   In fact, the target definitions that we have also won't work on
>>>> windows.    One question for discussion:  do we want to have separate target
>>>> definition files for OS/archs...e.g. linux/x86_64, win32/x86_64?    Along
>>>> those lines...do we need/want to support all of mac, linux, win X 
>>>> x86_32, x86_64?
>>> 
>>> I would say let's start small - Linux and Windows 64-bit and then go from there. At minimum we should have a bug open for Windows support if we don't already.
>> 
>> [Tim] I believe we will run into issues with the Docs not being buildable on Windows, although it is possible MSYS2 (or MINGW) can satisfy the build dependencies (as mentioned in prior email about building the docs). Currently, those dependencies are HOST tools and not built as -native tools by YP.
> 
> Could we just disable doc generation on Windows as a start? Presumably we could even cheat and build the docs on Linux and then bring the resulting built docs in when we build the Windows version - a bit hacky but it would help if getting the doc tools working on Windows is too painful.
> 

There are multiple ways to disable the building, but we can make it “os” specific in the pom.xml and it will be skipped for Windows until we can investigate the MYSYS2/MINGW options. I am reluctant to change anything about how Scott Rifenbark builds the docs, so disabling is the best option (other than providing the Linux built resources for Windows to grab).