Hi Velo, What do you think about supplying custom template via classpath instead from file path? This issue arises when I try to create a super reusable pom for all my flex projects that requires generator in the build process. With the current scheme, this would requires to use maven-dependency-plugin unpack feature to supply custom template as file path.
The required changes will be very localized at GranitedsGenerator#getStringByIndex( ... ) In that method, I would need to test whether the given String has a prefix class:, if it does, use it as is, otherwise, assume that it's a file path. Wdyt? If you're ok by this, I'll create the jira issue and attach the patch. Regards, Edward Yakop --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
