Remi P <[email protected]> wrote: >@velo: not yet... but I will try if I have no other workaround > >@chris: yes of course swz files are part of the official adobe sdk, but >what I said is that these swz artefacts are not deployed on the >sonatype >repository. > >regards > >Remi > > >On Wed, Sep 19, 2012 at 3:55 PM, Christofer Dutz ><[email protected]>wrote: > >> Why do you claim, that 4.6.0.23201B doesn't contain any SWZs? If I >> have a look at the FDK they are all there. >> We will be having serious trouble with the Apache FDKs as these will >> no longer contain SWZ files but all official Apache FDKs should >> contain them. >> >> Chris >> >> >> >> 2012/9/19 Marvin Froeder <[email protected]>: >> > Did you tried installind it manually? >> > >> > On Sep 19, 10:47 am, Remi P <[email protected]> wrote: >> >> Hi Chris, >> >> >> >> Sorry to reply to this old post, but I'm facing a similar issue >with >> signed >> >> RSLs. >> >> >> >> It seems that copy-flex-resources works fine when swz artefacts >are >> >> deployed in the repository but many versions don't contain the swz >> >> artefacts. For example version 4.6.b.23201 (the last stable >version form >> >> Adobe) doesn't include swz artefacts. Did you have any workaround >which >> >> could allow us to provide our own swz artefacts to FM? Or much >better: >> do >> >> you have write permissions to deploy artefacts in the flex >sonatype repo >> >> (but I don't know if it's an heavy task)? >> >> >> >> Regards >> >> >> >> Rémi >> >> >> >> On Wed, Apr 11, 2012 at 3:27 PM, Christofer Dutz < >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> [email protected]> wrote: >> >> > Hi, >> >> >> >> > In our case we never actually added an adobe rsl url. Even if we >were >> >> > using signed rsls. The copy-flex-resources nicely copies the swz >files >> >> > to the location I provided in the rslUrl. The Flashplayer has no >> >> > problem with loading them from my server as it trusts them >because of >> >> > their signature. >> >> >> >> > You could say that loading them from Adobe could reduce traffic >on >> >> > your server in real life, but on the downside you would be >dependent >> >> > on Adobe hosting the swz files on the same url (Imagine the Java >SDK >> >> > depending on a Sun Url). Usually I trust my own server most :-) >> >> >> >> > If you want to load the rsls from Adobe I see no real way to >optimize >> >> > besides eventually changing the order of the rsls to check your >server >> >> > first and Adobes servers after that. If you now remove the Adobe >rsls >> >> > and swzs then the application would try to load them from your >server >> >> > first - this would fail - and then it would try Adobes server. >When >> >> > loading your application modules however your Server would >immediately >> >> > serve them. >> >> >> >> > I have to admit that I like the "load everything from your own >server" >> >> > approach a lot more than the other one. >> >> >> >> > Just to add my 50ct to the discussion. >> >> >> >> > Chris >> >> >> >> > 2012/4/10 [email protected] <[email protected]>: >> >> > > Hi, I have more or less the same issue. >> >> >> >> > > Did you find any workaround ? >> >> >> >> > > Thanks, >> >> > > BQ. >> >> >> >> > > On Monday, September 26, 2011 7:19:15 AM UTC+2, J_A_X wrote: >> >> >> >> > >> I'm wondering if it's possible to fix a smallish issue with >the >> >> > >> compilation process. I set my RSL url like this: >> >> >> >> > >> <rslUrls> >> >> >> >> > >> <url> >> >> > >> >http://fpdownload.adobe.com/pub/{extension}/flex/${flex.sdk.version}/{artifactId}_{version}.{extension} >> >> > </url> >> >> > >> <url>rsls/{artifactId}-{version}.{extension}</url> >> >> > >> </rslUrls> >> >> >> >> > >> The first is of course to get the flex framework cached RSLs, >and >> the >> >> > >> second is for local RSLs. This of course works fine, but my >> problem >> >> > comes >> >> > >> with the config.xml that gets created: >> >> >> >> > >> <runtime-shared-library-path> >> >> >> >> > >> ><path-element>C:\Users\mboudreau\.m2\repository\com\adobe\flex\framework\framework\4.5.1.21328\framework-4.5.1.21328.swc</path-element> >> >> >> >> > >> <rsl-url> >> >> >>http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/framework_4.5.1.. >> .. >> >> > </rsl-url> >> >> >> >> > >> <policy-file-url> >> http://fpdownload.adobe.com/pub/swz/crossdomain.xml >> >> > </policy-file-url> >> >> > >> <rsl-url>rsls/framework-4.5.1.21328.swz</rsl-url> >> >> > >> </runtime-shared-library-path> >> >> >> >> > >> So it would look in both location for the RSL file, for all >RSLs. >> This >> >> > >> isn't much an issue with the Flex RSL, but it does become one >when >> >> > trying to >> >> > >> load my local RSLs since it always look at the adobe site >first. >> When >> >> > I'm >> >> > >> testing this in my browser, it seems that it takes a few >seconds >> longer >> >> > to >> >> > >> load my application when using this method because it needs >to >> wait for >> >> > the >> >> > >> request to come back before going to the next url. >> >> >> >> > >> I was hoping that there might be a way to fix this to have >only one >> >> > >> specific url per RSL so that it doesn't have to go through >each >> rslUrl. >> >> >> >> > > -- >> >> > > 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/ >> >> >> >> > -- >> >> > 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/ >> > >> > -- >> > 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/ >> >> -- >> 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/ >> > >-- >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/
I think there would be licensing issues in deploying swz on Sonatype or any other public repository as it's not part of the opensource package IIRC. The only sustainable option IMHO is to have your own (proxying) private repository. -- Simon Morvan -- 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/
