Compared to my own license deploy script for data-vis... - Uses -DgeneratePom=true instead of citing a specific manual pom file
- The manually deployed license artifact is included as a dependency to flexmojos plugin in project pom file (not sure if you're doing this or not, just guessing), otherwise flexmojos would have to assume what its looking for (apparently license:jar:3.0.0.477 in this case). - Here we're using 'com.adobe.flex.compiler' as the groupId like the debug output, compared to your 'com.adobe.flex.license', although I'm not sure if that's important or not when the dependency is dropped directly into the plugin Hopefully something above helps. --David On Mon, Aug 24, 2009 at 2:53 PM, Anjan <[email protected]> wrote: > > I am going through the FlexMojos FAQ to get rid of automation trial > limit. > One of the instructions says- > Now, you need to install manually license.jar on maven repo. > > I did a maven deploy with the following details to the maven repo - > Dfile=license-3.3.0.4852.jar > Dversion=3.3.0.4852 > DartifactId=license > DgroupId=com.adobe.flex.license > Dpackaging=jar > DpomFile="license-3.3.0.4852.pom" > > And I see the following, when I run mvn install -X > > 1. -licenses.license flexbuilder3 nnnnnnnnnnnnnnnnnnnnnnnn > 2. [DEBUG] com.adobe.flex.compiler:license:jar:3.0.0.477:compile > (selected for compile). > > But the automation limit trial still appears. Can someone help me on > this? > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
