Hi Alex,

maybe it's not only a folder, we should see it. For some approach, I think
is mostly like all the Jewel theme projects. Maybe we need to create a
project per RB, that will end in its own SWC and artifact for maven. Then
we can reference each single RB-SWC in a pom.xml. This implies copy/paste
the RB from Apache Flex project.


El mar., 16 oct. 2018 a las 18:55, Alex Harui (<[email protected]>)
escribió:

> Hi Carlos,
>
> I don't think I understand how to make a folder of RB SWCs available to
> Maven.  Don't all Maven dependencies require Maven coordinates in a POM?
> Or are you suggesting that folks will have to use additionalCompilerOptions
> in the pom to specify -library-path+=<path to RB SWCs>?
>
> -Alex
>
> On 10/16/18, 9:39 AM, "Carlos Rovira" <[email protected]> wrote:
>
>     Hi,
>
>     just let us know that uploading to Maven Central seems a lot of manual
> work
>     to upload all of the RBs individually.
>     So maybe we should take other way, that could be temporal, and as
> someone
>     has the time we could go the Maven Central way ( If all thinks is the
>     proper way).
>
>     I think, for now, as a temporal way, the most easy way is to make a
>     temporal project library and copy there all RBs so it can be available
> from
>     our project to ANT and MAVEN.
>
>     Thoughts?
>
>
>
>
>     El mar., 16 oct. 2018 a las 8:33, Alex Harui (<[email protected]
> >)
>     escribió:
>
>     > You can ask Chris if you want.  Flex was never made Maven-compatible.
>     > FlexJS/Royale was the first Flex-like SDK to be Maven-compatible.
>     >
>     > -Alex
>     >
>     > On 10/15/18, 10:58 PM, "Carlos Rovira" <[email protected]>
> wrote:
>     >
>     >     Hi Alex,
>     >
>     >     it's strange to me that artifacts are not published, I could ask
> Chris
>     > Dutz
>     >     what's the reason and see what is his response about it, and if
> we can
>     > if
>     >     it will be very difficult to do.
>     >     I think that seems to be the best way to go.
>     >
>     >
>     >
>     >     El mar., 16 oct. 2018 a las 0:34, Alex Harui
> (<[email protected]
>     > >)
>     >     escribió:
>     >
>     >     > Hi Carlos,
>     >     >
>     >     > I do not think Apache Flex or Adobe Flex was ever published as
> Maven
>     >     > artifacts.  The link you referenced only seems to reference
> poms and
>     > not
>     >     > binaries.  There are no pom.xml files in the Apache Flex repo.
>     >     >
>     >     > AIUI, there is this thing called a Mavenizer that can take a
> Flex
>     > SDK and
>     >     > generate Maven artifacts.  It is in the flex-utilities repo.  I
>     > think it
>     >     > will put the artifacts in your internal repository, but I
> don't think
>     >     > anyone from Adobe or Apache Flex has ever tried to push those
>     > artifacts to
>     >     > Maven Central.  I'm not sure what it would take to do that.
>     >     >
>     >     > So, I'm not sure what the right answer is.
>     >     >
>     >     > Thanks,
>     >     > -Alex
>     >     >
>     >     > On 10/15/18, 3:20 PM, "Carlos Rovira" <[email protected]
> >
>     > wrote:
>     >     >
>     >     >     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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmvnrepository.com%2Fartifact%2Forg.apache.flex.framework%2Fflex-framework&amp;data=02%7C01%7Caharui%40adobe.com%7Cd5adcf9035e54f7b222c08d63385e822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753047558552663&amp;sdata=852mkHDP8i6cgV%2BseTHtBYOUif0WKiFwgBDBQeQg14Q%3D&amp;reserved=0
>     >     >
>     >     >
>     >     >     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&amp;data=02%7C01%7Caharui%40adobe.com%7Cd5adcf9035e54f7b222c08d63385e822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753047558562672&amp;sdata=pQa3dQZUdmrjlniEKltUz7%2F39fPu5UFEgHXJMeI70OE%3D&amp;reserved=0
>     >     >     >
>     >     >     >
>     >     >     >
>     >     >
>     >     >     --
>     >     >     Carlos Rovira
>     >     >
>     >     >
>     >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Cd5adcf9035e54f7b222c08d63385e822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753047558562672&amp;sdata=pQa3dQZUdmrjlniEKltUz7%2F39fPu5UFEgHXJMeI70OE%3D&amp;reserved=0
>     >     >
>     >     >
>     >     >
>     >
>     >     --
>     >     Carlos Rovira
>     >
>     >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Cd5adcf9035e54f7b222c08d63385e822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753047558562672&amp;sdata=pQa3dQZUdmrjlniEKltUz7%2F39fPu5UFEgHXJMeI70OE%3D&amp;reserved=0
>     >
>     >
>     >
>
>     --
>     Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7Cd5adcf9035e54f7b222c08d63385e822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753047558562672&amp;sdata=pQa3dQZUdmrjlniEKltUz7%2F39fPu5UFEgHXJMeI70OE%3D&amp;reserved=0
>
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Reply via email to