If the user has the karma to deploy, the deployer can be used to deploy it, it works on command line whatever the repository manager.
-----Message d'origine----- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : jeudi 29 août 2013 19:32 À : dev@flex.apache.org Objet : Re: FlexUnit On Thu, Aug 29, 2013 at 8:04 AM, christofer.d...@c-ware.de < christofer.d...@c-ware.de> wrote: > That actually sounds like a really good idea from my side ... and I > really don't know, why nobody came up with that Suggestion yet ;-) > I remember discussing this a while ago. As long as there is a command line invocation available and no further prompts, we can easily integrate it as an option in the Installer. Deploying to Artifactory/Nexus might be a bit more involved. I have never used Nexus, but replicating all the functionality that the Artifactory UI offers might be a overkill for us. Once the artifacts are available manually adding it using their UI seems like a better option. Thanks, Om > > It would reduce the "Manual" part to the clicking of a Checkbox. In > that case I would also opt for a second Checkbox that is available as > soon as someone choose to mavenize in which a user can choose to > automatically deploy to an repository Manager (Artifactory, Nexus) > using the deployer tool from within the installer. > > Chris > > ________________________________________ > Von: Nick Collins [ndcoll...@gmail.com] > Gesendet: Donnerstag, 29. August 2013 16:16 > An: dev@flex.apache.org > Betreff: Re: FlexUnit > > Would a reasonable compromise be to add the "mavenizing" of the FDK > as an option to the installer? Where all I need do is check a box > saying "Use Apache Flex with Maven", and have the installer take care > of converting the FDK to the maven format and adding it to my local Maven repository. > > > On Thu, Aug 29, 2013 at 9:06 AM, Avi Kessner <akess...@gmail.com> wrote: > > > Oh, and thank you. mavenizing was very quick and easy , deploying > > on the other hand.. (atleast I don't have to do it manually) > > > > brought to you by the letters A, V, and I and the number 47 > > > > > > On Thu, Aug 29, 2013 at 5:06 PM, Avi Kessner <akess...@gmail.com> wrote: > > > So legally we can't store these sdks for maven publicly? I see 4.1 is > > > 112MB, yech. > > > brought to you by the letters A, V, and I > > > and the number 47 > > > > > > > > > On Thu, Aug 29, 2013 at 2:32 PM, christofer.d...@c-ware.de > > > <christofer.d...@c-ware.de> wrote: > > >> And I hate "lawyers" more than "manually" ;-) > > >> > > >> It's actually a Multi Minute process to Mavenize an FDK as I created > > the Apache Flex Mavenizer for that (It actually also mavenizes Adobe Flex > > FDKs) together with the Auto deployer you should have any Flex FDK > > mavenized and deployed in minutes. > > >> > > >> > > > https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Migrating+to+6.x?src= search > > >> > > >> Chris > > >> > > >> ________________________________________ > > >> Von: Avi Kessner [akess...@gmail.com] > > >> Gesendet: Donnerstag, 29. August 2013 12:33 > > >> An: dev@flex.apache.org > > >> Betreff: Re: FlexUnit > > >> > > >> Thanks. > > >> I hate that word.. "manually". > > >> Is there a more recent version or alternative to mockolate as well? > > >> And is this a multi day or multi hour process to mavenize the FDK? > > >> brought to you by the letters A, V, and I > > >> and the number 47 > > >> > > >> > > >> On Thu, Aug 29, 2013 at 1:11 PM, christofer.d...@c-ware.de > > >> <christofer.d...@c-ware.de> wrote: > > >>> Hi, > > >>> > > >>> Unit testing is a pretty tricky thing in Flexmojos. That's one of the > > things I am intending on performing the largest changes the the new > plugin. > > But from your question I can see you are using an about 100 year old > > Version of Flexmojos and Flex. I know I did quite a lot of tweaks and > > updates in the flexunit Support when we were working on releasing > flexunit > > 4.x. So I would like to ask you to update so a somewhat reasonably new > > Version of flexmojos ... 6.0.1 would be best ... but Keep in mind that > you > > Need to manually mavenize the FDK you want to use. > > >>> > > >>> Chris > > >>> > > >>> ________________________________________ > > >>> Von: Avi Kessner [akess...@gmail.com] > > >>> Gesendet: Donnerstag, 29. August 2013 09:52 > > >>> An: dev@flex.apache.org > > >>> Betreff: Re: FlexUnit > > >>> > > >>> I'm sorry to go off topic, but this is really starting to fustrate > me. > > >>> If anyone is able to help me out over at stackOverflow I really > > >>> appreciate it! > > >>> > > >>> > > > http://stackoverflow.com/questions/18505129/how-do-i-get-flexunit-flexmojos- and-mockolate-to-work-together > > >>> brought to you by the letters A, V, and I > > >>> and the number 47 > > >>> > > >>> > > >>> On Thu, Aug 29, 2013 at 6:11 AM, Cyrill Zadra < > cyrill.za...@gmail.com> > > wrote: > > >>>> Great! .. I pushed my changes always to "makeFlexUnitApacheReady". > > Shall I > > >>>> merge those changes also to develop branch and continue to work on > > this one? > > >>>> > > >>>> Cyrill > > >>>> > > >>>> > > >>>> On Thu, Aug 29, 2013 at 3:29 AM, Michael A. Labriola < > > >>>> labri...@digitalprimates.net> wrote: > > >>>> > > >>>>> > > >>>>> In the FlexUnit repo right now there is only a master. > > >>>>> > > >>>>> I am creating a develop branch presently and pushing some changes > we > > made > > >>>>> to the flexunit tasks to support a URL instead of just a local file > > when > > >>>>> executing tests. > > >>>>> > > >>>>> We should just make sure this gets integrated into master before > the > > next > > >>>>> release. > > >>>>> > > >>>>> Mike > > >>>>> > > >
