Hi Alex, I searched on the nexus hosted inner company, but didn't try to find it outside. I thought Flex SDK was in maven central as well is not the case? For example a quick search shows [1] where I see 4.12 and 4.13 here, and I suppose those should have the RBs right?
If is not the case, I think can we upload the latest 4.16.1 to maven central? [1] https://mvnrepository.com/artifact/org.apache.flex.framework/flex-framework El lun., 15 oct. 2018 a las 22:57, Alex Harui (<[email protected]>) escribió: > Hi Carlos, > > Where did you get that artifact? I could not find it on Maven Central. > Maybe you ran the Mavenizer on a Flex SDK? If so, the question is whether > we want Maven users to have to use the Mavenizer. > > -Alex > > On 10/15/18, 1:38 PM, "Carlos Rovira" <[email protected]> wrote: > > Hi Alex, > > I was looking for maven resoucebundle in maven and we have separate > artifacts. an example: > > > /org/apache/flex/framework/framework/4.16.0/framework-4.16.0-es_ES.rb.swc > > So I think it should not be a problem in maven too, and we can reuse > from > flex :) > > Best > > > El dom., 14 oct. 2018 a las 23:56, Alex Harui > (<[email protected]>) > escribió: > > > Hi, > > > > I just pushed support for old Flex resource bundles in Royale. Some > > people migrating old Flex apps will find it more convenient and may > even > > require that [ResourceBundle] metadata works. > > > > The interesting piece of this is that we can use the Flex resource > bundles > > as is. They don't need to be re-compiled by Royale from .properties > files. > > > > The question for us is about how to deal with downloading these > bundles. > > Right now, I've commented out [ResourceBundle] metadata and the > > -library-path options that point to the Flex bundles until we figure > out > > where to put them and how. > > > > I think for Ant, it is as simple as downloading a Flex SDK and > grabbing > > the bundles. The Royale build already grabs PixelBender. The Flex > SDK > > download is big, so it will slow up builds from scratch. > > > > For Maven, it is trickier. I don't think there are Maven artifacts > for > > Flex resource SWCs. Does anybody know for sure, one way or > another? If > > not, we might manually publish the SWCs as artifacts. > > > > I'm not in favor of copying the Flex properties files into the > Royale repo > > and putting together Ant and Maven builds for them, but if some > volunteer > > wants to do it, I won't object, I just don't want to spend my time > doing > > it, since these files should effectively be immutable. > > > > Thoughts? > > -Alex > > > > > > -- > Carlos Rovira > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C6e1a35fa0f844363b67908d632de3059%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636752327203767909&sdata=J%2B%2Ff4hcbKOcRyO0HkYsyFv1sVtBAkrRzRzOY4N0qMaw%3D&reserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
