Velo, I have been following the thread(s) regarding inclusion of the dita-asdoc goal by default.
http://osdir.com/ml/flex-mojos/2010-11/msg00023.html I didn't respond earlier to your request as to whether it should be included as I wasn't sure. I now think that it should not be included in the default lifecycle for flexmojos because: 1) It makes it awkward to configure the real asdoc generation using a custom asdoc template. 2) There are occasional errors concerning a duplicate ASDoc_Config.xml (or maybe ASDoc_Base.xml - I forget) when the dita-asdoc goal runs. This can be fixed by running a "clean install" but it's still annoying. Let me expand on point 1 a little. I configured a <templatePath> globally for a multi-module project, and then bound the actionscript documentation generation to a profile which was triggered from a system property (-Dasdoc). The problem was that when I invoked a "mvn install" the dita-asdoc goal would fail as the template was not available (the custom template dependency is only unpacked when the 'asdoc' profile is triggered). I could work around this by changing the <templatePath> declaration to a child module, but this feels clunky. My main goal was to get asdoc generation working correctly outside of the normal "install" lifecycle as the asdoc tool is ridiculously slow (are you listening Adobe?). Therefore I strongly believe that the dita-asdoc goal should *NOT* be included by default. For the record I have also fixed the dita asdoc conversion problem I mentioned in the earlier thread: http://markmail.org/message/v4xwtu4dejka33hh As it turns out the temporary dita xml generated when the asdoc tool is run directly does *NOT* encode the markup declared in the asdoc tags. But when asdoc is run via Flexmojos the asdoc markup tags are escaped as HTML entities. It would take a long time to work out what is causing this discrepancy (I'm guessing it's a jar dependency version issue between Flexmojos and a vanilla Flex SDK install), so I decided to fix it at the XSLT level. Hence the need for a custom asdoc template. I would really appreciate it if you can disable this goal in the default lifecycle. If for some reason you disagree and want it executed by default can you let me know how to disable it for my project please. A combination of this setup and some extra magic has allowed me finally (I've been working on this for some time) to get to where I want to be with asdoc generation integrated with Flexmojos. I will send a separate message about this if other people are interested in using this configuration. -- mischa (aka muji). -- 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/
