OK. I'm reading once again the discussion, and the problem I'm facing now must be what you explained more precisely in your first answer (http:// groups.google.com/group/flex-mojos/msg/d953a961c7e748c6)
"Well, the library.SWF (from the 3rd party SWC) has a given checksum. Then you optimize that SWF, which will have a new checksum. In order to get this RSL usable, you need to update this checksum inside the original SWC, that will break maven md5, sha1 and signatures. This is really really bad. To deal with the problem correctly, whoever is publishing the SWC must publish the optimized SWF as well. This is specially trickier when some as3 metadata must be preserved, so it is the role of the person that produces the SWC to produce the optimized SWF as well." In fact, what I was trying to do is exactly what is in one of the next messages : "You only need to generate the rsl for a 3rd party library, right? why don't you simply use adobe tooling to do so? Only needs to do it once and store it into some repository manager (AKA nexus.sonatype.org)" (http://groups.google.com/group/flex-mojos/msg/d953a961c7e748c6) So, is this "manual" optimization possible? If I'm right, SWC digests have to be updated (and that is really really bad :-), but does adobe optimizer is doing this? @Roberto: I've just given a try to install-rsl goal. So here is what I've done and what I've got : delete org.spicefactory in my local maven repository run "mvn flexmojos:install-rsl -DartifactId=parsley-flex3 - DgroupId=org.spicefactory -Dversion=2.3.1" on my common-project pom. run "mvn clean install" on my common library project run "mvn clean install" on my main project collect swf and rsl from my release module (using copy-flex-resources goal with module artifact and version stripping enabled) When I'm running the main swf, I'm getting : "VerifyError: Error #1014: class org.spicefactory.parsley.tag.core::MxmlObjectsTag could not be found." So I have no error due to rsl digests anymore, but the RSL seems to be missing some classes. Maybe I should explain my project structure : - A common lib which using Parsley with RSL scope - A main project which using Parsley and common lib with RSL scope If I delete scope of Parsley (=>compile) in both common lib and main project, my app is working, and both common lib and main project are a bit bigger. I have a doubt on : - which pom i have to run install-rsl goal against. I'm not sure if it matters - stripping module artifact and version from rsl. As the rsl filename is then not default one for FM, I have to set rslUrl in my parent pom. I don't if this could interfer with install-rsl - I think no, I guess rsl path is given to module using the rsl, not the rsl itself. -- 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/
