If it opens a popup, it will mess up the mavenizer … at least in
non-interactive mode which CI servers require.
One more reason to implement it the way I am doing it … I know whenever I took
the easy path in the past it kept on coming back at me with support questions,
so I’ll prefer to do things right the first time. Anyway, I think the DMG
extraction code would be a perfect contribution to the Apache Commons project
(Planning on moving things there as soon as I’m finished) as there is currently
no “copy-left-less” library to do this available anywhere.
Chris
Am 05.05.17, 17:07 schrieb "Alex Harui" <aha...@adobe.com>:
On 5/5/17, 8:02 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi Alex,
>
>Well I guess I could probably do that, but I am no fan of this. The
>Mavenizer is platform independent and is generally able to provide the
>Mac SDK on a Windows machine. Also, there are major drawbacks when
>starting OS processes from within a Java VM. That’s why my implementation
>should be able to unpack the DMGs on any platform.
Up to you. I agree it isn't perfect. I'm just trying to save you time.
The odds a DMG will need to be unpacked on other platforms is close to
zero, IMO. IIRC, the utility we use in the installer pops up a status
window. Not sure if that will mess up the Mavenizer. If you have a Mac,
you can try running the installer to see.
-Alex
