israfil-mojo - Project Hosting on Google Code

Earlier this year Sep 24, 2009 issue 30 (Add namespace mappings from the flexlibproperties) commented on by ganugapati - Is there any other way to specify namespace menifest mapping? Is there any other way to specify namespace menifest mapping? Apr 07, 2009 issue 40 (Feature request: support compiling multiple SWF modules for ...) commented on by rrsav...@hotmail.com - No problem, I fully understand. No problem, I fully understand. Apr 07, 2009 issue 40 (Feature request: support compiling multiple SWF modules for ...) commented on by christianedwardgruber - Sorry rrsav. I've not been using flex projects myself for quite some time, and it's been very hard to make it a piriority. Sorry rrsav. I've not been using flex projects myself for quite some time, and it's been very hard to make it a piriority. Apr 06, 2009 issue 40 (Feature request: support compiling multiple SWF modules for ...) commented on by luc.will - Ooeps, wrong mailing group. i was using flex-mojo. didn't realise that this was a other flex module :-( Ooeps, wrong mailing group. i was using flex-mojo. didn't realise that this was a other flex module :-( Apr 06, 2009 issue 40 (Feature request: support compiling multiple SWF modules for ...) commented on by rrsav...@hotmail.com - I made my own custom version of the Israfil Mojo to handle multiple modules, but due to the lack of activity with this project, I abandoned it and migrated to http://flex-mojos.info/ I made my own custom version of the Israfil Mojo to handle multiple modules, but due to the lack of activity with this project, I abandoned it and migrated to http://flex-mojos.info/ Apr 06, 2009 issue 40 (Feature request: support compiling multiple SWF modules for ...) commented on by rob...@shadeblue.com - I made my own custom version of the Israfil Mojo to handle multiple modules, but due to the lack of activity with this project, I abandoned it and migrated to http://flex-mojos.info/ I made my own custom version of the Israfil Mojo to handle multiple modules, but due to the lack of activity with this project, I abandoned it and migrated to http://flex-mojos.info/ Apr 06, 2009 issue 40 (Feature request: support compiling multiple SWF modules for ...) commented on by luc.will - I'm also having the same kind of problem. I have to create a 20x swf files , each holding a font + a css file. currently i have converted a ant script which basicly has 20 lines of <mxmlc file="${basedir}/fonts/CarpenterICG.css" output="${BIN_DIR}/CarpenterICG.swf" /> currently this is replaced with 20 maven project , 20 pom.xml in a multi project build. this all is a bit overkilled and hard to maintain, let alone explain to my fellow workers . I tried using modules but a can't get it working. What i would like to see is something like <sourceFiles>font/.css</sourceFiles> <excludes> <some file you want to exclude for some reason > </excludes> I'm also having the same kind of problem. I have to create a 20x swf files , each holding a font + a css file. currently i have converted a ant script which basicly has 20 lines of <mxmlc file="${basedir}/fonts/CarpenterICG.css" output="${BIN_DIR}/CarpenterICG.swf" /> currently this is replaced with 20 maven project , 20 pom.xml in a multi project build. this all is a bit overkilled and hard to maintain, let alone explain to my fellow workers . I tried using modules but a can't get it working. What i would like to see is something like <sourceFiles>font/.css</sourceFiles> <excludes> <some file you want to exclude for some reason > </excludes> Older Dec 19, 2008 issue 41 (Feature request: add support for compiling runtime CSS files) reported by rrsav...@hotmail.com - Add the ability to include (compile) Flex runtime CSS files. Runtime CSS files are compiled with the mxmlc compiler into separate SWF files. I understand that the Maven artifact created should be a single SWF file that is the main application SWF, I am not suggesting that that behavior should change. I am using the "maven-assembly-plugin" to package up all my Flex artifacts (fonts/images/etc) into a ZIP file for deployment. I wish to include these compiled SWF runtime CSS files in this artifacts ZIP file. The runtime CSS file definition for each defined runtime CSS file to compile should include a source path/file and a destination path/file. Reference: http://livedocs.adobe.com/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.h tm?context=LiveDocs_Book_Parts&file=styles_069_26.html Thank You, Robert Add the ability to include (compile) Flex runtime CSS files. Runtime CSS files are compiled with the mxmlc compiler into separate SWF files. I understand that the Maven artifact created should be a single SWF file that is the main application SWF, I am not suggesting that that behavior should change. I am using the "maven-assembly-plugin" to package up all my Flex artifacts (fonts/images/etc) into a ZIP file for deployment. I wish to include these compiled SWF runtime CSS files in this artifacts ZIP file. The runtime CSS file definition for each defined runtime CSS file to compile should include a source path/file and a destination path/file. Reference: http://livedocs.adobe.com/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.h tm?context=LiveDocs_Book_Parts&file=styles_069_26.html Thank You, Robert Nov 25, 2008 issue 40 (Feature request: support compiling multiple SWF modules for ...) reported by rrsav...@hotmail.com - Another Flex maven plug-in (info.flex-mojos:flex-compiler-mojo) supports compiling multiple SWF modules that may exist in a single Flex project. I prefer using this Maven2 plugin for Flex maven integration and it would be nice if it supported compiling multiple SWF modules in the Flex project. I have to achieve this today using ANT scripts. I understand that the Maven artifact created should be a single SWF file that is the main application SWF, I am not suggesting that that behavior should change. I am using the "maven-assembly-plugin" to package up all my Flex artifacts (fonts/images/etc) into a ZIP file for deployment. I wish to include these compiled SWF modules in this artifacts ZIP file. The module definition for each defined SWF module to compile should include a source path/file and a destination path/file as well as if it should be compiled with optimization againsts the main application SWF. The "flex-compiler-mojo" implementation does not provide a means to specify the destination path/filename and it automatically renames the output filename which I dislike. API reference: http://docs.flex-mojos.info/flex-compiler-mojo/compile-swf- mojo.html#moduleFiles Thank You, Robert Another Flex maven plug-in (info.flex-mojos:flex-compiler-mojo) supports compiling multiple SWF modules that may exist in a single Flex project. I prefer using this Maven2 plugin for Flex maven integration and it would be nice if it supported compiling multiple SWF modules in the Flex project. I have to achieve this today using ANT scripts. I understand that the Maven artifact created should be a single SWF file that is the main application SWF, I am not suggesting that that behavior should change. I am using the "maven-assembly-plugin" to package up all my Flex artifacts (fonts/images/etc) into a ZIP file for deployment. I wish to include these compiled SWF modules in this artifacts ZIP file. The module definition for each defined SWF module to compile should include a source path/file and a destination path/file as well as if it should be compiled with optimization againsts the main application SWF. The "flex-compiler-mojo" implementation does not provide a means to specify the destination path/filename and it automatically renames the output filename which I dislike. API reference: http://docs.flex-mojos.info/flex-compiler-mojo/compile-swf- mojo.html#moduleFiles Thank You, Robert Nov 25, 2008 issue 39 (Feature request: "actionScriptPropertiesFile" property for "...) reported by rrsav...@hotmail.com - Feature request to support "actionScriptPropertiesFile" for compiling SWF using "flex2:compile-swf" goal. Similar to the "flexLibPropertiesFile" property exposed in the "flex2:compile-swc" goal it would be ideal to support this same concept for the "flex2:compile-swf" goal. FlexBuilder3 does create a ".actionScriptProperties" that contains all the library files, source paths, compiler options, and all the other necessary compiler configuration information for FlexBuidler to compile. This would greatly simplify the build configuration between Maven and FlexBuilder. Thanks You, Robert Feature request to support "actionScriptPropertiesFile" for compiling SWF using "flex2:compile-swf" goal. Similar to the "flexLibPropertiesFile" property exposed in the "flex2:compile-swc" goal it would be ideal to support this same concept for the "flex2:compile-swf" goal. FlexBuilder3 does create a ".actionScriptProperties" that contains all the library files, source paths, compiler options, and all the other necessary compiler configuration information for FlexBuidler to compile. This would greatly simplify the build configuration between Maven and FlexBuilder. Thanks You, Robert Aug 21, 2008 issue 37 (Cannot compile: Mac OSX 10.5.1 with jdk 1.6.0_05on x64 on Ma...) changed by christianedwardgruber - Status: Accepted Labels: Priority-High Severity-Blocker OpSys-OSX Affects-Release-All Milestone-Release-1.4 Project-mojo-flex Quality −Priority-Medium Status: Accepted Labels: Priority-High Severity-Blocker OpSys-OSX Affects-Release-All Milestone-Release-1.4 Project-mojo-flex Quality −Priority-Medium Aug 21, 2008 issue 38 (Support += operator for extraParameters) changed by christianedwardgruber - Status: Accepted Labels: Type-Enhancement Affects-Release-1.3 Milestone-Release-1.4 Usability Complexity-Low Severity-Medium OpSys-All Project-mojo-flex −Type-Defect Status: Accepted Labels: Type-Enhancement Affects-Release-1.3 Milestone-Release-1.4 Usability Complexity-Low Severity-Medium OpSys-All Project-mojo-flex −Type-Defect Aug 21, 2008 issue 38 (Support += operator for extraParameters) reported by keesvandieren - It would be nice if the += operator is supported extra parameters. See the compiler options on: http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_14.html Suggestion on how to implement: If the parameter <name> starts with +=, do not add the '-' prefix in the parameters list (as this is currently done in AbstractFlexMojo.java finalizeParameters method). It would be nice if the += operator is supported extra parameters. See the compiler options on: http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_14.html Suggestion on how to implement: If the parameter <name> starts with +=, do not add the '-' prefix in the parameters list (as this is currently done in AbstractFlexMojo.java finalizeParameters method). Aug 04, 2008 issue 36 (NullPointerException when executing the flex2.tools.Compiler) commented on by tomas.darbois - We've got the same problem, with a path that contains an old jdk (before the correct one) different from the one declared in the System parameters $JAVA_HOME. It was causing this failure due to the fact that this jdk contains a library outdated. The catch code in net.israfil.mojo.flex2.StreamedParameterExecutableWrapper.main contains line 64 a system.out.println that read an array that is not initialized if there is an error line 57 of the same java class which is the case when you have a library that redefined the java.util.String with an old one which is causing the java file net.israfil.mojo.flex2.StringStreamUtil to raise an exception NotSuchMethod in line 85 when trying to do "line.contains(....);" which is not defined in java 1.3. A solution to have a better output from the plugin is to edit the java file net.israfil.mojo.flex2.StreamedParameterExecutableWrapper and change the line 64 by adding a try catch for example in order to avoid throwing an other exception in case of a not initialized array :) We've got the same problem, with a path that contains an old jdk (before the correct one) different from the one declared in the System parameters $JAVA_HOME. It was causing this failure due to the fact that this jdk contains a library outdated. The catch code in net.israfil.mojo.flex2.StreamedParameterExecutableWrapper.main contains line 64 a system.out.println that read an array that is not initialized if there is an error line 57 of the same java class which is the case when you have a library that redefined the java.util.String with an old one which is causing the java file net.israfil.mojo.flex2.StringStreamUtil to raise an exception NotSuchMethod in line 85 when trying to do "line.contains(....);" which is not defined in java 1.3. A solution to have a better output from the plugin is to edit the java file net.israfil.mojo.flex2.StreamedParameterExecutableWrapper and change the line 64 by adding a try catch for example in order to avoid throwing an other exception in case of a not initialized array :)

issue 40 (Feature request: support compiling multiple SWF modules for ...) reported by rrsav...@hotmail.com - Another Flex maven plug-in (info.flex-mojos:flex-compiler-mojo) supports compiling multiple SWF modules that may exist in a single Flex project. I prefer using this Maven2 plugin for Flex maven integration and it would be nice if it supported compiling multiple SWF modules in the Flex project. I have to achieve this today using ANT scripts. I understand that the Maven artifact created should be a single SWF file that is the main application SWF, I am not suggesting that that behavior should change. I am using the "maven-assembly-plugin" to package up all my Flex artifacts (fonts/images/etc) into a ZIP file for deployment. I wish to include these compiled SWF modules in this artifacts ZIP file. The module definition for each defined SWF module to compile should include a source path/file and a destination path/file as well as if it should be compiled with optimization againsts the main application SWF. The "flex-compiler-mojo" implementation does not provide a means to specify the destination path/filename and it automatically renames the output filename which I dislike. API reference: http://docs.flex-mojos.info/flex-compiler-mojo/compile-swf- mojo.html#moduleFiles Thank You, Robert

Another Flex maven plug-in (info.flex-mojos:flex-compiler-mojo) supports compiling multiple SWF modules that may exist in a single Flex project. I prefer using this Maven2 plugin for Flex maven integration and it would be nice if it supported compiling multiple SWF modules in the Flex project. I have to achieve this today using ANT scripts. I understand that the Maven artifact created should be a single SWF file that is the main application SWF, I am not suggesting that that behavior should change. I am using the "maven-assembly-plugin" to package up all my Flex artifacts (fonts/images/etc) into a ZIP file for deployment. I wish to include these compiled SWF modules in this artifacts ZIP file. The module definition for each defined SWF module to compile should include a source path/file and a destination path/file as well as if it should be compiled with optimization againsts the main application SWF. The "flex-compiler-mojo" implementation does not provide a means to specify the destination path/filename and it automatically renames the output filename which I dislike. API reference: http://docs.flex-mojos.info/flex-compiler-mojo/compile-swf- mojo.html#moduleFiles Thank You, Robert

Earlier this year

Older