On 5/5/16, 1:36 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: > >For multiple targets, I think it should be possible by using different pom >files for different targets. You could have a parent pom that calls these >two poms if you want to chain them together.
Sounds possible. I wonder why we haven't tried that yet. > >From an end user point of view, I don't need to have SDK downloaded, no >env. variables set, no dependencies to download, etc. All I have to do is >run "mvn install" from my project folder where I have my FlexJS project. >Maven will take care of everything else (downloading, compiling, copying, >etc.) It will also cache everything in the right places so that nothing >has >to be downloaded more than once. > >From an SDK developer/contributor point of view, I want to be able to run >maven and quickly compile the changes I make. This makes it easier for me >to contribute to the SDK development. > >This is the end goal of what Chris is trying. Ant does not come close to >this. Actually, other than Playerglobal and FlashPlayerDebugger, Ant already does this. And it could easily be made to do the other two but they are build tools and I wasn't sure our official build scripts can/should do that (needs licensing acceptance, makes us appear to have dependencies on non-AL-compatible things). I'm totally in favor of having Maven artifacts. I don't understand the "all-Maven-for-every-build-step or nothing" attitude. So what if we use Ant for some of it? -Alex
