Yes, you are right but some can be skiped, I'm thinking about the 1rst param as we know where the mavenized SDK is already and we maybe able to detect if maven is installed, in this case, skip the last param.
I'm not fan of mavenizing the SDK directly in the maven repo, the user might haven't Maven installed, even though, if the mavenized SDK is deployed directly in the local repo, the deployement from this location is not secure, the user might have some other stuffs there he doesn't want to deploy, it is preferable to let him choose None, Local and Remote, in case of remote, the FDK will automatically be back in its local repo the first time it uses it. So, I agree with the Om steps and at step 3, it would be better to prompt the user for the target-directory it would become: 1. User accepts all the licenses in the Installer. 2. Installation completes and SDK (FDK in your terminology) is ready to be used with an IDE. 3. We show the user an option to Mavenize the SDK (including prompting for the target-directory). 4. If the user accepts, then we invoke the Mavenizer command-line script. 5. We show another prompt asking if the user wants to deploy it to the None, Local (and Remote if Maven is detected) options. If Remote is selected, detect and propose a list of server Ids(to map on the <id> under <server> section of settings.xml, if none of this attributes are detected, disable the Remote option) as long with the repository URL. 6. If the user accepts and select Remote, then we invoke the Deployer command-line script, If he selects Local, that's a simple move operation to the local repo. -Fred -----Message d'origine----- De : Avi Kessner [mailto:akess...@gmail.com] Envoyé : vendredi 30 août 2013 12:03 À : dev@flex.apache.org Objet : Re: AW: AW: AW: FlexUnit I was thinking about the deploy script actually, sorry I wasn't clear On 30 Aug 2013 12:44, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de> wrote: > Well the arguments should be source-directory and target Directory. > I made the target-directory a Parameter because I didn't want the > mavenizer to mess with my local repo while developing it. But it > should be a valid Approach to use the FDK Directory as source and have > a look at the mavens ~userhome\.m2\settings.xml for the local repo > path and if that's not available to use the Default of ~userhome\.m2\repository. > > Chris > > ________________________________________ > Von: Avi Kessner [akess...@gmail.com] > Gesendet: Freitag, 30. August 2013 11:31 > An: dev@flex.apache.org > Betreff: Re: AW: AW: FlexUnit > > Just incase it isn't clear, the command line tool requires some user > specific arguments, so the installer needs to handle that as well On > 30 Aug 2013 10:28, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > On Aug 29, 2013 11:44 PM, "christofer.d...@c-ware.de" < > christofer.d...@c-ware.de> wrote: > > > > Well the poms themselves don't help with the libs. I will probably > > be > adding functionality to download Adobe stuff after asking for > confirmation by the user as we discussed some months ago as soon as I > am picking up on the new maven plugin. Guess it would be possible to > have binary Apache Flex Releases in public repos. But for now I really > like the idea of integrating the Mavenizer and Deployer into the > Installer (You Need that anyway in order to get a new FDK) > > > > Chris > > > > I am up for it. Although I need to admit that most of what you just > said is beyond my understanding. Let me propose a route. Tell me if > I am in the right track. > > 1. User accepts all the licenses in the Installer. > 2. Installation completes and SDK (FDK in your terminology) is ready > to be used with an IDE. > 3. We show the user an option to Mavenize the SDK. > 4. If the user accepts, then we invoke the Mavenizer command-line script. > 5. We show another prompt asking if the user wants to deploy it. > 6. If the user accepts, then we invoke the Deployer command-line script. > > Is this acceptable/doable? This is doable from the Installer point if > view. > > Thanks, > Om > > > ________________________________________ > > Von: Alex Harui [aha...@adobe.com] > > Gesendet: Donnerstag, 29. August 2013 23:27 > > An: dev@flex.apache.org > > Betreff: Re: AW: FlexUnit > > > > On 8/29/13 8:08 AM, "christofer.d...@c-ware.de" > > <christofer.d...@c-ware.de> wrote: > > > > >Well the Problem are the Adobe libs ... playerglobal and some > > >others, that we are not allowed to publish. There wouldn't be any > > >trouble with deploying the rest of the FDK to public repos beyond > > >that, I guess. But unfortunately these FDKs would be completeley > > >useless without the > missing > > >Adobe libs :-( > > > > Yeah, but I thought we were going to try to put POMs on the Adobe > download > > server? What happened to that plan? > > > > -Alex
