Hi Marvin, I _thought_ I had tried to put the dependencies into the parent pom - but accidentally I had put them into the <dependencyManagement> block, damn. Now I moved them into the parent pom flex mojos plugin section, and IT WORKS. But shouldn't it work in the module as well?
Thanks for pointing me to it, man. Peter On 26 Jun., 15:23, Marvin Froeder <[email protected]> wrote: > Hrmmmm... > Good approach. Where did you declare the extra dependencies to flexmojos? > On the module or on parent module? > > VELO > > On Fri, Jun 26, 2009 at 10:21 AM, peja <[email protected]> wrote: > > Thanks for your help, folks. > > > I did some more testing, here is what I did/found: > > > Compiling from within the module: > > ========================== > > 1.) when font path and fontkit dependency are correct - no problem > > > 2.) when I rename the font path (from "fonts" to "fontsXXX" to provoke > > a path error), I get: > > [ERROR] <project>/BaseTheme/src/main/flex/styles.css:[2343,-1] unable > > to resolve 'fonts/verdanai.ttf' for transcoding > > Seems logical because AFEFontManager cannot find the fonts. > > > 3.) when I remove the flex-fontkit.jar dependency from the pom (to > > provoke a classpath error), I get: > > [ERROR] <project>/BaseTheme/src/main/flex/styles.css:[2343,-1] > > exception during transcoding: No FontManager provided. Cannot build > > font. > > Seems logical because AFEFontManager is not in the classpath. > > > Compiling from the parent module: > > ========================== > > [ERROR] <project>/BaseTheme/src/main/flex/styles.css:[2343,-1] > > exception during transcoding: No FontManager provided. Cannot build > > font. > > > Since this is the same error message as compiling from within the > > module with a missing dependency, I am coming to the conclusion that > > this is a classpath problem. Do you agree? > > Can this be fixed, i.e. help Maven to find the classpath? > > > Thanks, > > Peter > > > On 26 Jun., 14:12, Marvin Froeder <[email protected]> wrote: > > > No, another SDK is not necessary, just declaring the extra depenendecies > > (as > > > was done) is enough... > > > This is not a classloading issue, the class was loaded and work, > > > but AFEFontManager probably has some but on the font path resolution. > > > > Debugging should help to figure out that. > > > > VELO > > > > On Fri, Jun 26, 2009 at 9:06 AM, James Cook <[email protected]> > > wrote: > > > > > Perhaps this is related? > > > > >http://www.mail-archive.com/[email protected]/msg118108.html > > > > > Perhaps for the purposes of hosting the Flex SDK, Marvin may be using > > > > the "MPL" version of the SDK. Because of Flex's classloading > > > > mechanisms, you may have to push into your own repository a non-MPL > > > > version of the Flex SDK to get access to the AFEFontManager. > > > > > -- jim > > > > > On Sun, Jun 21, 2009 at 5:08 AM, peja<[email protected]> wrote: > > > > > > I would like to use the Adobe flex-fontkit to compile/embed a font > > > > > with Flex Mojos 3.2, because using the BatikFontManager or the > > > > > JREFontManager results in washed out rendering. > > > > > > I am aware of the fact that the flex-fontkit is not part of the open > > > > > source SDK, so I installed the artifact on my local repository and > > > > > configured the flex mojos like this: > > > > > ... > > > > > <fonts> > > > > > <managers> > > > > > <!--manager-class>flash.fonts.BatikFontManager</manager-class--> > > > > > <manager-class>flash.fonts.AFEFontManager</manager-class> > > > > > </managers> > > > > > </fonts> > > > > > ... > > > > > <dependency> > > > > > <groupId>com.adobe.flex.compiler</groupId> > > > > > <artifactId>flex-fontkit</artifactId> > > > > > <version>${flex.sdk.version}</version> > > > > > <type>jar</type> > > > > > </dependency> > > > > > > It does work with the BatikFontManager configuration. When I use the > > > > > AFEFontManager, the flex-fontkit.jar is downloaded at build time, but > > > > > I get an error message: > > > > > [ERROR] /Volumes/SVA/contentlandscape-mvn/trunk/App/src/main/flex/ > > > > > App.mxml:[35,-1] exception during transcoding: No FontManager > > > > > provided. Cannot build font. > > > > > [ERROR] /Volumes/SVA/contentlandscape-mvn/trunk/App/src/main/flex/ > > > > > App.mxml:[35,-1] unable to build font 'akzidenz' > > > > > [ERROR] /Volumes/SVA/contentlandscape-mvn/trunk/App/src/main/flex/ > > > > > App.mxml:[35,-1] Unable to transcode ../../../../Theme/src/main/flex/ > > > > > fonts/AkzidenzGroteskBold.ttf. > > > > > [ERROR] /Volumes/SVA/contentlandscape-mvn/trunk/App/src/main/flex/ > > > > > App.mxml:[31,-1] exception during transcoding: No FontManager > > > > > provided. Cannot build font. > > > > > [ERROR] /Volumes/SVA/contentlandscape-mvn/trunk/App/src/main/flex/ > > > > > App.mxml:[31,-1] unable to build font 'akzidenz' > > > > > [ERROR] /Volumes/SVA/contentlandscape-mvn/trunk/App/src/main/flex/ > > > > > App.mxml:[31,-1] Unable to transcode ../../../../Theme/src/main/flex/ > > > > > fonts/AkzidenzGroteskRoman.ttf. > > > > > > Isn't the fontkit.jar added to the Classpath? What did I overlook? > > > > > > Thanks and Regards, > > > > > Peter --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
