Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 21E66DCA5 for ; Wed, 26 Sep 2012 17:30:46 +0000 (UTC) Received: (qmail 53538 invoked by uid 500); 26 Sep 2012 17:30:45 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 53510 invoked by uid 500); 26 Sep 2012 17:30:45 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 53501 invoked by uid 99); 26 Sep 2012 17:30:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 17:30:45 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [80.67.18.16] (HELO smtprelay04.ispgateway.de) (80.67.18.16) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 17:30:39 +0000 Received: from [10.128.0.7] (helo=exchange.df.eu) by smtprelay04.ispgateway.de with esmtps (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1TGvRC-00071W-JE for flex-dev@incubator.apache.org; Wed, 26 Sep 2012 19:30:18 +0200 Received: from ECCR06PUBLIC.exchange.local ([10.128.2.55]) by efe04.exchange.local ([10.128.0.7]) with mapi; Wed, 26 Sep 2012 19:30:18 +0200 From: "christofer.dutz@c-ware.de" To: "flex-dev@incubator.apache.org" Date: Wed, 26 Sep 2012 19:30:18 +0200 Subject: AW: AW: Flex Maven FDK Generator RC1 Thread-Topic: AW: Flex Maven FDK Generator RC1 Thread-Index: Ac2btzUojonnHgfwTn69outs13kL8gAS9JzhAAGXDpAAAHe0RgAAH7YA Message-ID: <66E38C42347D6446BF7FCB22C3D3878072DE7C73D3@ECCR06PUBLIC.exchange.local> References: <66E38C42347D6446BF7FCB22C3D3878072DE7C73CD@ECCR06PUBLIC.exchange.local> In-Reply-To: Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org 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 t= hink it should be enough to manually serve Maven artifacts with a simple Ht= tp Server. All If for example there was an Adobe Webserver somewhere that s= erves an URL like this "http://some.cool.server.adobe.com/some/context/what= soever/com/adobe/flash/framework/playerglobal/10.1/" and inside that direct= ory you make the pom xml and the playerglobal swc available for download, t= his 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 wou= ld automatically fetch the stuff they need from that Adobe server. Chris -----Urspr=FCngliche Nachricht----- Von: Alex Harui [mailto:aharui@adobe.com]=20 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" wrote: > Hi Alex, >=20 > Well in general it would be enough if Adobe simply published the=20 > airglobal, playerglobal and osmf swcs along with their language=20 > resources to a public repo ... only these 3 artifacts would be enough=20 > to make us all really really happy and Apache could start officially=20 > deploying Flex FDKs using maven without any legal issues. >=20 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 Adob= e server, which is probably much harder than trying to make the current Ado= be download pages work with Maven. I thought someone else once posted some code on this list with a pom.xml ne= xt 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=20 > naming convention as well as the maven poms). >=20 > Chris >=20 >=20 >=20 > -----Urspr=FCngliche 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 >=20 >=20 >=20 >=20 > On 9/26/12 12:18 AM, "Fr=E9d=E9ric THOMAS" wrot= e: >=20 >=20 >>=20 >>=20 >>> If we >>> wanted to create maven artifacts for the official maven repo, we=20 >>> certainly can't bundle in Adobe stuff, so wouldn't that require that=20 >>> Adobe either publishes to the official maven repo or at minimum puts=20 >>> up its own pom.xmls on its site so maven can pull the Adobe stuff=20 >>> from there? >>=20 >>=20 >>=20 >> Not sure of what you're talking about, OSMF, Textlayout, or something el= se ? >>=20 > Apache Flex has TextLayout now. But OSMF, PlayerGlobal, FlashPlayer,=20 > and AIR SDK will have to be downloaded from Adobe. Should Adobe be=20 > doing something to make it easier for Maven to download those things? >=20 > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >=20 -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui