.
-
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
flex.apache.org
Betreff: Re: Questions about current mavenizer status
Well, my problem was several months ago when I tried to use the package
"org.apache.flex" instead of "com.adobe.flex", but it was because Flexmojos
6 was still being developed. This time I only remember I had to
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
org
Betreff: Re: Questions about current mavenizer status
Well, my problem was several months ago when I tried to use the package
"org.apache.flex" instead of "com.adobe.flex", but it was because Flexmojos
6 was still being developed. This time I only remember I had to change
gmail.com]
> Gesendet: Dienstag, 19. November 2013 21:47
> An: Apache Flex Developers ML
> Betreff: Re: Questions about current mavenizer status
>
> Yes, it worked as described in the README. What was your problem exactly?
> I set the use-apache-gid parameter to false, because all
gt; > > > > the discussion always tends to explode in tons of emails and then
> > > > suddenly
> > > > > ends nowhere, so I have given up on this. I think the FDK
> Downloader
> > +
> > > > > Mavenizer path being the least complicated path. All others will
> > > > definit
her generate them as apache or adobe
groupIds.
Chris
-Ursprüngliche Nachricht-
Von: Toni Vega [mailto:toniveg...@gmail.com]
Gesendet: Dienstag, 19. November 2013 21:35
An: dev@flex.apache.org
Betreff: Re: Questions about current mavenizer status
Did the param "fdktarget" wor
my experience on the
> > > > Flexmojos Mailinglist (when it still existed) was that people
> > > > don't read documentation ;-)
> > > >
> > > > Chris
> > > >
> > > >
> > > Cosma/Toni/Chris,
> > >
> &g
iscussed in this thread is
> consistent with what is described here [1] If not, can one of you
> please update the wiki? This is very valuable info for others who
> want to go the mavenizer route, so please help keep the docs
> upto-date.
>
> Thanks,
> Om
>
> [1]
> htt
ayhem because from my experience on the Flexmojos
> > > > Mailinglist (when it still existed) was that people don't read
> > > > documentation ;-)
> > > >
> > > > Chris
> > > >
> > > >
> > > Cosma/Toni/Chris,
> >
t; >
> > > Chris
> > >
> > >
> > Cosma/Toni/Chris,
> >
> > Can you please make sure that the info discussed in this thread is
> > consistent with what is described here [1]
> > If not, can one of you please update the wiki? This is very valuable
> info
> > for othe
you please update the wiki? This is very valuable info
> for others who want to go the mavenizer route, so please help keep the docs
> upto-date.
>
> Thanks,
> Om
>
> [1]
> https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+SDK+Mavenizer
>
>
>
> >
valuable info
for others who want to go the mavenizer route, so please help keep the docs
upto-date.
Thanks,
Om
[1]
https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+SDK+Mavenizer
>
> -Ursprüngliche Nachricht-
> Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
>
ber 2013 18:26
An: Apache Flex Developers ML
Betreff: Questions about current mavenizer status
Hi there,
I’m in the process of trying of rolling out Apache Flex 4.11 internally for the
other employees of my company, and I need to deploy the related artifacts to
the company Maven repo.
AFAIK, the o
Thank you very much Toni, I’ve just successfully (?) created the artifacts
locally, very straightforward so far, no need to provide a separate AIR SDK
to the mavenizer. Tomorrow I’ll try to deploy them to the m2 repo and I
will report back.
The artifact names are determined by the mavenizer itself
Sorry, I forgot that I was using adt-maven.plugin by yelbota and probably
was the plugin who required the zipped version of the SDK. Just try it and
let me know. In that case, maybe you should deploy SDKs versions like
3.9.win and 3.9.mac and use different profiles to build. Maybe someone has
a bet
Hi Cosma, recentlly i was able to mavenize a mobile air application using
FDK 4.11 and AIR 3.9. I'll try to answer you. I hope to have understood
your questions and doubts.
Q1.: Yes, that is the way, although i had to do some tricks with package
names in flexmojos
Q2.: The mavenizer is able to ext
Hi there,
I’m in the process of trying of rolling out Apache Flex 4.11 internally for
the other employees of my company, and I need to deploy the related
artifacts to the company Maven repo.
AFAIK, the only way to do this for 4.11 is by mavenizing/deploying a
downloaded FDK, is this right? I was
29 matches
Mail list logo
