incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject RE: AW: AW: Flex Maven FDK Generator RC1
Date Wed, 26 Sep 2012 18:13:44 GMT
OK, let's start with that link.  I'll take a look this evening.

Alex Harui
Apache Flex Team
http://blogs.adobe.com/aharui

> -----Original Message-----
> From: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]
> Sent: Wednesday, September 26, 2012 11:07 AM
> To: flex-dev@incubator.apache.org
> Subject: AW: AW: AW: Flex Maven FDK Generator RC1
> 
> Hi Alex,
> 
> If you want I can simply send you the link to the zip with all Flex versions in their
> Mavenized form. But I would do that off the list. After all I only want to provide
> that for testing and discussion and not for real usage :-) There you could simply
> have a look at how it would look like.
> 
> Chris
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 26. September 2012 19:54
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: Flex Maven FDK Generator RC1
> 
> Hi Chris,
> 
> This sounds more possible.  I have some more questions:
> 
> 1) What goes in the pom.xml?
> 2) Are there any constraints on what the path is to the folder?
> 
> Adobe just recently restructed the playerglobal archive page.  The link pattern is
> now:
> 
> http://fpdownload.macromedia.com/get/flashplayer/installers/archive/playergl
> obal/playerglobal10_1.swc
> http://fpdownload.macromedia.com/get/flashplayer/installers/archive/playergl
> obal/playerglobal10_2.swc
> 
> Asking them to add a whole "com/adobe/flash..." would take more convincing
> than asking them to place each SWC in a folder and drop a pom.xml in it.
> Then the links would look more like:
> 
> http://fpdownload.macromedia.com/get/flashplayer/installers/archive/playergl
> obal/10.1/playerglobal10_1.swc
> http://fpdownload.macromedia.com/get/flashplayer/installers/archive/playergl
> obal/10.2/playerglobal10_2.swc
> 
> Or should it be:
> 
> http://fpdownload.macromedia.com/get/flashplayer/installers/archive/playergl
> obal/10.1/playerglobal.swc
> http://fpdownload.macromedia.com/get/flashplayer/installers/archive/playergl
> obal/10.2/playerglobal.swc
> 
> Thanks,
> -Alex
> 
> On 9/26/12 10:30 AM, "christofer.dutz@c-ware.de" <christofer.dutz@c-
> ware.de>
> wrote:
> 
> > Hi Alex,
> >
> > Well if Adobe would run its own repo this would be even better. I
> > think you don't even have to really run a full blown Maven repo server
> > for that. I think it should be enough to manually serve Maven
> > artifacts with a simple Http Server. All If for example there was an
> > Adobe Webserver somewhere that serves an URL like this
> >
> "http://some.cool.server.adobe.com/some/context/whatsoever/com/adobe/f
> > lash/fra mework/playerglobal/10.1/" and inside that directory you make
> > the pom xml and the playerglobal swc available for download, this
> > would be equally good. Then we could add the base Url
> > "http://some.cool.server.adobe.com/some/context/whatsoever/" to our
> > Maven repos and they would automatically fetch the stuff they need
> > from that Adobe server.
> >
> > Chris
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Alex Harui [mailto:aharui@adobe.com]
> > Gesendet: Mittwoch, 26. September 2012 19:21
> > An: flex-dev@incubator.apache.org
> > Betreff: Re: AW: Flex Maven FDK Generator RC1
> >
> >
> >
> >
> > On 9/26/12 10:11 AM, "christofer.dutz@c-ware.de"
> > <christofer.dutz@c-ware.de>
> > wrote:
> >
> >> Hi Alex,
> >>
> >> Well in general it would be enough if Adobe simply published the
> >> airglobal, playerglobal and osmf swcs along with their language
> >> resources to a public repo ... only these 3 artifacts would be enough
> >> to make us all really really happy and Apache could start officially
> >> deploying Flex FDKs using maven without any legal issues.
> >>
> > Are there alternatives?  Getting Adobe to agree to deploy to a public
> > repo is probably much harder than having a separate public Adobe repo
> > on an Adobe server, which is probably much harder than trying to make
> > the current Adobe download pages work with Maven.
> >
> > I thought someone else once posted some code on this list with a
> > pom.xml next to it.  Isn't that the minimum requirement or is there more?
> >
> > What is involved in creating a "repo"?
> >
> >> I could even send you the prepared artifacts (Files with the correct
> >> naming convention as well as the maven poms).
> >>
> >> Chris
> >>
> >>
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Alex Harui [mailto:aharui@adobe.com]
> >> Gesendet: Mittwoch, 26. September 2012 18:22
> >> An: flex-dev@incubator.apache.org
> >> Betreff: Re: Flex Maven FDK Generator RC1
> >>
> >>
> >>
> >>
> >> On 9/26/12 12:18 AM, "Frédéric THOMAS" <webdoublefx@hotmail.com>
> wrote:
> >>
> >>
> >>>
> >>>
> >>>> If we
> >>>> wanted to create maven artifacts for the official maven repo, we
> >>>> certainly can't bundle in Adobe stuff, so wouldn't that require
> >>>> that Adobe either publishes to the official maven repo or at
> >>>> minimum puts up its own pom.xmls on its site so maven can pull the
> >>>> Adobe stuff from there?
> >>>
> >>>
> >>>
> >>> Not sure of what you're talking about, OSMF, Textlayout, or something else
> ?
> >>>
> >> Apache Flex has TextLayout now.  But OSMF, PlayerGlobal, FlashPlayer,
> >> and AIR SDK will have to be downloaded from Adobe. Should Adobe be
> >> doing something to make it easier for Maven to download those things?
> >>
> >> --
> >> Alex Harui
> >> Flex SDK Team
> >> Adobe Systems, Inc.
> >> http://blogs.adobe.com/aharui
> >>
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe Systems, Inc.
> > http://blogs.adobe.com/aharui
> >
> 
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui


Mime
View raw message