Ok, I will get that on FME. Just need to finish AIR3 support.... On Nov 21, 3:26 pm, Simon Morvan <[email protected]> wrote: > Well... why not adding that to FME... BTW, we're still waiting for your > pricing plan to get a definitive license/version to use in production. > > FWIW, here's a workaround in the meantime : > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>exec-maven-plugin</artifactId> > <version>1.2.1</version> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>exec</goal> > </goals> > <configuration> > <executable>java</executable> > <workingDirectory>${basedir}/target</workingDirectory> > <classpathScope>compile</classpathScope> > > <arguments> > <argument>-classpath</argument> > <classpath/> > <argument>com.adobe.air.ADT</argument> > <argument>-migrate</argument> > <argument>-storetype</argument> > <argument>pkcs12</argument> > <argument>-storepass</argument> > <argument>${air.cert.pass}</argument> > <argument>-keystore</argument> > <argument>${project.basedir}/src/main/resources/sign-old.p12</argument> > <argument>${project.basedir}/target/${project.build.finalName}.air</argument> > <argument>${project.basedir}/target/${project.build.finalName}-migrate.air</argument> > </arguments> > > </configuration> > > </execution> > </executions> > > </plugin> > > And add this dependency to your project : > > <dependency> > <groupId>com.adobe.flex.compiler</groupId> > <artifactId>adt</artifactId> > <version>${flex.sdk.version}</version> > <scope>compile</scope> > </dependency> > > Finally, if you want to have the final .air being the migrated one, add > this couple of renames > > <plugin> > <artifactId>maven-antrun-plugin</artifactId> > <executions> > <execution> > <goals> > <goal>run</goal> > </goals> > <phase>package</phase> > <configuration> > <tasks> > <move file="${project.build.directory}/${project.build.finalName}.air" > > tofile="${project.build.directory}/${project.build.finalName}-original.air" > overwrite="true"></move> > <move > file="${project.build.directory}/${project.build.finalName}-migrate.air" > > tofile="${project.build.directory}/${project.build.finalName}.air" > overwrite="true"></move> > </tasks> > </configuration> > </execution> > </executions> > </plugin> > > Hope this helps. > > -- > Simon > > Le 15/11/2011 12:21, Marvin Froeder a écrit : > > > > > > > > > I can include this to FME if you wanna. > > > VELO > > > On Nov 15, 8:34 am, Simon Morvan<[email protected]> wrote: > >> Actually if I do this only once, I'm forced to ensure an upgrade path > >> that use that specific version. > >> I would prefer "double signing" all my .air during the 180-day grace > >> period ensuring a smoother upgrade expericence for our users. > > >> Do you plan to integrate this or should I prepare a scripting magic voodoo > >> ? > > >> Le 09/11/2011 13:08, velo a écrit : > > >>> Isn't that something you could do just once and live with the new > >>> signature? Or is there any reason you would need to do that over and > >>> over again every time you build your project? > >>> Keep in mind that will slow down your build by a few seconds. > >>> VELO > >>> On Nov 8, 3:43 pm, Simon Morvan<[email protected]> wrote: > >>>> Hello there's, > >>>> How can I add the "migration signature" of my old certificate when > >>>> publishing with sign-air ? > >>>> i.e. : automating the adt -migrate into the build process. > >>>> -- > >>>> Simon
-- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
