.
-
From: dev@flex.apache.org
Sent: Tuesday, November ##, #:##:## PM (-##:##)
To kana##@paypal.com
Subject: AW: Questions about current mavenizer status
With the #.#.#-SNAPSHOT I deployed # Days ago you can actually start
ou don't use any sort of deployer in that case ;-)
>>
>>
>> Von: Avi Kessner [akess...@gmail.com]
>> Gesendet: Mittwoch, 20. November 2013 13:27
>> An: dev@flex.apache.org
>> Betreff: Re: AW: Questions about current m
hat case ;-)
>
>
> Von: Avi Kessner [akess...@gmail.com]
> Gesendet: Mittwoch, 20. November 2013 13:27
> An: dev@flex.apache.org
> Betreff: Re: AW: Questions about current mavenizer status
>
> It's not really an edge case. In my company we just co
Well I guess you don't use any sort of deployer in that case ;-)
Von: Avi Kessner [akess...@gmail.com]
Gesendet: Mittwoch, 20. November 2013 13:27
An: dev@flex.apache.org
Betreff: Re: AW: Questions about current mavenizer status
It's not real
sma Colanicchia" ha
> scritto:
> >>
> >> > Great work, thank you. Note about the wiki page: "The actual Mavenizer
> >> > (SDKDeployer)" maybe should be "... (SDKGenerator)"? (If it is
> >> > referred to the related class name) Il 1
3 11:55
An: Apache Flex Developers ML
Betreff: Re: AW: Questions about current mavenizer status
I’m now trying to deploy the artifacts to a shared repository with the
in-vm deployer.
Our repository is not exposed via HTTP, instead is accessed as a network
share using a file://... repository UR
gt; Thanks for reporting.
>>
>> Chris
>>
>> -Ursprüngliche Nachricht-
>> Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
>> Gesendet: Dienstag, 19. November 2013 23:03
>> An: Apache Flex Developers ML
>> Betreff: Re: AW: Questions about current mav
;
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
> Gesendet: Dienstag, 19. November 2013 23:03
> An: Apache Flex Developers ML
> Betreff: Re: AW: Questions about current mavenizer status
>
> Also, there's probably a ty
Ok ... so I fixed the two mistakes :-)
Thanks for reporting.
Chris
-Ursprüngliche Nachricht-
Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
Gesendet: Dienstag, 19. November 2013 23:03
An: Apache Flex Developers ML
Betreff: Re: AW: Questions about current mavenizer status
Also
exmojos 6.x uses com.adobe.flex and Flexmojos 7.x
> >> org.apache.flex :-)
> >>
> >> -Ursprüngliche Nachricht-
> >> Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> >> Gesendet: Dienstag, 19. November 2013 22:44
> >> An: d
> Sorry ... Flexmojos 6.x uses com.adobe.flex and Flexmojos 7.x
>> org.apache.flex :-)
>>
>> -Ursprüngliche Nachricht-
>> Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
>> Gesendet: Dienstag, 19. November 2013 22:44
>> An: dev@flex.apac
com.adobe.flex and Flexmojos 7.x
> org.apache.flex :-)
>
> -Ursprüngliche Nachricht-
> Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> Gesendet: Dienstag, 19. November 2013 22:44
> An: dev@flex.apache.org
> Betreff: AW: Questions about current maven
Sorry ... Flexmojos 6.x uses com.adobe.flex and Flexmojos 7.x org.apache.flex
:-)
-Ursprüngliche Nachricht-
Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Gesendet: Dienstag, 19. November 2013 22:44
An: dev@flex.apache.org
Betreff: AW: Questions about current
Done ... docs are up to date :-)
-Ursprüngliche Nachricht-
Von: omup...@gmail.com [mailto:omup...@gmail.com] Im Auftrag von OmPrakash
Muppirala
Gesendet: Dienstag, 19. November 2013 20:52
An: dev@flex.apache.org
Betreff: Re: Questions about current mavenizer status
On Tue, Nov 19, 2013 a
This is a maven problem, that I wasn't able to work myself around.
So Flexmojos 6.x uses com.apache.flex and Flexmojos 7.x uses org.apache.flex
So if you want to use Adobe FDKs you will have to stick to Flexmojos 6.x and if
you want to use the latest Apache Flex FDKs, you can use Flexmojos 6.x and
With the 7.0.0-SNAPSHOT I deployed 2 Days ago you can actually start using
"org.apache.flex" :-)
The Flexmojos 6 Branch requires you to have the Apache FDKs with a
"com.adobe.flex" groupId. So depending on the version of Flexmojos you are
intending on using, you have to either generate them as a
I'll give the wiki document a workover ... stay tuned and thanks for the
feedback.
Chris
-Ursprüngliche Nachricht-
Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
Gesendet: Dienstag, 19. November 2013 21:47
An: Apache Flex Developers ML
Betreff: Re: Questions about current mavenizer
Hi Cosma,
yes you are right. The Downloader only downloads the artifacts for the current
operating-system. But for example older Adobe FDKs had the following structure:
{root}/runtimes/air
{root}/runtimes/air/android
{root}/runtimes/air/mac
{root}/runtimes/air/win
{root}/runtimes/player/10.2/
{r
Hi Cosma,
as Toni already confirmed, the mavenizer is currently the easiest way to create
maven artifacts from a Flex SDK you downloaded using the Downloader.
The Mavenizer doesn't actually require the Air SDK, the problem was, that the
Mavenizer is able to mavenize any Flex SDK starting from Ad
19 matches
Mail list logo
