On 11/29/12 11:48 AM, "christofer.d...@c-ware.de"
<christofer.d...@c-ware.de> wrote:
> Hi Alex,
>
> a local maven repo is on the machine the build is running ... that's one repo
> per machine. Think of it as a Maven-Cache. So if I run the build on my
> machine, the artifacts are available on that machine, but not on any other
> one.
Ah ok. I get it now.
>
> My idea was that if the build is set to "non-interactive" and the mojo detects
> missing runtime artifacts from Adobe, that it would output the license
> agreement and at the bottom output a message, that if the user accepts this
> agreement he has to run the build again and provide a system-property
> "-DIAcceptTheAdobeLicense=34854395704857204572098457024870" (The number is
> generated every time the mojo is run and no IAcceptTheAdobeLicense property is
> prvided). The generated token is saved in a place the plugin can find it again
> the next time it runs (temp-dir). If the token is provided in the next run,
> the mojo will download the stuff and deploy it on the local machine only.
>
> Ok so this is not 100% fool-proof but at least as fool-proof as creating an
> automated http-downloader that checks the "i agree" checkbox on the Adobe
> download.
I will try to get this approved.
One more question about the AIR SDK zip: Why do you need pom.xml files in
the subfolders of the AIR SDK to run the tools in there?
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
