Just a thought, I guess it will have to deal with the native process to get the java environment variable and run the java command if you want the installer to be able to generate the mavenized FDK.
-----Original Message----- From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Sent: Friday, November 09, 2012 3:41 PM To: flex-dev@incubator.apache.org Subject: AW: [jira] [Commented] (FLEX-33246) Apache Flex Mavenizer needs a 'better' README Hi, as far as I understood the Installer, it automatically installs the Flex SDK and automatically downloads the missing binaries and copies them in the right position to create a fully functional FDK? So if you were to simply copy the FDK directory created to another directory "{sdkroot}/flex/flex-4.8.0.????" would it then work? I guess I should add an option to simply generate one FDK. The current version was initially intended for me generating Every available FDK and then to deploy that somehow. But I do see the use case in which someone would deploy a single FDK. I think I'll try the Installer and have a look at what that creates. Currently I have to admit that I was so full of work, that I simply used the FDK I built myself. Chris -----Ursprüngliche Nachricht----- Von: Markus Gritsch [mailto:markus_grit...@gmx.de] Gesendet: Freitag, 9. November 2012 14:07 An: flex-dev@incubator.apache.org Betreff: Re: [jira] [Commented] (FLEX-33246) Apache Flex Mavenizer needs a 'better' README Hi Chris, just let the installer run again - version 1.0.9 - the directory structure the installer produces is different from the one mavenizer requires. As your mentioned in your documentation the flex and air sdks have to be in the same directory. I think it will be possible when there are two different variables for "sdkSourceDirectoryName" - main function of SDKGenerator - which directs to flex- and air-sdk in a separate way. Markus On Nov 9, 2012, at 12:26 PM, christofer.d...@c-ware.de wrote: > Well If the installer doesn't produce any different structure, I guess it should work with an SDK generated by the installer without modification. > I just added a real README to the Issue ... if you could have a look > at that eventually it solves all of your problems. If not, please just give me Feedback on the problem and I'll get right on to it. > > Chris > > -----Ursprüngliche Nachricht----- > Von: Markus Gritsch [mailto:markus_grit...@gmx.de] > Gesendet: Freitag, 9. November 2012 11:31 > An: flex-dev@incubator.apache.org > Betreff: Re: [jira] [Commented] (FLEX-33246) Apache Flex Mavenizer > needs a 'better' README > > Hi Chris, > > Just tried the mavenizer - it would be nice when the installer could work with the apache flex sdk installer reusing already downloaded flex and air sdk - any thoughts? > > Markus > > On Nov 9, 2012, at 11:08 AM, Erik de Bruin (JIRA) wrote: > >> >> [ >> https://issues.apache.org/jira/browse/FLEX-33246?page=com.atlassian.j >> i >> ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134 >> 9 >> 3869#comment-13493869 ] >> >> Erik de Bruin commented on FLEX-33246: >> -------------------------------------- >> >> I think other users would appreciate the reminder as well... So maybe move the links to the README and add a little context? >> >>> Apache Flex Mavenizer needs a 'better' README >>> --------------------------------------------- >>> >>> Key: FLEX-33246 >>> URL: https://issues.apache.org/jira/browse/FLEX-33246 >>> Project: Apache Flex >>> Issue Type: Sub-task >>> Reporter: Erik de Bruin >>> Labels: flex, mavenizer >>> >>> Also, the README can use some work (more step by step, fill in the >>> blanks) and the download-sources.txt needs some kind of context >>> (don't know what it's for etc.) >> >> -- >> This message is automatically generated by JIRA. >> If you think it was sent incorrectly, please contact your JIRA >> administrators For more information on JIRA, see: >> http://www.atlassian.com/software/jira >
