AW: [DRAFT] Apache Flex December 2013 Report

[christofer.d...@c-ware.de]

Just to understand the current Position:
- Alex is currently the chair and would volunteer to continue, but never has 
stated that he would aktually like to stay in that Position (It's more the 
others stating that they would want him to stay)
- Justin actively would like to be the chair and would also be capable of doing 
so

Currently it Looks as if Alex wouldn't mind passing on the Position to Justin 
and Justin would really like to do the Job? And if the chair Position has 
nothing to do with Alex' involvement with the Flex Project, wouldn't this give 
him even more time to do non-beaurocratic stuff? Then he could concentrate his 
time on delivering code and not for delivering reports?

Just my thoughts to the discussion.

Chris




Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Dienstag, 3. Dezember 2013 08:16
An: dev@flex.apache.org
Betreff: Re: [DRAFT] Apache Flex December 2013 Report

Hi,

IMO he's not clearly stated that he will stand for another year and yes the 
choice is his. The board report seems to me to be a good place to state that. 
When putting the guidelines together consensus was that the chair should be for 
a year or reviewed every year. There may be other PMC members who would also 
like to have a turn at being the chair.

There does seem some support for changing the chair (see the other discuss 
thread on that) but there's certainly not a consensus either way, up to Alex to 
consider and decide. Again I think everyone can agree he's done a good job and 
will continue to do so, but it may also be good to change and spread the 
experience about.

Looking back to when Alex was voted in it was pointed out by the mentors that 
there should of been more discussion on who should be chair. [1] Now seems a 
good time to have that discussion.

Thanks,
Justin

1. http://markmail.org/message/3cljrqmwfipsq7zn

AW: [DISCUSS] Apache Flex chair

[christofer.d...@c-ware.de]

I see it exactly the same way (Except for the thing with the letters and the 
number) ;-)

Chris

-Ursprüngliche Nachricht-
Von: Avi Kessner [mailto:akess...@gmail.com] 
Gesendet: Sonntag, 1. Dezember 2013 12:52
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Apache Flex chair

I didn't care, and thought the rational to give more people the experience is a 
good one.  However, the logic in following argument might be sound and a bit 
scary.

"There's the additional rationale keeping Alex in the position as I think it 
would be less likely for folks at Adobe to assign him to some non-Flex position 
if he's the Flex PMC chair.
"

Hearing from Alex on that would be good. Because I don't think we are ready to 
miss out on Adobe support just yet.

brought to you by the letters A, V, and I and the number 47


On Sun, Dec 1, 2013 at 1:45 PM, Jeffry Houser  wrote:

>
>  I don't care myself.  My impression is that many of the folks on this 
> list are US based; and you started the conversation at the start of a 
> major US Holiday [Thanksgiving].  That may have contributed to the 
> lack of a response.  I, myself, have been running non-stop for 6 days 
> [and I have two more before I can look up].
>
>  You may consider waiting until mid-week and giving the thread another 
> poke.
>
>
> On 12/1/2013 1:04 AM, Justin Mclean wrote:
>
>> Hi,
>>
>> Not exactly a huge response of this so I'd assume most people don't 
>> care one way or another. Anyone else have something to say?
>>
>> Justin
>>
>
>
> --
> Jeffry Houser
> Technical Entrepreneur
> http://www.jeffryhouser.com
> 203-379-0773
>
>

AW: Donation News

[christofer.d...@c-ware.de]

Just my 50ct to this Topic ... 

you are talking about the demo in which you can select Nokia phones depending 
on different aspects ... how about changing this to: "Apache Flex Commiter" 
selection. 

Each Member of the Flex Team that wants to be part of this sends a Picture and 
fills out a short form containng some Information on what parts of Flex he is 
working on, Hobbies, Movies and presto ... no license issues and it would even 
give users the benefit of being able to see who's working on what on Apache 
Flex project?

Chris


Von: Mark Kessler [kesslerconsult...@gmail.com]
Gesendet: Freitag, 29. November 2013 13:41
An: Dev@Flex
Betreff: Re: Donation News

Well you could try [1], they seem to release all rights to their photos
[2].  I think [3] works as well.

[1] http://openclipart.org
[2] http://openclipart.org/share


[3] http://www.clker.com/


-Mark

On Fri, Nov 29, 2013 at 1:05 AM, Alex Harui  wrote:

> Well, I could be wrong, but that's not my understanding, based on some
> email threads from Roy over the past few years on general@.  Even if code
> has an Apache License, Apache projects are not supposed to use such code
> without explicit permission.  Maybe there are different rules for icons.
> But first, let's first see if anyone comes up with CC-SA free art. Then we
> should ask Legal before checking it in.
>
>

AW: Donation News

[christofer.d...@c-ware.de]

I would volunteer to do the BlazeDS testing as I have real interest on working 
on BlazeDS (I do have quite a set of improvements, I would like to address as 
soon as it is donated).

Chris


Von: Alex Harui [aha...@adobe.com]
Gesendet: Donnerstag, 28. November 2013 08:42
An: dev@flex.apache.org
Betreff: Donation News

I finally got a clean-looking scan on a bunch of Adobe stuff.  I will be
submitting it to Legal for review next week (reminder that the US is on
holiday Thursday and Friday).  Then, unless Legal sees something it
doesn't like, I have to get some business folks and a VP to sign off and
then I replace any remaining Adobe headers with Apache headers and start
checking it in.  Still hoping to get it done in December.

Contents of this donation will hopefully be:

1. Several popular ADC web articles, tutorials, etc.
2. A newer version of FDB that supports workers
3. FlexPMD
4. The Mobile Trader demo app
5. A spec for MXML
6. Some files that are needed to complete the BlazeDS donation
7. As much of Squiggly as I could find
8. TourDeFlex

The BlazeDS donation is otherwise ready except for the files I mentioned
in #6.  With those files, the BlazeDS build scripts seems to run
successfully.  Testing is still needed of course, but will happen
post-donation if we can find a volunteer.

Some things to think about:
A) The ADC content is full of references to stylesheets that give it its
look and feel. I haven't put the stylesheets in the donation because I'm
pretty sure the Adobe business folks will want us to come up with a
different look.
B) For various copyright reasons, many of the images in the ADC examples
could not be donated and have been replaced by copies of other ADC images.
 At some point, we may need to spend time on fixing this up
C) Where do we check in the ADC content?  Does it just go in SVN for the
web-site?
D) A few files in the FlexPMD trunk belong to third-parties and therefore
not in the donation.  It looks like it was just a few tests and bug test
cases.  However, I'm not planning to fix up the build script.
E) Where do we check in FlexPMD?  I think flex-utilities
F) TourDeFlex and the FlexStore example on the ADC use images of Nokia
phones.  These images will not be donated.  Anybody in the mood to
generate 22 different phone images? It is probably better if they are
hand-drawn and not photos of a real phone.

-Alex

Reason for not locating experimental_mobile in the frameworks/libs/mobile directory?

[christofer.d...@c-ware.de]

Hi,

I am currently in the process of migrating all of my applications to FM7 and 
Flex 4.11, I just noticed that my mavenizer includes the experimental_mobile 
lib in with the rest of the normmal framework. The reason is that it is not 
located in the mobile subdirectory. Is there a reason for this not being there? 
To me it sort of more belongs there than with the rest of the framework.

Chris

AW: AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

ere, but the file set is identical (no
> > additional file or artifacts are generated).
> >
> > So, it seems that the mavenized version is actually the same when
> > generated from a mac/win FDK. Probably, many of the differences will
> emerge
> > once mobile packaging will be supported by flexmojos?
> >
> > I can provide the output of the diff runs, if required..
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 2013/11/20 christofer.d...@c-ware.de 
> >
> > 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, there's probably a typo on " url: (optional) The username used to
> >> deploy the artifacts.
> >> mvn: (required only if a username is provided) The password used to
> >> deploy the artifacts"
> >> Il 19/nov/2013 23:00 "Cosma 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 19/nov/2013 22:47
> >> > "christofer.d...@c-ware.de" < christofer.d...@c-ware.de> ha scritto:
> >> >
> >> >> 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 mavenizer status
> >> >>
> >> >> 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 set the "use-apache-gid"
> >> >> parameter to false or use Flexmojos 7.x and set it to true.
> >> >>
> >> >> Hope that clears up things a little :-)
> >> >>
> >> >> Chris
> >> >>
> >> >> -Ursprüngliche Nachricht-
> >> >> Von: Toni Vega [mailto:toniveg...@gmail.com]
> >> >> Gesendet: Dienstag, 19. November 2013 22:11
> >> >> An: dev@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
> >> >> change the property in the parent pom of Flexmojos to use
> >> >> "org.apache.flex" and it worked fine.
> >> >>
> >> >>
> >> >> 2013/11/19 Cosma Colanicchia 
> >> >>
> >> >> > Yes, it worked as described in the README. What was your problem
> >> >> > exactly? I set the use-apache-gid parameter to false, because all
> >> >> > of my project are still using the old flexmojos versions
> >> >> >
> >> >> > Noticed now that the README.txt does not describe the
> >> >> > use-apache-god parameter, that is correctly reported in the wiki
> >> page.
> >> >> >
> >> >> >
> >> >> > 2013/11/19 Toni Vega 
> >> >> >
> >> >> > > Did the param "fdktarget" work for you, Cosma? I remember I tried
> >> >> > > to configure that quite time ago but it didn't worked forme. I
> >> >> > > also remember that Christofer recomended me not to use
> >> "org.apache.flex"
> >> >> > > package (Flexmojos 6 was still in development). This last time I
> >> >> > > tried it, I just changed the prop

AW: AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

Ok ... so I didn't think there was such a think as a file-accessible remote 
maven repository.
You never stop learning ;-) But I'll have a look at this case.

Chris


Von: Cosma Colanicchia [cosma...@gmail.com]
Gesendet: Mittwoch, 20. November 2013 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 URL. The new deployer fail instantly
with an ArtifactTransferException.

Probably this is an edge case, with the previous deployer I was able to
successful deploy the artifacts (probably because it relies on standard mvm
commands).


This is the exception stack trace:

Installing Artifact: com.adobe.air:compiler:3.9
 - File with extension pom
org.eclipse.aether.deployment.DeploymentException: Failed to deploy
artifacts: Could not transfer artifact com.adobe.air:compiler:pom:3.9
from/to repo (file:///Volumes/Area\ Sviluppatori/m2-repository):
/Volumes/Area\
Sviluppatori/m2-repository/com/adobe/air/compiler/3.9/compiler-3.9.pom (No
such file or directory)
 at
org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:341)
at
org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:269)
 at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:413)
at SDKInVMDeployer.processArtifact(SDKInVMDeployer.java:214)
 at SDKInVMDeployer.processDir(SDKInVMDeployer.java:152)
at SDKInVMDeployer.processDir(SDKInVMDeployer.java:161)
 at SDKInVMDeployer.processDir(SDKInVMDeployer.java:161)
at SDKInVMDeployer.processDir(SDKInVMDeployer.java:161)
 at SDKInVMDeployer.processDir(SDKInVMDeployer.java:161)
at SDKInVMDeployer.processDir(SDKInVMDeployer.java:161)
 at SDKInVMDeployer.start(SDKInVMDeployer.java:137)
at SDKInVMDeployer.main(SDKInVMDeployer.java:89)
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not
transfer artifact com.adobe.air:compiler:pom:3.9 from/to repo
(file:///Volumes/Area\ Sviluppatori/m2-repository): /Volumes/Area\
Sviluppatori/m2-repository/com/adobe/air/compiler/3.9/compiler-3.9.pom (No
such file or directory)
 at
org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43)
at
org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:342)
 at
org.eclipse.aether.connector.basic.BasicRepositoryConnector.put(BasicRepositoryConnector.java:271)
at
org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:335)
 ... 11 more
Caused by: java.io.FileNotFoundException: /Volumes/Area\
Sviluppatori/m2-repository/com/adobe/air/compiler/3.9/compiler-3.9.pom (No
such file or directory)
 at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:194)
 at java.io.FileOutputStream.(FileOutputStream.java:145)
at
org.eclipse.aether.transport.file.FileTransporter.implPut(FileTransporter.java:85)
 at
org.eclipse.aether.spi.connector.transport.AbstractTransporter.put(AbstractTransporter.java:117)
at
org.eclipse.aether.connector.basic.BasicRepositoryConnector$PutTaskRunner.runTask(BasicRepositoryConnector.java:578)
 at
org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:337)
... 13 more




2013/11/20 Cosma Colanicchia 

> I have created the FDKs for 4.11 (with the latest AIR and FP versions, and
> all options checked) from Windows and from Mac, and tried to diff out the
> two folders.
>
> I see that there are a lot of changes, some of which are expected:
>  - /bin (adl vs adl.exe, adt vs adt.exe)
>  - /android/lib binaries (aapt vs aapt.exe, additional dlls for win)
>  - /lib/aot binaries
>  - /lib/nai binaries
>  - /runtimes
>  - a lot of differences in text files (xml, xsd and some sources), maybe
> due to line breaks?
>  - many differences in swc and jar binary files (maybe the installer is
> downloading different binary packages created with different build run?)
>
> Then I run the mavenizer, and compared the output: the swc and jar
> differences are clearly still there, but the file set is identical (no
> additional file or artifacts are generated).
>
> So, it seems that the mavenized version is actually the same when
> generated from a mac/win FDK. Probably, many of the differences will emerge
> once mobile packaging will be supported by flexmojos?
>
> I can provide the output of the diff runs, if required..
>
>
>
>
>
>
>
>
>
>
> 2013/11/20 christofer.d...@c-ware.de 
>
> Ok ... so I fixed the two mistakes :-)
>> Thanks for reporting.
>>
>> Chris
>>
>> -Ursprüngliche Nachricht-
>> Von

AW: AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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, there's probably a typo on " url: (optional) The username used to deploy 
the artifacts.
mvn: (required only if a username is provided) The password used to deploy the 
artifacts"
Il 19/nov/2013 23:00 "Cosma 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 19/nov/2013 22:47 
> "christofer.d...@c-ware.de" < christofer.d...@c-ware.de> ha scritto:
>
>> 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 mavenizer status
>>
>> 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 set the "use-apache-gid" 
>> parameter to false or use Flexmojos 7.x and set it to true.
>>
>> Hope that clears up things a little :-)
>>
>> Chris
>>
>> -Ursprüngliche Nachricht-
>> Von: Toni Vega [mailto:toniveg...@gmail.com]
>> Gesendet: Dienstag, 19. November 2013 22:11
>> An: dev@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 
>> change the property in the parent pom of Flexmojos to use 
>> "org.apache.flex" and it worked fine.
>>
>>
>> 2013/11/19 Cosma Colanicchia 
>>
>> > Yes, it worked as described in the README. What was your problem 
>> > exactly? I set the use-apache-gid parameter to false, because all 
>> > of my project are still using the old flexmojos versions
>> >
>> > Noticed now that the README.txt does not describe the 
>> > use-apache-god parameter, that is correctly reported in the wiki page.
>> >
>> >
>> > 2013/11/19 Toni Vega 
>> >
>> > > Did the param "fdktarget" work for you, Cosma? I remember I tried 
>> > > to configure that quite time ago but it didn't worked forme. I 
>> > > also remember that Christofer recomended me not to use "org.apache.flex"
>> > > package (Flexmojos 6 was still in development). This last time I 
>> > > tried it, I just changed the properties in Flexmojos parent pom.
>> Thanks!
>> > >
>> > > Regards
>> > >
>> > >
>> > > 2013/11/19 Cosma Colanicchia 
>> > >
>> > > > @Christofer
>> > > >
>> > > > Thanks for the info, just some questions: when you say "win"
>> > > > directory,
>> > > are
>> > > > you referring to the subfolders in runtimes/air and
>> > runtimes/air-captive?
>> > > > The SDK produced by the installer correctly contains the "mac"
>> > runtimes,
>> > > if
>> > > > I understand correctly I should be able to add the 
>> > > > corresponding
>> "win"
>> > > > folders (borrowing them from an SDK prepared by the installer 
>> > > > on a
>> > > Windows
>> > > > machine?) and the mavenizer should pick up them producing 
>> > > > artifacts
>> > > usable
>> > > > from win and mac, am I right? I see that the bin directory 
>> > > > already
>> > > contains
>> > > > windows batch file as well as bash scripts, so it should 
>> > > > already be cross-platform in this respect.
>> > > >
>> > > > I'll also try the in-vm deployer and let you know.
>> > > >
>> > > >
>> > > > @O

AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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 mavenizer status

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 set 
the "use-apache-gid" parameter to false or use Flexmojos 7.x and set it to 
true. 

Hope that clears up things a little :-)

Chris

-Ursprüngliche Nachricht-
Von: Toni Vega [mailto:toniveg...@gmail.com]
Gesendet: Dienstag, 19. November 2013 22:11
An: dev@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 change the 
property in the parent pom of Flexmojos to use "org.apache.flex" and it worked 
fine.


2013/11/19 Cosma Colanicchia 

> Yes, it worked as described in the README. What was your problem 
> exactly? I set the use-apache-gid parameter to false, because all of 
> my project are still using the old flexmojos versions
>
> Noticed now that the README.txt does not describe the use-apache-god 
> parameter, that is correctly reported in the wiki page.
>
>
> 2013/11/19 Toni Vega 
>
> > Did the param "fdktarget" work for you, Cosma? I remember I tried to 
> > configure that quite time ago but it didn't worked forme. I also 
> > remember that Christofer recomended me not to use "org.apache.flex"
> > package (Flexmojos 6 was still in development). This last time I 
> > tried it, I just changed the properties in Flexmojos parent pom. Thanks!
> >
> > Regards
> >
> >
> > 2013/11/19 Cosma Colanicchia 
> >
> > > @Christofer
> > >
> > > Thanks for the info, just some questions: when you say "win" 
> > > directory,
> > are
> > > you referring to the subfolders in runtimes/air and
> runtimes/air-captive?
> > > The SDK produced by the installer correctly contains the "mac"
> runtimes,
> > if
> > > I understand correctly I should be able to add the corresponding "win"
> > > folders (borrowing them from an SDK prepared by the installer on a
> > Windows
> > > machine?) and the mavenizer should pick up them producing 
> > > artifacts
> > usable
> > > from win and mac, am I right? I see that the bin directory already
> > contains
> > > windows batch file as well as bash scripts, so it should already 
> > > be cross-platform in this respect.
> > >
> > > I'll also try the in-vm deployer and let you know.
> > >
> > >
> > > @Om
> > >
> > > After a first look, it seems ok and very similar to the README.txt 
> > > contents. Maybe we could add some detail about the AIR SDK 
> > > requirement (that is actually not required with the latest Apache 
> > > Flex releases),
> and
> > > some words about the effect of running it from a specific platform 
> > > (mac/win). This is not a problem with the installer itself (it is 
> > > meant
> > to
> > > prepare an SDK for the user on its environment), but generally the 
> > > artifacts are prepared and deployed in order to be used by other 
> > > developers, so we should probably warn users about this.
> > >
> > > If we want to help out new users, we could try to provide a
> streamlined,
> > > step-by-step guide referred to the latest Apache Flex version, 
> > > along
> > with a
> > > convenience link to a compiled jar of the mavenizer tool and maybe 
> > > a bash/batch wrapper file. On the other hand, this could be 
> > > totally
> avoided
> > > if we plan to go ahead in managing the mavenizer from the installer.
> > >
> > >
> > > 2013/11/19 OmPrakash Muppirala 
> > >
> > > > On Tue, Nov 19, 2013 at 11:47 AM, christofer.d...@c-ware.de < 
> > > > christofer.d...@c-ware.de> wrote:
> > > >
> > > > > Hi Cosma,
> > > > >
> > > > > as Toni already confirmed, the mavenizer is currently the 
> > > > > easiest
> way
> > &g

AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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 at 11:47 AM, christofer.d...@c-ware.de < 
christofer.d...@c-ware.de> wrote:

> 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 
> Adobe Flex 2 up to 4.11. In order to be able to User newer Air 
> versions with older FDKs I added the ability to mavenize the Air SDKs 
> separately.
>
> I think I remember creating all the runtime archives for any platform 
> (Flashplayer or Air Runtime) found in the Flex SDK or the Air SDK. So 
> if the SDK contains a "win" dir, it creates the windows archive, if 
> lnx the ones for Linus and mac the ones for Macs.
>
> When deploying to your local maven repository, I would suggest to give 
> my new deployer a testdrive. It should be noticeably faster with 
> deploying the artifacts. (SDKInVMDeployer).
>
> Please don't start that dreaded "deploy flex to a public repo"-thread ...
> 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 definitely end in a support-mayhem because from my 
> experience on the Flexmojos Mailinglist (when it still existed) was 
> that people don't read documentation ;-)
>
> 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 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]
> Gesendet: Dienstag, 19. November 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 only way to do this for 4.11 is by mavenizing/deploying a 
> downloaded FDK, is this right? I was following the other thread about 
> storing ready-to-use artifacts in some public repository, but this 
> path doesn't seem ready yet (BTW, is there something I could do to 
> help in this
> effort?)
>
> I managed to successfully build and mavenize the FDK from develop 
> branch in some months ago, but I still have some questions:
>
> Q1 - I'm going to try running the mavenizer/deployer tools on the 
> output of the Apache Flex Installer in order to mavenize the released 
> 4.11 FDK, is this the intended way of using it?
>
> Q2 - the mavenizer requires the AIR runtime in a separate directory... 
> but the installer output should already have integrated it in the FDK, 
> should provide it separately anyway?
>
> Q3 - is the FDK produced by the installer cross-platform? This time 
> I'm using a Mac to run the installer, so it has probably downloaded 
> the Mac version of the AIR SDK.. does this mean that, when mavenizing 
> this SDK, the Windows binaries (e.g. adt command line tool) won't be 
> included in the SDK artifacts and the SDK won't be fully compatible 
> with developers on Windows machines?
>
>
> Thank you for any help
> Cosma
>

AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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 set 
the "use-apache-gid" parameter to false or use Flexmojos 7.x and set it to 
true. 

Hope that clears up things a little :-)

Chris

-Ursprüngliche Nachricht-
Von: Toni Vega [mailto:toniveg...@gmail.com] 
Gesendet: Dienstag, 19. November 2013 22:11
An: dev@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 change the 
property in the parent pom of Flexmojos to use "org.apache.flex" and it worked 
fine.


2013/11/19 Cosma Colanicchia 

> Yes, it worked as described in the README. What was your problem 
> exactly? I set the use-apache-gid parameter to false, because all of 
> my project are still using the old flexmojos versions
>
> Noticed now that the README.txt does not describe the use-apache-god 
> parameter, that is correctly reported in the wiki page.
>
>
> 2013/11/19 Toni Vega 
>
> > Did the param "fdktarget" work for you, Cosma? I remember I tried to 
> > configure that quite time ago but it didn't worked forme. I also 
> > remember that Christofer recomended me not to use "org.apache.flex" 
> > package (Flexmojos 6 was still in development). This last time I 
> > tried it, I just changed the properties in Flexmojos parent pom. Thanks!
> >
> > Regards
> >
> >
> > 2013/11/19 Cosma Colanicchia 
> >
> > > @Christofer
> > >
> > > Thanks for the info, just some questions: when you say "win" 
> > > directory,
> > are
> > > you referring to the subfolders in runtimes/air and
> runtimes/air-captive?
> > > The SDK produced by the installer correctly contains the "mac"
> runtimes,
> > if
> > > I understand correctly I should be able to add the corresponding "win"
> > > folders (borrowing them from an SDK prepared by the installer on a
> > Windows
> > > machine?) and the mavenizer should pick up them producing 
> > > artifacts
> > usable
> > > from win and mac, am I right? I see that the bin directory already
> > contains
> > > windows batch file as well as bash scripts, so it should already 
> > > be cross-platform in this respect.
> > >
> > > I'll also try the in-vm deployer and let you know.
> > >
> > >
> > > @Om
> > >
> > > After a first look, it seems ok and very similar to the README.txt 
> > > contents. Maybe we could add some detail about the AIR SDK 
> > > requirement (that is actually not required with the latest Apache 
> > > Flex releases),
> and
> > > some words about the effect of running it from a specific platform 
> > > (mac/win). This is not a problem with the installer itself (it is 
> > > meant
> > to
> > > prepare an SDK for the user on its environment), but generally the 
> > > artifacts are prepared and deployed in order to be used by other 
> > > developers, so we should probably warn users about this.
> > >
> > > If we want to help out new users, we could try to provide a
> streamlined,
> > > step-by-step guide referred to the latest Apache Flex version, 
> > > along
> > with a
> > > convenience link to a compiled jar of the mavenizer tool and maybe 
> > > a bash/batch wrapper file. On the other hand, this could be 
> > > totally
> avoided
> > > if we plan to go ahead in managing the mavenizer from the installer.
> > >
> > >
> > > 2013/11/19 OmPrakash Muppirala 
> > >
> > > > On Tue, Nov 19, 2013 at 11:47 AM, christofer.d...@c-ware.de < 
> > > > christofer.d...@c-ware.de> wrote:
> > > >
> > > > > 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
> > >

AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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 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" work for you, Cosma? I remember I tried to configure 
that quite time ago but it didn't worked forme. I also remember that Christofer 
recomended me not to use "org.apache.flex" package (Flexmojos 6 was still in 
development). This last time I tried it, I just changed the properties in 
Flexmojos parent pom. Thanks!

Regards


2013/11/19 Cosma Colanicchia 

> @Christofer
>
> Thanks for the info, just some questions: when you say "win" 
> directory, are you referring to the subfolders in runtimes/air and 
> runtimes/air-captive?
> The SDK produced by the installer correctly contains the "mac" 
> runtimes, if I understand correctly I should be able to add the corresponding 
> "win"
> folders (borrowing them from an SDK prepared by the installer on a 
> Windows
> machine?) and the mavenizer should pick up them producing artifacts 
> usable from win and mac, am I right? I see that the bin directory 
> already contains windows batch file as well as bash scripts, so it 
> should already be cross-platform in this respect.
>
> I'll also try the in-vm deployer and let you know.
>
>
> @Om
>
> After a first look, it seems ok and very similar to the README.txt 
> contents. Maybe we could add some detail about the AIR SDK requirement 
> (that is actually not required with the latest Apache Flex releases), 
> and some words about the effect of running it from a specific platform 
> (mac/win). This is not a problem with the installer itself (it is 
> meant to prepare an SDK for the user on its environment), but 
> generally the artifacts are prepared and deployed in order to be used 
> by other developers, so we should probably warn users about this.
>
> If we want to help out new users, we could try to provide a 
> streamlined, step-by-step guide referred to the latest Apache Flex 
> version, along with a convenience link to a compiled jar of the 
> mavenizer tool and maybe a bash/batch wrapper file. On the other hand, 
> this could be totally avoided if we plan to go ahead in managing the 
> mavenizer from the installer.
>
>
> 2013/11/19 OmPrakash Muppirala 
>
> > On Tue, Nov 19, 2013 at 11:47 AM, christofer.d...@c-ware.de < 
> > christofer.d...@c-ware.de> wrote:
> >
> > > 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 Adobe
> Flex 2
> > > up to 4.11. In order to be able to User newer Air versions with 
> > > older
> > FDKs
> > > I added the ability to mavenize the Air SDKs separately.
> > >
> > > I think I remember creating all the runtime archives for any 
> > > platform (Flashplayer or Air Runtime) found in the Flex SDK or the 
> > > Air SDK. So
> if
> > > the SDK contains a "win" dir, it creates the windows archive, if 
> > > lnx
> the
> > > ones for Linus and mac the ones for Macs.
> > >
> > > When deploying to your local maven repository, I would suggest to 
> > > give
> my
> > > new deployer a testdrive. It should be noticeably faster with 
> > > deploying
> > the
> > > artifacts. (SDKInVMDeployer).
> > >
> > > Please don't start that dreaded "deploy flex to a public 
> > > repo"-thread
> ...
> > > 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
> > definitely
> > > end in a support-mayhem because from my experience on the 
> > > Flexmojos Mailinglist (when it still existed) was that people 
> > > don't read documentation ;-)
> > >
> > > Chris
> > >

AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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 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 of my project are still 
using the old flexmojos versions

Noticed now that the README.txt does not describe the use-apache-god parameter, 
that is correctly reported in the wiki page.


2013/11/19 Toni Vega 

> Did the param "fdktarget" work for you, Cosma? I remember I tried to 
> configure that quite time ago but it didn't worked forme. I also 
> remember that Christofer recomended me not to use "org.apache.flex" 
> package (Flexmojos 6 was still in development). This last time I tried 
> it, I just changed the properties in Flexmojos parent pom. Thanks!
>
> Regards
>
>
> 2013/11/19 Cosma Colanicchia 
>
> > @Christofer
> >
> > Thanks for the info, just some questions: when you say “win” 
> > directory,
> are
> > you referring to the subfolders in runtimes/air and runtimes/air-captive?
> > The SDK produced by the installer correctly contains the “mac” 
> > runtimes,
> if
> > I understand correctly I should be able to add the corresponding “win”
> > folders (borrowing them from an SDK prepared by the installer on a
> Windows
> > machine?) and the mavenizer should pick up them producing artifacts
> usable
> > from win and mac, am I right? I see that the bin directory already
> contains
> > windows batch file as well as bash scripts, so it should already be 
> > cross-platform in this respect.
> >
> > I’ll also try the in-vm deployer and let you know.
> >
> >
> > @Om
> >
> > After a first look, it seems ok and very similar to the README.txt 
> > contents. Maybe we could add some detail about the AIR SDK 
> > requirement (that is actually not required with the latest Apache 
> > Flex releases), and some words about the effect of running it from a 
> > specific platform (mac/win). This is not a problem with the 
> > installer itself (it is meant
> to
> > prepare an SDK for the user on its environment), but generally the 
> > artifacts are prepared and deployed in order to be used by other 
> > developers, so we should probably warn users about this.
> >
> > If we want to help out new users, we could try to provide a 
> > streamlined, step-by-step guide referred to the latest Apache Flex 
> > version, along
> with a
> > convenience link to a compiled jar of the mavenizer tool and maybe a 
> > bash/batch wrapper file. On the other hand, this could be totally 
> > avoided if we plan to go ahead in managing the mavenizer from the installer.
> >
> >
> > 2013/11/19 OmPrakash Muppirala 
> >
> > > On Tue, Nov 19, 2013 at 11:47 AM, christofer.d...@c-ware.de < 
> > > christofer.d...@c-ware.de> wrote:
> > >
> > > > 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 
> > > > Adobe
> > Flex 2
> > > > up to 4.11. In order to be able to User newer Air versions with 
> > > > older
> > > FDKs
> > > > I added the ability to mavenize the Air SDKs separately.
> > > >
> > > > I think I remember creating all the runtime archives for any 
> > > > platform (Flashplayer or Air Runtime) found in the Flex SDK or 
> > > > the Air SDK. So
> > if
> > > > the SDK contains a "win" dir, it creates the windows archive, if 
> > > > lnx
> > the
> > > > ones for Linus and mac the ones for Macs.
> > > >
> > > > When deploying to your local maven repository, I would suggest 
> > > > to
> give
> > my
> > > > new deployer a testdrive. It should be noticeably faster with
> deploying
> > > the
> > > > artifacts. (SDKInVMDeployer).
> > > >
> > > > Please don’t start that dreaded "deploy flex to a public 
> > > > repo"-thread
> > ...
> > > &g

AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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/
{root}/runtimes/player/10.2/lnx
{root}/runtimes/player/10.2/mac
{root}/runtimes/player/10.2/win

Even if I didn't implement packaging of android, I think you get the Idea of 
what directory structure the mavenizer expects.
Eventually it could be an option to have some Advanced Settings in the SDK 
Download Tool to "also download other os runtimes". Then the Mavenizer would 
also package these.

Chris

-Ursprüngliche Nachricht-
Von: Cosma Colanicchia [mailto:cosma...@gmail.com] 
Gesendet: Dienstag, 19. November 2013 21:27
An: Apache Flex Developers ML
Betreff: Re: Questions about current mavenizer status

@Christofer

Thanks for the info, just some questions: when you say “win” directory, are you 
referring to the subfolders in runtimes/air and runtimes/air-captive?
The SDK produced by the installer correctly contains the “mac” runtimes, if I 
understand correctly I should be able to add the corresponding “win”
folders (borrowing them from an SDK prepared by the installer on a Windows
machine?) and the mavenizer should pick up them producing artifacts usable from 
win and mac, am I right? I see that the bin directory already contains windows 
batch file as well as bash scripts, so it should already be cross-platform in 
this respect.

I’ll also try the in-vm deployer and let you know.


@Om

After a first look, it seems ok and very similar to the README.txt contents. 
Maybe we could add some detail about the AIR SDK requirement (that is actually 
not required with the latest Apache Flex releases), and some words about the 
effect of running it from a specific platform (mac/win). This is not a problem 
with the installer itself (it is meant to prepare an SDK for the user on its 
environment), but generally the artifacts are prepared and deployed in order to 
be used by other developers, so we should probably warn users about this.

If we want to help out new users, we could try to provide a streamlined, 
step-by-step guide referred to the latest Apache Flex version, along with a 
convenience link to a compiled jar of the mavenizer tool and maybe a bash/batch 
wrapper file. On the other hand, this could be totally avoided if we plan to go 
ahead in managing the mavenizer from the installer.


2013/11/19 OmPrakash Muppirala 

> On Tue, Nov 19, 2013 at 11:47 AM, christofer.d...@c-ware.de < 
> christofer.d...@c-ware.de> wrote:
>
> > 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 
> > Adobe Flex 2 up to 4.11. In order to be able to User newer Air 
> > versions with older
> FDKs
> > I added the ability to mavenize the Air SDKs separately.
> >
> > I think I remember creating all the runtime archives for any 
> > platform (Flashplayer or Air Runtime) found in the Flex SDK or the 
> > Air SDK. So if the SDK contains a "win" dir, it creates the windows 
> > archive, if lnx the ones for Linus and mac the ones for Macs.
> >
> > When deploying to your local maven repository, I would suggest to 
> > give my new deployer a testdrive. It should be noticeably faster 
> > with deploying
> the
> > artifacts. (SDKInVMDeployer).
> >
> > Please don’t start that dreaded "deploy flex to a public repo"-thread ...
> > 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
> definitely
> > end in a support-mayhem because from my experience on the Flexmojos 
> > Mailinglist (when it still existed) was that people don't read 
> > documentation ;-)
> >
> > 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 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+Maven
> izer
>
>
>
> >
> > -Ursprüngliche Nachricht-
> > Von: Cosma Colanicchia [mailto:cosma...@gmail.c

AW: Questions about current mavenizer status

[christofer.d...@c-ware.de]

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 Adobe Flex 2 up to 
4.11. In order to be able to User newer Air versions with older FDKs I added 
the ability to mavenize the Air SDKs separately. 

I think I remember creating all the runtime archives for any platform 
(Flashplayer or Air Runtime) found in the Flex SDK or the Air SDK. So if the 
SDK contains a "win" dir, it creates the windows archive, if lnx the ones for 
Linus and mac the ones for Macs.

When deploying to your local maven repository, I would suggest to give my new 
deployer a testdrive. It should be noticeably faster with deploying the 
artifacts. (SDKInVMDeployer).

Please don’t start that dreaded "deploy flex to a public repo"-thread ... 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 definitely end in a 
support-mayhem because from my experience on the Flexmojos Mailinglist (when it 
still existed) was that people don't read documentation ;-)

Chris


-Ursprüngliche Nachricht-
Von: Cosma Colanicchia [mailto:cosma...@gmail.com] 
Gesendet: Dienstag, 19. November 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 only way to do this for 4.11 is by mavenizing/deploying a downloaded 
FDK, is this right? I was following the other thread about storing ready-to-use 
artifacts in some public repository, but this path doesn’t seem ready yet (BTW, 
is there something I could do to help in this
effort?)

I managed to successfully build and mavenize the FDK from develop branch in 
some months ago, but I still have some questions:

Q1 - I’m going to try running the mavenizer/deployer tools on the output of the 
Apache Flex Installer in order to mavenize the released 4.11 FDK, is this the 
intended way of using it?

Q2 - the mavenizer requires the AIR runtime in a separate directory... but the 
installer output should already have integrated it in the FDK, should provide 
it separately anyway?

Q3 - is the FDK produced by the installer cross-platform? This time I’m using a 
Mac to run the installer, so it has probably downloaded the Mac version of the 
AIR SDK.. does this mean that, when mavenizing this SDK, the Windows binaries 
(e.g. adt command line tool) won’t be included in the SDK artifacts and the SDK 
won’t be fully compatible with developers on Windows machines?


Thank you for any help
Cosma

AW: AW: How can I check if an swf has advanced-telemetry enabled?

[christofer.d...@c-ware.de]

Hi Alex,

thanks for that pointer. I guess SwfxPrinter seems to be exactly what I was 
looking for ... will give this a spin the next time I can free some time for 
Flexmojos :-)

Chris



Von: Alex Harui [aha...@adobe.com]
Gesendet: Montag, 18. November 2013 08:05
An: dev@flex.apache.org
Betreff: Re: AW: How can I check if an swf has advanced-telemetry enabled?

I don't think that's right.  The 4th byte is the SWF version.  The
enabling tool may have forced a newer SWF version, but that could happen
for other reasons.

I think you need to decode the SWF.  There are SWF decoding classes in
modules/swfutils/src/.  SWFDump just calls SwfxPrinter.java.

-Alex

On 11/17/13 10:50 PM, "christofer.d...@c-ware.de"
 wrote:

>Ok ... so I just had another look,
>- unpacked an swf that was not enabled
>- then enabled that SWF
>- unpacked that content
>- loaded both files in a text-compare tool
>
>So it seems that the difference is simplywithin the first 7 bytes
>Not Enabled: FWS0J+
>Enabed: FWS4J+
>(There seems to be some sort of line break after the FWS)
>So can I go and hunt for the one different byte to detect if a file is
>enabled?
>
>Chris
>
>-Ursprüngliche Nachricht-
>Von: Darrell Loverin [mailto:darrell.love...@gmail.com]
>Gesendet: Montag, 18. November 2013 02:18
>An: dev@flex.apache.org
>Betreff: Re: How can I check if an swf has advanced-telemetry enabled?
>
>Oh, I see, Justin added it to swfutils. I was looking for it in falcon
>since this is where I had added the support but I don't see the code in
>Apache Flex's falcon.
>
>
>-Darrell
>
>
>On Sun, Nov 17, 2013 at 3:46 PM, Justin Mclean
>wrote:
>
>> Hi,
>>
>> > I believe there was a new tag added to the swf to enable telemetry.
>> > I
>> don't
>> > see this tag supported in Apache Flex.
>>
>> The new tag in the swf is supported in Apache Flex (4.10 and 4.11)
>> otherwise how else could we support it?
>>
>> The tags value is 93, so you can look for that or just use swfdump, if
>> the swf has advanced telemetry turned on it will show this:
>> 
>>
>> Thanks,
>> Justin

AW: How can I check if an swf has advanced-telemetry enabled?

[christofer.d...@c-ware.de]

Ok ... so I just had another look, 
- unpacked an swf that was not enabled
- then enabled that SWF
- unpacked that content
- loaded both files in a text-compare tool

So it seems that the difference is simplywithin the first 7 bytes 
Not Enabled: FWS0J+
Enabed: FWS4J+ 
(There seems to be some sort of line break after the FWS)
So can I go and hunt for the one different byte to detect if a file is enabled?

Chris

-Ursprüngliche Nachricht-
Von: Darrell Loverin [mailto:darrell.love...@gmail.com] 
Gesendet: Montag, 18. November 2013 02:18
An: dev@flex.apache.org
Betreff: Re: How can I check if an swf has advanced-telemetry enabled?

Oh, I see, Justin added it to swfutils. I was looking for it in falcon since 
this is where I had added the support but I don't see the code in Apache Flex's 
falcon.


-Darrell


On Sun, Nov 17, 2013 at 3:46 PM, Justin Mclean wrote:

> Hi,
>
> > I believe there was a new tag added to the swf to enable telemetry. 
> > I
> don't
> > see this tag supported in Apache Flex.
>
> The new tag in the swf is supported in Apache Flex (4.10 and 4.11) 
> otherwise how else could we support it?
>
> The tags value is 93, so you can look for that or just use swfdump, if 
> the swf has advanced telemetry turned on it will show this:
> 
>
> Thanks,
> Justin

AW: How can I check if an swf has advanced-telemetry enabled?

[christofer.d...@c-ware.de]

Well I want to be able to detect programmatically, if advanced telemetry is 
tuned on. 
I agree, running that in Scout would prove its presence, but I want to check 
this in flexmojos testsuite.

@Darrell: As soon as I upgraded the FDK used by Flexmojos 7 to 4.10 this was 
the first compiler version that actually required me to support the 
advancedTelemerty flag. So currently 4.10 and 4.11 seem to be the ones that 
support that flag. Don't know however, if the compiler actually uses this... 
this is what I want to check. I know there is a Perl script and an enabler 
application that modifies SWFs, but having a look at this seemed confusing. So 
I was hoping for someone here on the list to simply say something like: "In 
order to enable an swf, the 4th byte has to be set to XYZ" ;-) 

Then checking this would be really easy.

Chris

-Ursprüngliche Nachricht-
Von: Avi Kessner [mailto:akess...@gmail.com] 
Gesendet: Sonntag, 17. November 2013 19:06
An: dev@flex.apache.org
Betreff: Re: How can I check if an swf has advanced-telemetry enabled?

Run scout?
On Nov 17, 2013 7:01 PM, "Darrell Loverin" 
wrote:

> I believe there was a new tag added to the swf to enable telemetry. I 
> don't see this tag supported in Apache Flex.
>
>
> -Darrell Loverin
>
>
>
> On Sun, Nov 17, 2013 at 8:30 AM, christofer.d...@c-ware.de < 
> christofer.d...@c-ware.de> wrote:
>
> > Hi,
> >
> > I have recently extedned Flexmojos to support the advanced telemetry 
> > compiler flag. Also I have created unit-tests that sort of test that 
> > functionality. Unfortunately I can simply see that below flex 4.10 
> > that flag is simply not supported by the compiler. I can't however 
> > check if
> the
> > file is actually enabled. So my question is, what is changed in a 
> > SWF in order to enable it so I can check this in a unit-test.
> >
> > Chris
> >
>

How can I check if an swf has advanced-telemetry enabled?

[christofer.d...@c-ware.de]

Hi,

I have recently extedned Flexmojos to support the advanced telemetry compiler 
flag. Also I have created unit-tests that sort of test that functionality. 
Unfortunately I can simply see that below flex 4.10 that flag is simply not 
supported by the compiler. I can't however check if the file is actually 
enabled. So my question is, what is changed in a SWF in order to enable it so I 
can check this in a unit-test.

Chris

AW: [FLEXJS] inheritance/interfaces

[christofer.d...@c-ware.de]

It's acutally pretty important that B also implements IA ... so an "instanceof" 
or "is" check should work as well as it should be possible to cast instaces A 
and B to IA.

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Donnerstag, 14. November 2013 17:58
An: dev@flex.apache.org
Betreff: [FLEXJS] inheritance/interfaces

Hi,

Quick question (too lazy to build an AS project to check):

If class B extends class A and class A implements interface IA, does
class B also implement IA? In other words, in this scenario, does (B
is IA) return true?

I'm asking, because org.apache.flex.utils.Language.is() currently
doesn't. If it should, that'll be my first thing... and I was sooo
close to solving the CSS thing ;-)

Thanks,

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

AW: Updated Mavenizer

[christofer.d...@c-ware.de]

I'm just using Aether for deploying mavenized FDKs so it has nothing to do with 
the actual execution of FM. So there shouldn't be a Problem.

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Dienstag, 5. November 2013 00:38
An: dev@flex.apache.org
Betreff: RE: Updated Mavenizer

Thanks Chris, sounds good, I don't have the time at the moment to look at
the code because of my work and I'm between Paris and London but will check
it as soon as I can, just a question, are you aware there is an issue with
FM and Aether running FM with maven 3.1.1 ? Should I raise an issue
somewhere ?

-Fred

-Message d'origine-----
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : dimanche 3 novembre 2013 16:00
À : dev@flex.apache.org
Objet : Updated Mavenizer

Hi,

today I committed some changes to the Mavenizer Tool.

Change 1 made sure all SDKs (Flex and Air) are processed in the right order
regarding the versions of the SDKs.

Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven to
deploy the Mavenized files as it uses Aether directly to deploy files
directly inside the VM, causing a dramatic speedup of the time needed to
deploy stuff as well as being able to execute without the reliance on an
already installed Maven system. This should make it easy to add the new
Deployer to any sort of installer.

Chris

AW: AW: Updated Mavenizer

[christofer.d...@c-ware.de]

Ok ... so I updated the class ... should work now :-)
Thanks for reporting this.

Chris

-Ursprüngliche Nachricht-
Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] 
Gesendet: Montag, 4. November 2013 16:07
An: dev@flex.apache.org
Betreff: AW: AW: Updated Mavenizer

Hi Piotr,

Having a look at the code and the exception, I find this error relatively 
strange. Googling a Little, I could see that Integer.compare was introduced in 
Java 1.7 ... think I'll overwork this to make the mavenizer work in 1.6 too.

For now changing the line in the exception to this:
return 
Integer.valueOf(versionSegments1.length).compareTo(versionSegments2.length);

should do the trick. Unfortunately I can't commit here at work and I'll have to 
do this this eavening.

Chris


Von: piotr.zarzycki [piotrzarzyck...@gmail.com]
Gesendet: Montag, 4. November 2013 15:07
An: dev@flex.apache.org
Betreff: Re: AW: Updated Mavenizer

Hi Christofer,

I'm getting exception when i try to generate FDK.

Exception in thread "main" java.lang.NoSuchMethodError:
java.lang.Integer.compare(II)I
at common.ConversionPlan$1.compare(ConversionPlan.java:29)
at common.ConversionPlan$1.compare(ConversionPlan.java:16)
at java.util.TreeMap.getEntryUsingComparator(Unknown Source)
at java.util.TreeMap.getEntry(Unknown Source)
at java.util.TreeMap.containsKey(Unknown Source)
at java.util.TreeSet.contains(Unknown Source)
at common.ConversionPlan.addVersion(ConversionPlan.java:38)
at SDKGenerator.buildAirConversionPlan(SDKGenerator.java:49)
at SDKGenerator.main(SDKGenerator.java:156)



-
Flex/Air developer open to new job offers and challenges.
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Updated-Mavenizer-tp31841p31882.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: AW: Updated Mavenizer

[christofer.d...@c-ware.de]

Hi Piotr,

Having a look at the code and the exception, I find this error relatively 
strange. Googling a Little, I could see that Integer.compare was introduced in 
Java 1.7 ... think I'll overwork this to make the mavenizer work in 1.6 too.

For now changing the line in the exception to this:
return 
Integer.valueOf(versionSegments1.length).compareTo(versionSegments2.length);

should do the trick. Unfortunately I can't commit here at work and I'll have to 
do this this eavening.

Chris


Von: piotr.zarzycki [piotrzarzyck...@gmail.com]
Gesendet: Montag, 4. November 2013 15:07
An: dev@flex.apache.org
Betreff: Re: AW: Updated Mavenizer

Hi Christofer,

I'm getting exception when i try to generate FDK.

Exception in thread "main" java.lang.NoSuchMethodError:
java.lang.Integer.compare(II)I
at common.ConversionPlan$1.compare(ConversionPlan.java:29)
at common.ConversionPlan$1.compare(ConversionPlan.java:16)
at java.util.TreeMap.getEntryUsingComparator(Unknown Source)
at java.util.TreeMap.getEntry(Unknown Source)
at java.util.TreeMap.containsKey(Unknown Source)
at java.util.TreeSet.contains(Unknown Source)
at common.ConversionPlan.addVersion(ConversionPlan.java:38)
at SDKGenerator.buildAirConversionPlan(SDKGenerator.java:49)
at SDKGenerator.main(SDKGenerator.java:156)



-
Flex/Air developer open to new job offers and challenges.
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Updated-Mavenizer-tp31841p31882.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

What's the difference between normal Air applications and ones targeted at the mobile platforms?

[christofer.d...@c-ware.de]

Hi,

sorry for this eventually stupid question, but I recently "remembered" that 
there were some issues with Flexmojos regarding building of Mobile 
applications. It seems the normal Flexmojos couldn't build Air applications for 
mobile devices. Unfortunately I have never built any mobile-air apps and 
therefore don't quite know what Flexmojos is currently missing. Is there some 
sort of post-processing needed to bundle the normal Air apps? If someone here 
could explain what's missing, I'd be glad to add that to FM. There must be 
something, cause Velo offered this feature in his commercial FM Enterprise.

Chris

AW: Updated Mavenizer

[christofer.d...@c-ware.de]

Hi Toni,

I haven't managed to fee enough time to successfully continue working on that 
plugin as my work situation has changed quite a bit so nut much progress here, 
but I have been making sure that we are able to work with Flexmojos 6.0.1, 
which should work nicely and the 7.x branch which I am intending on optimizing 
for Apache Flex and stripping out stuff related to Adobe Flex which is causing 
problems with Apache Flex (such as "caching/signed rsls").

Chris

-Ursprüngliche Nachricht-
Von: Toni Vega [mailto:toniveg...@gmail.com] 
Gesendet: Sonntag, 3. November 2013 16:17
An: dev@flex.apache.org
Betreff: Re: Updated Mavenizer

Hi Christofer,

Sorry if I'm a little bit disconnected but, which is the current state of the 
new maven-flex-plugin and when will it be released?

Thanks!


2013/11/3 christofer.d...@c-ware.de 

> Hi,
>
> today I committed some changes to the Mavenizer Tool.
>
> Change 1 made sure all SDKs (Flex and Air) are processed in the right 
> order regarding the versions of the SDKs.
>
> Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs 
> Maven to deploy the Mavenized files as it uses Aether directly to 
> deploy files directly inside the VM, causing a dramatic speedup of the 
> time needed to deploy stuff as well as being able to execute without 
> the reliance on an already installed Maven system. This should make it 
> easy to add the new Deployer to any sort of installer.
>
> Chris
>

Updated Mavenizer

[christofer.d...@c-ware.de]

Hi,

today I committed some changes to the Mavenizer Tool.

Change 1 made sure all SDKs (Flex and Air) are processed in the right order 
regarding the versions of the SDKs.

Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven to 
deploy the Mavenized files as it uses Aether directly to deploy files directly 
inside the VM, causing a dramatic speedup of the time needed to deploy stuff as 
well as being able to execute without the reliance on an already installed 
Maven system. This should make it easy to add the new Deployer to any sort of 
installer.

Chris

AW: License Stuff

[christofer.d...@c-ware.de]

Hi Frederic, 

but that's not quite true ... each maven repo has a root and relative to that 
the groupId, artifactId and version make up the relative path finished by the 
file name containing the artifactId, version and classifier.

In Flexmojos I handle the config.zip in a way that it is fetched as zip and 
extracted prior to the execution of the compiler. So it should be possible to 
fix up a zipped Air thingy and somehow handle that ... so if it's the problem 
"all or nothing" then we could handle this.

Chris



-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] 
Gesendet: Dienstag, 29. Oktober 2013 22:56
An: dev@flex.apache.org
Betreff: RE: License Stuff

> The FP SDK is just playerglobal.swc.  It is a single file so if there 
> was
a pom.xml next to it, would that be sufficient?

Thanks for make me recall again :-) yes, you're right it could be enough.

> AIR is a compressed tree of files.  There is an issue about the fact 
> that
the runtime is bundled, but otherwise, is there a capability in Maven to deal 
with compressed files that don't have the subfolders also populated with 
pom.xml and other files?  If not, what is the minimum set of changes we'd have 
to make to get an AIR SDK on the download server to work with Maven (skipping 
over the license acceptance issue for now).

Not sure and surely not easily otherwise all those subtrees [1]

-Fred

[1]
http://apacheflexvm.cloudapp.net/artifactory/simple/ext-release-local/com/ad
obe/air/

-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre 2013 22:46 
À : dev@flex.apache.org Objet : Re: License Stuff

Like I said, I don't know much about Maven.

IIRC, there was some thinking that, because the FP and AIR SDKs are the "leaf" 
of a dependency tree, there wasn't much more than a pom.xml needed.
 I believe I even looked at a few files on some Maven repo and that seemed to 
be the only major difference.  Have we since decided differently?

But let's also separate out FP, from AIR.

The FP SDK is just playerglobal.swc.  It is a single file so if there was a 
pom.xml next to it, would that be sufficient?  Would it be worth it if we only 
made non-AIR apps work well with Maven?

AIR is a compressed tree of files.  There is an issue about the fact that the 
runtime is bundled, but otherwise, is there a capability in Maven to deal with 
compressed files that don't have the subfolders also populated with pom.xml and 
other files?  If not, what is the minimum set of changes we'd have to make to 
get an AIR SDK on the download server to work with Maven (skipping over the 
license acceptance issue for now).

-Alex

On 10/29/13 2:37 PM, "Frédéric THOMAS"  wrote:

>I can't see how 1 or more pom.xml on their server could help Alex,  we 
>need artifacts and classifiers along with the project descriptor, I 
>mean trees entire mavenized SDKs. did I miss or forgot something again
>:-) ?
>
>-Fred
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre
>2013 22:32 À : dev@flex.apache.org Objet : Re: License Stuff
>
>Adobe did not want to deal with registration or a way to avoid the 
>license dialog, but I'm pretty sure we got permission to put up pom.xml 
>files on the current downloads server.
>
>On 10/29/13 2:29 PM, "Frédéric THOMAS"  wrote:
>
>>IIRC Adobe didn't want to invest in a server just for that.
>>
>>-Fred
>>
>>-Message d'origine-
>>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre
>>2013 22:20 À : dev@flex.apache.org Objet : Re: License Stuff
>>
>>
>>
>>On 10/29/13 2:14 PM, "Frédéric THOMAS"  wrote:
>>
>>>Also, I can retrieve it at the moment but when I read the specific 
>>>Air license terms, I understood it couldn't be distributed in piece 
>>>but only in only one full and original distribution.
>>Yes, that's probably true, and the runtimes are part of the SDK.  I 
>>don't think they make a distribution without the runtimes.
>>
>>Just to be sure, we once talked about Adobe putting pom.xml files on 
>>its downloads server.  Have we decided that is insufficient and a 
>>distribution agreement is better? Either way, there is some sort of a 
>>license acceptance requirement unless we can get an exemption.
>>
>>-Alex
>>
>

AW: License Stuff

[christofer.d...@c-ware.de]

It's not just the pom, but the directory structure and the naming of the file 
... so all of these would have to be adjusted.

Chris

-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com] 
Gesendet: Dienstag, 29. Oktober 2013 22:46
An: dev@flex.apache.org
Betreff: Re: License Stuff

Like I said, I don't know much about Maven.

IIRC, there was some thinking that, because the FP and AIR SDKs are the "leaf" 
of a dependency tree, there wasn't much more than a pom.xml needed.
 I believe I even looked at a few files on some Maven repo and that seemed to 
be the only major difference.  Have we since decided differently?

But let's also separate out FP, from AIR.

The FP SDK is just playerglobal.swc.  It is a single file so if there was a 
pom.xml next to it, would that be sufficient?  Would it be worth it if we only 
made non-AIR apps work well with Maven?

AIR is a compressed tree of files.  There is an issue about the fact that the 
runtime is bundled, but otherwise, is there a capability in Maven to deal with 
compressed files that don't have the subfolders also populated with pom.xml and 
other files?  If not, what is the minimum set of changes we'd have to make to 
get an AIR SDK on the download server to work with Maven (skipping over the 
license acceptance issue for now).

-Alex

On 10/29/13 2:37 PM, "Frédéric THOMAS"  wrote:

>I can't see how 1 or more pom.xml on their server could help Alex,  we 
>need artifacts and classifiers along with the project descriptor, I 
>mean trees entire mavenized SDKs. did I miss or forgot something again 
>:-) ?
>
>-Fred
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre 
>2013 22:32 À : dev@flex.apache.org Objet : Re: License Stuff
>
>Adobe did not want to deal with registration or a way to avoid the 
>license dialog, but I'm pretty sure we got permission to put up pom.xml 
>files on the current downloads server.
>
>On 10/29/13 2:29 PM, "Frédéric THOMAS"  wrote:
>
>>IIRC Adobe didn't want to invest in a server just for that.
>>
>>-Fred
>>
>>-Message d'origine-
>>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre
>>2013 22:20 À : dev@flex.apache.org Objet : Re: License Stuff
>>
>>
>>
>>On 10/29/13 2:14 PM, "Frédéric THOMAS"  wrote:
>>
>>>Also, I can retrieve it at the moment but when I read the specific 
>>>Air license terms, I understood it couldn't be distributed in piece 
>>>but only in only one full and original distribution.
>>Yes, that's probably true, and the runtimes are part of the SDK.  I 
>>don't think they make a distribution without the runtimes.
>>
>>Just to be sure, we once talked about Adobe putting pom.xml files on 
>>its downloads server.  Have we decided that is insufficient and a 
>>distribution agreement is better? Either way, there is some sort of a 
>>license acceptance requirement unless we can get an exemption.
>>
>>-Alex
>>
>

AW: AW: License Stuff

[christofer.d...@c-ware.de]

Well it seems the is nothing like that:
http://nexus.cestpasdur.com/nexus/content/repositories/sonatype-forge/com/adobe/flex/framework/playerglobal/4.6.b.23201/

As you can see, it's as easy as accessing the URL to download the playerglobal.

Chris

-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com] 
Gesendet: Dienstag, 29. Oktober 2013 21:31
An: dev@flex.apache.org
Betreff: Re: AW: License Stuff



On 10/29/13 1:13 PM, "christofer.d...@c-ware.de"
 wrote:

>But if the deal Velo and Sonatype had with Adobe was enough, I guess 
>this would be all we need and we wouldn't have the hassle of having to 
>implement any sort of manual deployment wrapper as I would really hate 
>having to implement any sort if "interactive" maven build.
The last time I talked with Adobe Legal, the distribution agreement is not 
enough.  Folks must be made aware of the terms and conditions before 
downloading.  So, while Sonatype had the rights to allow folks to download 
copies of Adobe software from Sonatype servers, someday, if Adobe Legal ever 
did a review, they would have been required to have some sort of way of 
ensuring that folks understood the licensing before allowing the download.

Does Sonatype have any such facility for doing that? Registered users with 
logins?
>
>Chris
>
>-Ursprüngliche Nachricht-
>Von: Alex Harui [mailto:aha...@adobe.com]
>Gesendet: Dienstag, 29. Oktober 2013 21:08
>An: dev@flex.apache.org
>Betreff: Re: License Stuff
>
>We did not pursue that approach because Apache supposedly only 
>distributes source code with open licenses.  Even if there was such an 
>agreement, the binary packages still could not contain Adobe stuff 
>because a binary package can only contain the compiled results of a 
>source package.
>
>I may still set up a simple "business" to distribute the same package 
>as Adobe 4.6 but a license acceptance will still be required which 
>AFAIK still poses a problem for Maven.
>
>Maybe we should add some license handling to Maven itself?
>
>-Alex
>
>On 10/29/13 12:53 PM, "Frédéric THOMAS"  wrote:
>
>>Not sure if it has been already asked but can't Apache  / Apache Flex 
>>sign a Distribution agreement ?
>>
>>-Message d'origine-
>>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre
>>2013 17:57 À : dev@flex.apache.org Objet : Re: License Stuff
>>
>>
>>
>>On 10/29/13 7:16 AM, "christofer.d...@c-ware.de"
>> wrote:
>>
>>>Hi Guys,
>>>
>>>I am currently talking to Brian Fox from Sonatype. He told me that 
>>>Sonatype signed a Distribution Agreement with Adobe had been signed 
>>>in 2008, but this has expired 2009, but it seems they are willing to 
>>>re-sign such an Agreement.
>>>
>>>For which parts would we Need an Agreement from Adobe? As far as I 
>>>know this would be the Flach Playerglobal and for Air the Airglobal 
>>>and related SWCs/RSLs is there anything else? Can a Distribution 
>>>Agreement be signed for all of the missing parts?
>>I believe you need the entire AIR SDK.  Well, maybe not the runtimes, 
>>but the packagers if you are going to support mobile output.
>>
>>>
>>>If we manage to sort this out, I guess There should be nothing else 
>>>preventing us from Publishing Flex SDKs without having to implement 
>>>any hacks. I guess this would help a lot of Flex users quite a lot.
>>In my last conversation with Adobe Legal, they still want folks to 
>>accept the license agreement once per company.  The distribution 
>>agreement only gives you the right to distribute, but folks still need 
>>to be aware that not every file is Apache-licensed.
>>
>>-Alex
>>
>

AW: License Stuff

[christofer.d...@c-ware.de]

Hi Frederic,

well whenever I do a Flexmojos Release, I have to deploy quite a lot of files. 
That was never really a problem.
I guess it should be possible to stage all the fdk files using the deployer 
after all it's nothing than an ordinary maven deploy. All that's different to 
an ordinary deply is that you have to deploy to a staging repo which you can 
test and as soon as all is good, you hit the "Go" button and the stuff is 
publically available at the Sonatype OSS repo and after some time artifacts are 
synced to Mavan Central.

Chris

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] 
Gesendet: Dienstag, 29. Oktober 2013 21:31
An: dev@flex.apache.org
Betreff: RE: License Stuff

Chris, I just had a look at the deployment process requires by Sonatype, 
something I did 2 years ago, so, I didn't remembered well, it was heavy and it 
was only one Flex Lib built by Maven.

How do you think we can deploy our not Maven built SDK artifacts in the 
Sonatype way ? can it accept a compress file as a bundle of all signed 
artifacts or something else ?

-Fred

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mardi 29 octobre 2013 21:14
À : dev@flex.apache.org
Objet : AW: License Stuff

But if the deal Velo and Sonatype had with Adobe was enough, I guess this would 
be all we need and we wouldn't have the hassle of having to implement any sort 
of manual deployment wrapper as I would really hate having to implement any 
sort if "interactive" maven build.

Chris

-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com]
Gesendet: Dienstag, 29. Oktober 2013 21:08
An: dev@flex.apache.org
Betreff: Re: License Stuff

We did not pursue that approach because Apache supposedly only distributes 
source code with open licenses.  Even if there was such an agreement, the 
binary packages still could not contain Adobe stuff because a binary package 
can only contain the compiled results of a source package.

I may still set up a simple "business" to distribute the same package as Adobe 
4.6 but a license acceptance will still be required which AFAIK still poses a 
problem for Maven.

Maybe we should add some license handling to Maven itself?

-Alex

On 10/29/13 12:53 PM, "Frédéric THOMAS"  wrote:

>Not sure if it has been already asked but can't Apache  / Apache Flex 
>sign a Distribution agreement ?
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre
>2013 17:57 À : dev@flex.apache.org Objet : Re: License Stuff
>
>
>
>On 10/29/13 7:16 AM, "christofer.d...@c-ware.de"
> wrote:
>
>>Hi Guys,
>>
>>I am currently talking to Brian Fox from Sonatype. He told me that 
>>Sonatype signed a Distribution Agreement with Adobe had been signed in 
>>2008, but this has expired 2009, but it seems they are willing to 
>>re-sign such an Agreement.
>>
>>For which parts would we Need an Agreement from Adobe? As far as I 
>>know this would be the Flach Playerglobal and for Air the Airglobal 
>>and related SWCs/RSLs is there anything else? Can a Distribution 
>>Agreement be signed for all of the missing parts?
>I believe you need the entire AIR SDK.  Well, maybe not the runtimes, 
>but the packagers if you are going to support mobile output.
>
>>
>>If we manage to sort this out, I guess There should be nothing else 
>>preventing us from Publishing Flex SDKs without having to implement 
>>any hacks. I guess this would help a lot of Flex users quite a lot.
>In my last conversation with Adobe Legal, they still want folks to 
>accept the license agreement once per company.  The distribution 
>agreement only gives you the right to distribute, but folks still need 
>to be aware that not every file is Apache-licensed.
>
>-Alex
>

AW: License Stuff

[christofer.d...@c-ware.de]

I gave Brian the Alex' contact. Hopefully Alex will be able to give him the 
contact he needs to sort this out.
It seems easy to ask for the permission to redistribute, but I doubt it will be 
that easy to actually receive the permission to do so .. so keep your fingers 
crossed.


Chris

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] 
Gesendet: Dienstag, 29. Oktober 2013 21:50
An: dev@flex.apache.org
Betreff: RE: License Stuff

> Looks like it is pretty easy to get a license.  Just ask here [1]

I meant in order to publicly distribute adobe artifacts, not only in a closed 
intranet environment as mentioned, I read that document last night and others 
too, I haven't see any talking about an agreement to allow public distribution 
of Air / FP, from the ones I read, only Adobe was allowed to distribute them 
publicly, the reason why I had liked a pointer on a such license agreement used 
by Sonatype and how to get it.

Thanks,
-Fred

-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre 2013 21:35 
À : dev@flex.apache.org Objet : Re: License Stuff



On 10/29/13 1:23 PM, "Frédéric THOMAS"  wrote:

>Thanks for reminding me, it was completely out of my head.
>
>> I may still set up a simple "business" to distribute the same package 
>> as
>Adobe 4.6 but a license acceptance will still be required which AFAIK 
>still poses a problem for Maven.
>
>The acceptance can be done thru the installer which in return gives a 
>credential to a Maven repo we could manage, maybe my limited company 
>could manage to ask an Adobe Distribution License, what's the requirements
?
Looks like it is pretty easy to get a license.  Just ask here [1]
>
>> Maybe we should add some license handling to Maven itself?
>
>I don't think it is possible to have an interactive process.
If Ant can ask a question, Maven should be able to as well.  And if there is
a server involved, it should be able to handle registration so you can skip
the interactive dialogs.  But that's just my opinion...

>
>-Fred
[1] http://www.adobe.com/products/players/flash-player-distribution.html

AW: License Stuff

[christofer.d...@c-ware.de]

It should be able, but it's not the usual way to go. Think about CI Servers ... 
how do you want to handle them?
I would like to keep the maven build as normal as possible.

Chris

-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com] 
Gesendet: Dienstag, 29. Oktober 2013 21:35
An: dev@flex.apache.org
Betreff: Re: License Stuff



On 10/29/13 1:23 PM, "Frédéric THOMAS"  wrote:

>Thanks for reminding me, it was completely out of my head.
>
>> I may still set up a simple "business" to distribute the same package 
>> as
>Adobe 4.6 but a license acceptance will still be required which AFAIK 
>still poses a problem for Maven.
>
>The acceptance can be done thru the installer which in return gives a 
>credential to a Maven repo we could manage, maybe my limited company 
>could manage to ask an Adobe Distribution License, what's the requirements ?
Looks like it is pretty easy to get a license.  Just ask here [1]
>
>> Maybe we should add some license handling to Maven itself?
>
>I don't think it is possible to have an interactive process.
If Ant can ask a question, Maven should be able to as well.  And if there is a 
server involved, it should be able to handle registration so you can skip the 
interactive dialogs.  But that's just my opinion...

>
>-Fred
[1] http://www.adobe.com/products/players/flash-player-distribution.html

AW: License Stuff

[christofer.d...@c-ware.de]

But if the deal Velo and Sonatype had with Adobe was enough, I guess this would 
be all we need and we wouldn't have the hassle of having to implement any sort 
of manual deployment wrapper as I would really hate having to implement any 
sort if "interactive" maven build.

Chris

-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com] 
Gesendet: Dienstag, 29. Oktober 2013 21:08
An: dev@flex.apache.org
Betreff: Re: License Stuff

We did not pursue that approach because Apache supposedly only distributes 
source code with open licenses.  Even if there was such an agreement, the 
binary packages still could not contain Adobe stuff because a binary package 
can only contain the compiled results of a source package.

I may still set up a simple "business" to distribute the same package as Adobe 
4.6 but a license acceptance will still be required which AFAIK still poses a 
problem for Maven.

Maybe we should add some license handling to Maven itself?

-Alex

On 10/29/13 12:53 PM, "Frédéric THOMAS"  wrote:

>Not sure if it has been already asked but can't Apache  / Apache Flex 
>sign a Distribution agreement ?
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre 
>2013 17:57 À : dev@flex.apache.org Objet : Re: License Stuff
>
>
>
>On 10/29/13 7:16 AM, "christofer.d...@c-ware.de"
> wrote:
>
>>Hi Guys,
>>
>>I am currently talking to Brian Fox from Sonatype. He told me that 
>>Sonatype signed a Distribution Agreement with Adobe had been signed in 
>>2008, but this has expired 2009, but it seems they are willing to 
>>re-sign such an Agreement.
>>
>>For which parts would we Need an Agreement from Adobe? As far as I 
>>know this would be the Flach Playerglobal and for Air the Airglobal 
>>and related SWCs/RSLs is there anything else? Can a Distribution 
>>Agreement be signed for all of the missing parts?
>I believe you need the entire AIR SDK.  Well, maybe not the runtimes, 
>but the packagers if you are going to support mobile output.
>
>>
>>If we manage to sort this out, I guess There should be nothing else 
>>preventing us from Publishing Flex SDKs without having to implement 
>>any hacks. I guess this would help a lot of Flex users quite a lot.
>In my last conversation with Adobe Legal, they still want folks to 
>accept the license agreement once per company.  The distribution 
>agreement only gives you the right to distribute, but folks still need 
>to be aware that not every file is Apache-licensed.
>
>-Alex
>

License Stuff

[christofer.d...@c-ware.de]

Hi Guys,

I am currently talking to Brian Fox from Sonatype. He told me that Sonatype 
signed a Distribution Agreement with Adobe had been signed in 2008, but this 
has expired 2009, but it seems they are willing to re-sign such an Agreement.

For which parts would we Need an Agreement from Adobe? As far as I know this 
would be the Flach Playerglobal and for Air the Airglobal and related SWCs/RSLs 
is there anything else? Can a Distribution Agreement be signed for all of the 
missing parts?

If we manage to sort this out, I guess There should be nothing else preventing 
us from Publishing Flex SDKs without having to implement any hacks. I guess 
this would help a lot of Flex users quite a lot.

Chris

AW: AW: AW: AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

Just got a Response: 

"Hi Chris, I will double check, but I am almost positive we signed this back 
when Marvin was actively maintaining flexmojos."

So this Looks extremely positive :-) *amreallyexitedaboutthis*


Von: Miguel Ferreira [miguel.cd.ferre...@hotmail.com]
Gesendet: Dienstag, 29. Oktober 2013 10:42
An: dev@flex.apache.org
Betreff: RE: AW: AW: AW: Add Mavenizer functionality to Installer

That will be perfect and really really useful.
Miguel

> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Date: Tue, 29 Oct 2013 10:17:26 +0100
> Subject: AW: AW: AW: Add Mavenizer functionality to Installer
>
> I just signed up to the Mailinglist and sent an inquiry ... let's see what 
> they answer. After all ... eventually they allready have signed an Agreement 
> as Velo used to deploy stuff there ...
>
> Chris
>
> 
> Von: Avi Kessner [akess...@gmail.com]
> Gesendet: Dienstag, 29. Oktober 2013 10:01
> An: dev@flex.apache.org
> Betreff: Re: AW: AW: Add Mavenizer functionality to Installer
>
> If I knew how/what, I would contact Sonotype.
>
> brought to you by the letters A, V, and I
> and the number 47
>
>
> On Tue, Oct 29, 2013 at 10:29 AM, christofer.d...@c-ware.de <
> christofer.d...@c-ware.de> wrote:
>
> > Well I doubt it would be possible to Setup protected Areas as this is in
> > contrast to the "public-repo" idea. But I would still prefer to have the
> > fdk deployed somewhere reliable. I know in our Business things Change quite
> > fast I wouldn't have immagined giving up my Consultant life and having a
> > full employment doing GWT stuff one year ago. But things have changed,
> > dramatically reducing the amount of time I have to develop the next Flex
> > Maven plugin (Sorry for that). I just want to prevent that one day a
> > posting Comes to this list, that the repo is offline because of whatsoever
> > reasons. As Sonatype is running Maven Central I doubt that they will go out
> > of Business soon, so for me it's currently the most reliable place in
> > Addition to the fact that it should work with any Maven Installation out of
> > the box.
> >
> > Chris
> >
> > 
> > Von: Frédéric THOMAS [webdoubl...@hotmail.com]
> > Gesendet: Montag, 28. Oktober 2013 19:48
> > An: dev@flex.apache.org
> > Betreff: RE: AW: AW: Add Mavenizer functionality to Installer
> >
> > > Well at sonatype they do distinguish between SNAPSHOT and Release
> > Versions. So the process of updating SNAPSHOTS is far less complicated than
> > that of deploying Releases
> >
> > Indeed but can I upload a zip instead of doing a deploy at sonatype? I
> > never
> > tried but actually, I wouldn't use the Deployer to do it, too consuming,
> > especially for nightly builds.
> > Can they / will create a single reader role for ApacheFlex to match the
> > license policy requirement we have ? You've probably got more experiences
> > with Sonatype and can probably surprise me.
> >
> > All in all, I prefer to keep control on the non-maven standard deploy
> > process instead of being under the umbrella of Sonatype, I can revise my
> > POV
> > if the answer to those 2 question is YES though :-)
> >
> > > But I still think that your process of creating individual users will
> > introduce some Problems (Settings.xml sharing)
> >
> > I can't see any other situations than the ones we have now, as explained
> > before, today a user from the Adobe site, once accepted the license and
> > downloaded an artifact can easily share it with no problems, idem from what
> > the installer download, the same if I authorize a user (or a company) to
> > download the SDK artifacts to its local/company repo after he accepted the
> > licenses from the Installer (with the advantage here that a same artifact
> > will be downloaded only once).
> >
> > Note: The actual license agreement is not nominative, so, I wasn't thinking
> > about 1 credential per user but 1 credential for the accepted license
> > agreement to match the same idea.
> >
> > Maybe there are situations I didn't considerate yet ?
> >
> > > Nevertheless ... I think I should make Flexmojos use the Apache GID ... I
> > doubt I will find the time to work much on the new plugin in the near
> > future
> > and I would like to have promote the Apachiness of Flex ;-)
> >
> > I would wait for FM-Next, I wouldn't like to waste my time to re-mavenize
> > and re-

AW: AW: AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

I just signed up to the Mailinglist and sent an inquiry ... let's see what they 
answer. After all ... eventually they allready have signed an Agreement as Velo 
used to deploy stuff there ...

Chris


Von: Avi Kessner [akess...@gmail.com]
Gesendet: Dienstag, 29. Oktober 2013 10:01
An: dev@flex.apache.org
Betreff: Re: AW: AW: Add Mavenizer functionality to Installer

If I knew how/what, I would contact Sonotype.

brought to you by the letters A, V, and I
and the number 47


On Tue, Oct 29, 2013 at 10:29 AM, christofer.d...@c-ware.de <
christofer.d...@c-ware.de> wrote:

> Well I doubt it would be possible to Setup protected Areas as this is in
> contrast to the "public-repo" idea. But I would still prefer to have the
> fdk deployed somewhere reliable. I know in our Business things Change quite
> fast I wouldn't have immagined giving up my Consultant life and having a
> full employment doing GWT stuff one year ago. But things have changed,
> dramatically reducing the amount of time I have to develop the next Flex
> Maven plugin (Sorry for that). I just want to prevent that one day a
> posting Comes to this list, that the repo is offline because of whatsoever
> reasons. As Sonatype is running Maven Central I doubt that they will go out
> of Business soon, so for me it's currently the most reliable place in
> Addition to the fact that it should work with any Maven Installation out of
> the box.
>
> Chris
>
> 
> Von: Frédéric THOMAS [webdoubl...@hotmail.com]
> Gesendet: Montag, 28. Oktober 2013 19:48
> An: dev@flex.apache.org
> Betreff: RE: AW: AW: Add Mavenizer functionality to Installer
>
> > Well at sonatype they do distinguish between SNAPSHOT and Release
> Versions. So the process of updating SNAPSHOTS is far less complicated than
> that of deploying Releases
>
> Indeed but can I upload a zip instead of doing a deploy at sonatype? I
> never
> tried but actually, I wouldn't use the Deployer to do it, too consuming,
> especially for nightly builds.
> Can they / will create a single reader role for ApacheFlex to match the
> license policy requirement we have ? You've probably got more experiences
> with Sonatype and can probably surprise me.
>
> All in all, I prefer to keep control on the non-maven standard deploy
> process instead of being under the umbrella of Sonatype, I can revise my
> POV
> if the answer to those 2 question is YES though :-)
>
> > But I still think that your process of creating individual users will
> introduce some Problems (Settings.xml sharing)
>
> I can't see any other situations than the ones we have now, as explained
> before, today a user from the Adobe site, once accepted the license and
> downloaded an artifact can easily share it with no problems, idem from what
> the installer download, the same if I authorize a user (or a company) to
> download the SDK artifacts to its local/company repo after he accepted the
> licenses from the Installer (with the advantage here that a same artifact
> will be downloaded only once).
>
> Note: The actual license agreement is not nominative, so, I wasn't thinking
> about 1 credential per user but 1 credential for the accepted license
> agreement to match the same idea.
>
> Maybe there are situations I didn't considerate yet ?
>
> > Nevertheless ... I think I should make Flexmojos use the Apache GID ... I
> doubt I will find the time to work much on the new plugin in the near
> future
> and I would like to have promote the Apachiness of Flex ;-)
>
> I would wait for FM-Next, I wouldn't like to waste my time to re-mavenize
> and re-deploy all the Flex/Air SDKs even if in case you do it, I will ;-)
>
> Thanks,
> -Fred
>
> -Message d'origine-
> De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> Envoyé : lundi 28 octobre 2013 16:22
> À : dev@flex.apache.org
> Objet : AW: AW: AW: Add Mavenizer functionality to Installer
>
> Well at sonatype they do distinguish between SNAPSHOT and Release Versions.
> So the process of updating SNAPSHOTS is far less complicated than that of
> deploying Releases. But I still think that your process of creating
> individual users will introduce some Problems (Settings.xml sharing)
>
> Nevertheless ... I think I should make Flexmojos use the Apache GID ... I
> doubt I will find the time to work much on the new plugin in the near
> future
> and I would like to have promote the Apachiness of Flex ;-)
>
> Chris
>
> 
> Von: Frédéric THOMAS [webdoubl...@hotmail.com]
> Gesendet: Montag, 28. Oktober 2013 16:07
> An: dev@flex.apache.org
> Betreff:

AW: AW: AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

Well I doubt it would be possible to Setup protected Areas as this is in 
contrast to the "public-repo" idea. But I would still prefer to have the fdk 
deployed somewhere reliable. I know in our Business things Change quite fast I 
wouldn't have immagined giving up my Consultant life and having a full 
employment doing GWT stuff one year ago. But things have changed, dramatically 
reducing the amount of time I have to develop the next Flex Maven plugin (Sorry 
for that). I just want to prevent that one day a posting Comes to this list, 
that the repo is offline because of whatsoever reasons. As Sonatype is running 
Maven Central I doubt that they will go out of Business soon, so for me it's 
currently the most reliable place in Addition to the fact that it should work 
with any Maven Installation out of the box.

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 19:48
An: dev@flex.apache.org
Betreff: RE: AW: AW: Add Mavenizer functionality to Installer

> Well at sonatype they do distinguish between SNAPSHOT and Release
Versions. So the process of updating SNAPSHOTS is far less complicated than
that of deploying Releases

Indeed but can I upload a zip instead of doing a deploy at sonatype? I never
tried but actually, I wouldn't use the Deployer to do it, too consuming,
especially for nightly builds.
Can they / will create a single reader role for ApacheFlex to match the
license policy requirement we have ? You've probably got more experiences
with Sonatype and can probably surprise me.

All in all, I prefer to keep control on the non-maven standard deploy
process instead of being under the umbrella of Sonatype, I can revise my POV
if the answer to those 2 question is YES though :-)

> But I still think that your process of creating individual users will
introduce some Problems (Settings.xml sharing)

I can't see any other situations than the ones we have now, as explained
before, today a user from the Adobe site, once accepted the license and
downloaded an artifact can easily share it with no problems, idem from what
the installer download, the same if I authorize a user (or a company) to
download the SDK artifacts to its local/company repo after he accepted the
licenses from the Installer (with the advantage here that a same artifact
will be downloaded only once).

Note: The actual license agreement is not nominative, so, I wasn't thinking
about 1 credential per user but 1 credential for the accepted license
agreement to match the same idea.

Maybe there are situations I didn't considerate yet ?

> Nevertheless ... I think I should make Flexmojos use the Apache GID ... I
doubt I will find the time to work much on the new plugin in the near future
and I would like to have promote the Apachiness of Flex ;-)

I would wait for FM-Next, I wouldn't like to waste my time to re-mavenize
and re-deploy all the Flex/Air SDKs even if in case you do it, I will ;-)

Thanks,
-Fred

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : lundi 28 octobre 2013 16:22
À : dev@flex.apache.org
Objet : AW: AW: AW: Add Mavenizer functionality to Installer

Well at sonatype they do distinguish between SNAPSHOT and Release Versions.
So the process of updating SNAPSHOTS is far less complicated than that of
deploying Releases. But I still think that your process of creating
individual users will introduce some Problems (Settings.xml sharing)

Nevertheless ... I think I should make Flexmojos use the Apache GID ... I
doubt I will find the time to work much on the new plugin in the near future
and I would like to have promote the Apachiness of Flex ;-)

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 16:07
An: dev@flex.apache.org
Betreff: RE: AW: AW: Add Mavenizer functionality to Installer

Chris,

Do you think Sonatype would allows the creation of specific user granted to
download the SDK ? It would be nice but I'm not sure, plus I would need to
deal with their heavy process to deal with snapshot and release on non-maven
built projects, I don't today, I just upload a zip and tomorrow, I will just
tell jenkins to deploy the build (mavenized SDK) to Artifactory, not sure it
is as easy as that with sonatype, at least from what I remember.

What do you think ?

Frédéric THOMAS

> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Date: Mon, 28 Oct 2013 14:18:50 +0100
> Subject: AW: AW: Add Mavenizer functionality to Installer
>
> Well in that case, I would opt for creating an Apache Flex account at
sonatype and to Stage and Deploy stuff there ... (The way Velo did it) ... I
guess there is legally no real difference between a Company repo and the big
sonatype repo. Actually we don't have permission to publish stuff in either
s

AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

Hi,

So what would it take for Sonatype to gain such a Distribution license from 
Adobe? As far as I see, we actually only Need it for the playerglobal and 
airglobal (Please correct me if I'm wrong). At least the number of artifacts 
should be minimal and it would allow us to officially deploy the FDKs on the 
Sonytypes Maven repo (and effectively also Maven Central). Eventually Sonatype 
allready have such a license, as they hosted Adobe artifacts in the past.

What do you think? Should I contact Sonatype for this?

Chris




Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Montag, 28. Oktober 2013 23:46
An: dev@flex.apache.org
Betreff: Re: Add Mavenizer functionality to Installer

Hi,

> Until now, the problem was we couldn't host the SDK in a public repo because
> it would let those who download it, to download the third-party as well
> without accept the Adobe licenses

Hate to say this but but just because you accept the licences doesn't mean you 
can host the binaries publicly or download them from elsewhere.

To host the binaries somewhere you need a distribution license from Adobe for 
their parts.

Thanks,
Justin

AW: AW: AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

Well at sonatype they do distinguish between SNAPSHOT and Release Versions. So 
the process of updating SNAPSHOTS is far less complicated than that of 
deploying Releases. But I still think that your process of creating individual 
users will introduce some Problems (Settings.xml sharing)

Nevertheless ... I think I should make Flexmojos use the Apache GID ... I doubt 
I will find the time to work much on the new plugin in the near future and I 
would like to have promote the Apachiness of Flex ;-)

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 16:07
An: dev@flex.apache.org
Betreff: RE: AW: AW: Add Mavenizer functionality to Installer

Chris,

Do you think Sonatype would allows the creation of specific user granted to 
download the SDK ? It would be nice but I'm not sure, plus I would need to deal 
with their heavy process to deal with snapshot and release on non-maven built 
projects, I don't today, I just upload a zip and tomorrow, I will just tell 
jenkins to deploy the build (mavenized SDK) to Artifactory, not sure it is as 
easy as that with sonatype, at least from what I remember.

What do you think ?

Frédéric THOMAS

> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Date: Mon, 28 Oct 2013 14:18:50 +0100
> Subject: AW: AW: Add Mavenizer functionality to Installer
>
> Well in that case, I would opt for creating an Apache Flex account at 
> sonatype and to Stage and Deploy stuff there ... (The way Velo did it) ... I 
> guess there is legally no real difference between a Company repo and the big 
> sonatype repo. Actually we don't have permission to publish stuff in either 
> solution.
>
> This is also where I deploy the Flexmojos Libs as well as I helped deploy the 
> latest FlexUnit release.
>
> On the cool side this is probably allready in the list of allmost all Major 
> Nexus/Artifactory/Whatsoever instances and therefore there would probably not 
> be any Problems with accessing the artifacts. But if such an Approach would 
> be taken, I guess I would create a new Major Version of Flexmojos, which runs 
> on Apache Flex's GID org.apache.flex instead of the current com.adobe.flex.
>
> Chris
>
> 
> Von: Frédéric THOMAS [webdoubl...@hotmail.com]
> Gesendet: Montag, 28. Oktober 2013 13:42
> An: dev@flex.apache.org
> Betreff: RE: AW: Add Mavenizer functionality to Installer
>
> You're right, that's my exp too but from the company I'm working for at the 
> moment, this is the only way as the installer doesn't work from here plus,I 
> don't think an ApacheFlex VM managed by PMCs and almost dedicated to it will 
> be "no-name" for long time :-)
>
> Frédéric THOMAS
>
> > From: christofer.d...@c-ware.de
> > To: dev@flex.apache.org
> > Date: Mon, 28 Oct 2013 12:18:48 +0100
> > Subject: AW: Add Mavenizer functionality to Installer
> >
> > But from my experiance it is usually more difficult to convince the 
> > Company-Repo admins to add a "no-name" repo as source. At least most of the 
> > companies I've worked for. And deploying of a new Flex Version would 
> > probably not be done by any ordinary developer, but by one Special Person 
> > that is permitted to do so.
> >
> > Chris
> >
> > 
> > Von: Frédéric THOMAS [webdoubl...@hotmail.com]
> > Gesendet: Montag, 28. Oktober 2013 10:53
> > An: dev@flex.apache.org
> > Betreff: RE: Add Mavenizer functionality to Installer
> >
> > 1- I'm short of time at the moment and that's a long run even without
> > thinking to integrate with the actual code
> > 2- Anyway, before I integrate anything in the actual code of the installer,
> > its code needs to be refactored
> > 3- There's no jar produced at the moment for the converter, that something
> > to be considered too.
> > 4- It's not allowed in every company the user can manage the repo he wants
> > to access, in big ones, he has to go by the company one which in return,
> > proxied the repo they choose.
> >
> > -Fred
> >
> > -Message d'origine-
> > De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> > Envoyé : lundi 28 octobre 2013 10:43
> > À : dev@flex.apache.org
> > Objet : AW: Add Mavenizer functionality to Installer
> >
> > Still I can't really see what would be the Problem to add the mavenizer to
> > the Installer? I guess this would resolve any legal Problems. I do see some
> > Major Speed improvement Option to Switch the Deployer to use Mavens wagon
> > instead of ma

AW: AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

Well in that case, I would opt for creating an Apache Flex account at sonatype 
and to Stage and Deploy stuff there ... (The way Velo did it) ... I guess there 
is legally no real difference between a Company repo and the big sonatype repo. 
Actually we don't have permission to publish stuff in either solution.

This is also where I deploy the Flexmojos Libs as well as I helped deploy the 
latest FlexUnit release. 

On the cool side this is probably allready in the list of allmost all Major 
Nexus/Artifactory/Whatsoever instances and therefore there would probably not 
be any Problems with accessing the artifacts. But if such an Approach would be 
taken, I guess I would create a new Major Version of Flexmojos, which runs on 
Apache Flex's GID org.apache.flex instead of the current com.adobe.flex.

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 13:42
An: dev@flex.apache.org
Betreff: RE: AW: Add Mavenizer functionality to Installer

You're right, that's my exp too but from the company I'm working for at the 
moment, this is the only way as the installer doesn't work from here plus,I 
don't think an ApacheFlex VM managed by PMCs and almost dedicated to it will be 
"no-name" for long time :-)

Frédéric THOMAS

> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Date: Mon, 28 Oct 2013 12:18:48 +0100
> Subject: AW: Add Mavenizer functionality to Installer
>
> But from my experiance it is usually more difficult to convince the 
> Company-Repo admins to add a "no-name" repo as source. At least most of the 
> companies I've worked for. And deploying of a new Flex Version would probably 
> not be done by any ordinary developer, but by one Special Person that is 
> permitted to do so.
>
> Chris
>
> 
> Von: Frédéric THOMAS [webdoubl...@hotmail.com]
> Gesendet: Montag, 28. Oktober 2013 10:53
> An: dev@flex.apache.org
> Betreff: RE: Add Mavenizer functionality to Installer
>
> 1- I'm short of time at the moment and that's a long run even without
> thinking to integrate with the actual code
> 2- Anyway, before I integrate anything in the actual code of the installer,
> its code needs to be refactored
> 3- There's no jar produced at the moment for the converter, that something
> to be considered too.
> 4- It's not allowed in every company the user can manage the repo he wants
> to access, in big ones, he has to go by the company one which in return,
> proxied the repo they choose.
>
> -Fred
>
> -Message d'origine-
> De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> Envoyé : lundi 28 octobre 2013 10:43
> À : dev@flex.apache.org
> Objet : AW: Add Mavenizer functionality to Installer
>
> Still I can't really see what would be the Problem to add the mavenizer to
> the Installer? I guess this would resolve any legal Problems. I do see some
> Major Speed improvement Option to Switch the Deployer to use Mavens wagon
> instead of making hundreds of mvn-calls, but adding the mavenizer to the
> installer still seems to be the best Option from my Point of view.
>
> Chris
>
> 
> Von: Frédéric THOMAS [webdoubl...@hotmail.com]
> Gesendet: Montag, 28. Oktober 2013 10:17
> An: dev@flex.apache.org
> Betreff: RE: Add Mavenizer functionality to Installer
>
> Hi Justin,
>
> >What to stop users sharing that URL and/or user credentials around?
>
> I thought about it too and ended to think I don't want to add more
> restrictions than what exists today, I mean today, once you accepted a
> license and downloaded an Adobe Artifact, you can share it as you like,
> that's not even nominative.
> I just want to replicate the actual security, so, yes, if an user wants to
> share the credentials, it can do it, as it can do it with the artifact
> itself.
>
> > As long as you make it clear that these are not official releases and
> > for
> development use only as per Apache policy.
>
> Np, it will be suffixed with "-SNAPSHOT " with means in Maven, non-released
>
> > Could it cope with it load and the costs that is likely to incur
> > (assume
> 100 or 200 installs a day)? Who owns and maintains the server? Could the
> apache Flex PMC be given access to it?
>
> From what I understand, I'm not charged or should be very low rate, I will
> verify anyway, can't do it now, windowsazure has a 401.
> I own and maintain the server, it is the same kind than the Erik ones, it
> will serve me for some of my devs too (probably) or / and to test the SDK
> RCs and I can give access to PMCs who ask me.
>
&

AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

But from my experiance it is usually more difficult to convince the 
Company-Repo admins to add a "no-name" repo as source. At least most of the 
companies I've worked for. And deploying of a new Flex Version would probably 
not be done by any ordinary developer, but by one Special Person that is 
permitted to do so.

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 10:53
An: dev@flex.apache.org
Betreff: RE: Add Mavenizer functionality to Installer

1- I'm short of time at the moment and that's a long run even without
thinking to integrate with the actual code
2- Anyway, before I integrate anything in the actual code of the installer,
its code needs to be refactored
3- There's no jar produced at the moment for the converter, that something
to be considered too.
4- It's not allowed in every company the user can manage the repo he wants
to access, in big ones, he has to go by the company one which in return,
proxied the repo they choose.

-Fred

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : lundi 28 octobre 2013 10:43
À : dev@flex.apache.org
Objet : AW: Add Mavenizer functionality to Installer

Still I can't really see what would be the Problem to add the mavenizer to
the Installer? I guess this would resolve any legal Problems. I do see some
Major Speed improvement Option to Switch the Deployer to use Mavens wagon
instead of making hundreds of mvn-calls, but adding the mavenizer to the
installer still seems to be the best Option from my Point of view.

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 10:17
An: dev@flex.apache.org
Betreff: RE: Add Mavenizer functionality to Installer

Hi Justin,

>What to stop users sharing that URL and/or user credentials around?

I thought about it too and ended to think I don't want to add more
restrictions than what exists today, I mean today, once you accepted a
license and downloaded an Adobe Artifact, you can share it as you like,
that's not even nominative.
I just want to replicate the actual security, so, yes, if an user wants to
share the credentials, it can do it, as it can do it with the artifact
itself.

> As long as you make it clear that these are not official releases and
> for
development use only as per Apache policy.

Np, it will be suffixed with "-SNAPSHOT " with means in Maven, non-released

> Could it cope with it load and the costs that is likely to incur
> (assume
100 or 200 installs a day)? Who owns and maintains the server? Could the
apache Flex PMC be given access to it?

>From what I understand, I'm not charged or should be very low rate, I will
verify anyway, can't do it now, windowsazure has a 401.
I own and maintain the server, it is the same kind than the Erik ones, it
will serve me for some of my devs too (probably) or / and to test the SDK
RCs and I can give access to PMCs who ask me.

Thanks,
-Fred

-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 28
octobre 2013 10:03 À : dev@flex.apache.org Objet : Re: Add Mavenizer
functionality to Installer

Hi,

> From the Installer, users already have to accept licenses for the
> third party artifacts, for those users I can grant access to a online
> maven repo which serves the Mavenized SDKs
What to stop users sharing that URL and/or user credentials around?

> I can even add the lasts nightly mavenized build versions.
As long as you make it clear that these are not official releases and for
development use only as per Apache policy.

> The server exist today as it serves me, it serves up to the 4.11
> version
Could it cope with it load and the costs that is likely to incur (assume 100
or 200 installs a day)? Who owns and maintains the server? Could the apache
Flex PMC be given access to it?

Thanks,
Justin

AW: Flex SDK 4.10: RSL URLs in flex-config.xml do not match file in framework/rsls/

[christofer.d...@c-ware.de]

Well I remember that I pack up everything in the FDK Directory (leaving away 
some stuff) and provide this zip. I also know that in FM this zip is important 
and it is used. I guess the Flex-config.xml is probably used as I guess this is 
the central Piece of Information in the zip.

I will have a look ad FMs code when I'm home (Hoping I won't forgett ;-))

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 11:00
An: dev@flex.apache.org
Betreff: RE: Flex SDK 4.10: RSL URLs in flex-config.xml do not match file in 
framework/rsls/

Just checked you are correct :(

Note: It doesn't seem to affect the mavenized sdk.
@Alex, @Chris, does IJ or FM uses the flex-config.xml from the config zip in
some way ?

-Fred

-Message d'origine-
De : Alexander Doroshko [mailto:alexander.doros...@jetbrains.com]
Envoyé : lundi 28 octobre 2013 10:27
À : dev@flex.apache.org
Objet : Re: Flex SDK 4.10: RSL URLs in flex-config.xml do not match file in
framework/rsls/

I'm sorry for such a late report, but the issue is still there in 4.11
release (4.11.0.20131017).
flex-config.xml contains invalid names like
framework_4.11.0.0.swf

On 09.08.2013 15:11, Justin Mclean wrote:
> Hi,
>
> Fixed and checked in.
> https://github.com/apache/flex-sdk/commit/9f3efa46684bf26381b3e9cb355b
> ff61a013c8e6#build.xml
>
> The question now is do we:
> 1) Make a new point release.
> 2) Document this somewhere including a corrected flex config file to
download.
> 3) Write a script to correct bad config files out there.
>
> Justin

AW: Add Mavenizer functionality to Installer

[christofer.d...@c-ware.de]

Still I can't really see what would be the Problem to add the mavenizer to the 
Installer? I guess this would resolve any legal Problems. I do see some Major 
Speed improvement Option to Switch the Deployer to use Mavens wagon instead of 
making hundreds of mvn-calls, but adding the mavenizer to the installer still 
seems to be the best Option from my Point of view.

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 28. Oktober 2013 10:17
An: dev@flex.apache.org
Betreff: RE: Add Mavenizer functionality to Installer

Hi Justin,

>What to stop users sharing that URL and/or user credentials around?

I thought about it too and ended to think I don't want to add more
restrictions than what exists today, I mean today, once you accepted a
license and downloaded an Adobe Artifact, you can share it as you like,
that's not even nominative.
I just want to replicate the actual security, so, yes, if an user wants to
share the credentials, it can do it, as it can do it with the artifact
itself.

> As long as you make it clear that these are not official releases and for
development use only as per Apache policy.

Np, it will be suffixed with "-SNAPSHOT " with means in Maven, non-released

> Could it cope with it load and the costs that is likely to incur (assume
100 or 200 installs a day)? Who owns and maintains the server? Could the
apache Flex PMC be given access to it?

>From what I understand, I'm not charged or should be very low rate, I will
verify anyway, can't do it now, windowsazure has a 401.
I own and maintain the server, it is the same kind than the Erik ones, it
will serve me for some of my devs too (probably) or / and to test the SDK
RCs and I can give access to PMCs who ask me.

Thanks,
-Fred

-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : lundi 28 octobre 2013 10:03
À : dev@flex.apache.org
Objet : Re: Add Mavenizer functionality to Installer

Hi,

> From the Installer, users already have to accept licenses for the
> third party artifacts, for those users I can grant access to a online
> maven repo which serves the Mavenized SDKs
What to stop users sharing that URL and/or user credentials around?

> I can even add the lasts nightly mavenized build versions.
As long as you make it clear that these are not official releases and for
development use only as per Apache policy.

> The server exist today as it serves me, it serves up to the 4.11
> version
Could it cope with it load and the costs that is likely to incur (assume 100
or 200 installs a day)? Who owns and maintains the server? Could the apache
Flex PMC be given access to it?

Thanks,
Justin

AW: How to create generic skins, manage layouts and manage views for multiple clients in flex application?

[christofer.d...@c-ware.de]

Hi, 

Well I use the Approach described by Justin not only for providing different 
Looks for different Customers, but also for delivering different Skin SWFs for 
different Client types: Destop, Destkop-Low-Res, Mobile, Tablet. Depending on 
the type of Client, my application loads different SWF modules.
http://livedocs.adobe.com/flex/3/html/help.html?content=styles_10.html

Chris



Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Montag, 28. Oktober 2013 09:26
An: dev@flex.apache.org
Betreff: Re: How to create generic skins, manage layouts and manage views for 
multiple clients in flex application?

Hi,

> Is there any easy way to create a skinning themes in flex and managing
> assets(icons, fxg) in library?
You can load CSS compiled into a swf at runtime. The swf loaded could be based 
on a client id in an xml file or even the URL the application was loaded from 
or variables passing into the swf from the HTML.

> Is there any easy way(alternative) to mange layout for multiple clients in
> flex ?
States could help you here.

> Some clients don't want login page and other clients wants login page. How
> to  mange these configure views class that without modifying code.
Using states and and XML config file would be one way of doing it.

Thanks,
Justin

AW: ASDoc

[christofer.d...@c-ware.de]

But nevertheless it would be good to have Errors with Error-Messages that help 
track down the problem instead of silently generating XML :-)

Chris


Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Donnerstag, 24. Oktober 2013 00:07
An: dev@flex.apache.org
Betreff: Re: ASDoc

Hi,

Not checked but fairly certain this is not a regression, ASdocs has allways 
been very picky about it's content.

Thanks,
Justin

AW: ASDoc

[christofer.d...@c-ware.de]

Done :-)


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 16:59
An: dev@flex.apache.org
Betreff: RE: ASDoc

Hi Chris,

You are right.  It should report an error instead of producing invalid XML.
I may have a look at the ASDOC compiler code at a later time to fix that.
Can you please raise a ticket if you think it deserves a fix.
Otherwise, I will also forget about this ;-)

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 16:39
À : dev@flex.apache.org
Objet : AW: ASDoc

Hi Maurice,

I wasn't assuming that this was intentional, because in that case I would have 
expected an Exeption or some sort of error message, instead of producing 
invalid XML as Output. Especially it seems to have messed up the entire 
structure of the generated document. So how about outputting some sort of Error 
in that case and not outputting any Input. Cause in case of the Flexmojos 
Testsuite the expected file was created without any error and the tool 
outputting the XML as HTML died ungracefully because of the messed up XML. An 
error explaining what and why something is going wrong would have been good :-)

Just wanted to give some Feedback on Trouble I was having ... allmost had 
forgotton this ;-)

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 16:26
An: dev@flex.apache.org
Betreff: RE: ASDoc

I would rather call that a "bug fix" as the previous versions of ASDoc allowed 
invalid html in the asdoc comments, and now it doesn't anymore.
But I won't argue with you.
So let's call it a regression :-).

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:58
À : dev@flex.apache.org
Objet : AW: ASDoc

This was the Default Header added to all code by Velo who initially created the 
Project. It's not the main intent to make it's way into the generated ASDoc 
documents, but to be in place on any source file same as all These Apache 
Headers in Apache Projects.

And I would call it a Regression as all seems to have worked previously and the 
latest ASDoc implementations produce Nonsense XML.

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:47
An: dev@flex.apache.org
Betreff: RE: ASDoc

Ok, I understand.

/**

* along with this program.  If not, see <http://www.gnu.org/licenses/>.
*/
package net.flexmojos.oss.it

What I don't understand, is why you put asdoc comments at the package level , 
since they are ignored anyway by the ASDOC compiler.

So maybe a simpler fix to that "bug" would have been to remove the second "*" , 
something like:

/*

* along with this program.  If not, see <http://www.gnu.org/licenses/>.
*/
package net.flexmojos.oss.it

what do you think ?

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:30
À : dev@flex.apache.org
Objet : AW: ASDoc

Hi Maurice,

Have a look at this commit: 
https://github.com/chrisdutz/flexmojos/commit/6f0e7f2f390525b45ef47db6cf65fac385a0ee54
I had to replace all "<" with "<" and all ">" with ">" and I'm sure this 
is a Regression.
But one not from us, but by the latest Adobe Versions. The tests run through 
for Flex 2-4.5.x, but start failing in the newest Versions. As I updated 
Flexmojos to circumvent this Problem, I can't really see if it's still a 
Problem.

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:20
An: dev@flex.apache.org
Betreff: RE: ASDoc

Are you sure this is a regression?

Can you give an example of ASDOC comment that causes this problem, so that I 
can run it on older version of ASDOC tool.

Thanks

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:18
À : dev@flex.apache.org
Objet : ASDoc

Hi,

it seems People have been working on ASDoc judging from the number of mails 
regarding ASDoc on the list.
When taking over Flexmojos, my first unit of work was getting the testsuite up 
and running again. It seems in the latest Adobe Flex Versions there was some 
Major regression. I had to modify allmost every source file containng Velos 
license Header as this contained his email-address with a "<" at the front and 
a ">" the end of the address. This caused the ASDoc tool to generate totally 
useless XML-rubbish. Has some work been done on this?

Chris

AW: ASDoc

[christofer.d...@c-ware.de]

Hi Maurice,

I wasn't assuming that this was intentional, because in that case I would have 
expected an Exeption or some sort of error message, instead of producing 
invalid XML as Output. Especially it seems to have messed up the entire 
structure of the generated document. So how about outputting some sort of Error 
in that case and not outputting any Input. Cause in case of the Flexmojos 
Testsuite the expected file was created without any error and the tool 
outputting the XML as HTML died ungracefully because of the messed up XML. An 
error explaining what and why something is going wrong would have been good :-)

Just wanted to give some Feedback on Trouble I was having ... allmost had 
forgotton this ;-)

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 16:26
An: dev@flex.apache.org
Betreff: RE: ASDoc

I would rather call that a "bug fix" as the previous versions of ASDoc allowed 
invalid html in the asdoc comments, and now it doesn't anymore.
But I won't argue with you.
So let's call it a regression :-).

Maurice

-----Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:58
À : dev@flex.apache.org
Objet : AW: ASDoc

This was the Default Header added to all code by Velo who initially created the 
Project. It's not the main intent to make it's way into the generated ASDoc 
documents, but to be in place on any source file same as all These Apache 
Headers in Apache Projects.

And I would call it a Regression as all seems to have worked previously and the 
latest ASDoc implementations produce Nonsense XML.

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:47
An: dev@flex.apache.org
Betreff: RE: ASDoc

Ok, I understand.

/**

* along with this program.  If not, see <http://www.gnu.org/licenses/>.
*/
package net.flexmojos.oss.it

What I don't understand, is why you put asdoc comments at the package level , 
since they are ignored anyway by the ASDOC compiler.

So maybe a simpler fix to that "bug" would have been to remove the second "*" , 
something like:

/*

* along with this program.  If not, see <http://www.gnu.org/licenses/>.
*/
package net.flexmojos.oss.it

what do you think ?

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:30
À : dev@flex.apache.org
Objet : AW: ASDoc

Hi Maurice,

Have a look at this commit: 
https://github.com/chrisdutz/flexmojos/commit/6f0e7f2f390525b45ef47db6cf65fac385a0ee54
I had to replace all "<" with "<" and all ">" with ">" and I'm sure this 
is a Regression.
But one not from us, but by the latest Adobe Versions. The tests run through 
for Flex 2-4.5.x, but start failing in the newest Versions. As I updated 
Flexmojos to circumvent this Problem, I can't really see if it's still a 
Problem.

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:20
An: dev@flex.apache.org
Betreff: RE: ASDoc

Are you sure this is a regression?

Can you give an example of ASDOC comment that causes this problem, so that I 
can run it on older version of ASDOC tool.

Thanks

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:18
À : dev@flex.apache.org
Objet : ASDoc

Hi,

it seems People have been working on ASDoc judging from the number of mails 
regarding ASDoc on the list.
When taking over Flexmojos, my first unit of work was getting the testsuite up 
and running again. It seems in the latest Adobe Flex Versions there was some 
Major regression. I had to modify allmost every source file containng Velos 
license Header as this contained his email-address with a "<" at the front and 
a ">" the end of the address. This caused the ASDoc tool to generate totally 
useless XML-rubbish. Has some work been done on this?

Chris

AW: ASDoc

[christofer.d...@c-ware.de]

This was the Default Header added to all code by Velo who initially created the 
Project. It's not the main intent to make it's way into the generated ASDoc 
documents, but to be in place on any source file same as all These Apache 
Headers in Apache Projects.

And I would call it a Regression as all seems to have worked previously and the 
latest ASDoc implementations produce Nonsense XML.

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:47
An: dev@flex.apache.org
Betreff: RE: ASDoc

Ok, I understand.

/**

* along with this program.  If not, see <http://www.gnu.org/licenses/>.
*/
package net.flexmojos.oss.it

What I don't understand, is why you put asdoc comments at the package level , 
since they are ignored anyway by the ASDOC compiler.

So maybe a simpler fix to that "bug" would have been to remove the second "*" , 
something like:

/*

* along with this program.  If not, see <http://www.gnu.org/licenses/>.
*/
package net.flexmojos.oss.it

what do you think ?

Maurice

-----Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:30
À : dev@flex.apache.org
Objet : AW: ASDoc

Hi Maurice,

Have a look at this commit: 
https://github.com/chrisdutz/flexmojos/commit/6f0e7f2f390525b45ef47db6cf65fac385a0ee54
I had to replace all "<" with "<" and all ">" with ">" and I'm sure this 
is a Regression.
But one not from us, but by the latest Adobe Versions. The tests run through 
for Flex 2-4.5.x, but start failing in the newest Versions. As I updated 
Flexmojos to circumvent this Problem, I can't really see if it's still a 
Problem.

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:20
An: dev@flex.apache.org
Betreff: RE: ASDoc

Are you sure this is a regression?

Can you give an example of ASDOC comment that causes this problem, so that I 
can run it on older version of ASDOC tool.

Thanks

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:18
À : dev@flex.apache.org
Objet : ASDoc

Hi,

it seems People have been working on ASDoc judging from the number of mails 
regarding ASDoc on the list.
When taking over Flexmojos, my first unit of work was getting the testsuite up 
and running again. It seems in the latest Adobe Flex Versions there was some 
Major regression. I had to modify allmost every source file containng Velos 
license Header as this contained his email-address with a "<" at the front and 
a ">" the end of the address. This caused the ASDoc tool to generate totally 
useless XML-rubbish. Has some work been done on this?

Chris

AW: ASDoc

[christofer.d...@c-ware.de]

Hi Maurice,

Have a look at this commit: 
https://github.com/chrisdutz/flexmojos/commit/6f0e7f2f390525b45ef47db6cf65fac385a0ee54
I had to replace all "<" with "<" and all ">" with ">" and I'm sure this 
is a Regression.
But one not from us, but by the latest Adobe Versions. The tests run through 
for Flex 2-4.5.x, but start failing in the newest Versions. As I updated 
Flexmojos to circumvent this Problem, I can't really see if it's still a 
Problem.

Chris


Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:20
An: dev@flex.apache.org
Betreff: RE: ASDoc

Are you sure this is a regression?

Can you give an example of ASDOC comment that causes this problem, so that I 
can run it on older version of ASDOC tool.

Thanks

Maurice

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octobre 2013 15:18
À : dev@flex.apache.org
Objet : ASDoc

Hi,

it seems People have been working on ASDoc judging from the number of mails 
regarding ASDoc on the list.
When taking over Flexmojos, my first unit of work was getting the testsuite up 
and running again. It seems in the latest Adobe Flex Versions there was some 
Major regression. I had to modify allmost every source file containng Velos 
license Header as this contained his email-address with a "<" at the front and 
a ">" the end of the address. This caused the ASDoc tool to generate totally 
useless XML-rubbish. Has some work been done on this?

Chris

ASDoc

[christofer.d...@c-ware.de]

Hi,

it seems People have been working on ASDoc judging from the number of mails 
regarding ASDoc on the list.
When taking over Flexmojos, my first unit of work was getting the testsuite up 
and running again. It seems in the latest Adobe Flex Versions there was some 
Major regression. I had to modify allmost every source file containng Velos 
license Header as this contained his email-address with a "<" at the front and 
a ">" the end of the address. This caused the ASDoc tool to generate totally 
useless XML-rubbish. Has some work been done on this?

Chris

AW: UID performance

[christofer.d...@c-ware.de]

It's allways free? ... ok then this doesn't suck at all ;-) 
At least it explains why I coulnd't find a package in which I could purchase it.


Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Freitag, 18. Oktober 2013 11:08
An: dev@flex.apache.org
Betreff: Re: UID performance

Hi,

> I don't have Scout :-(
Scout is currently free with the free Creative Cloud account last time I 
checked.

Thanks,
Justin

AW: UID performance

[christofer.d...@c-ware.de]

I am currently using the 30 Day Trial of the Creative Cloud Service. In 
gengeral it seems possible to "purchase" Scout as part of the All In package, 
but I couldn't find a way to purchase it separately.

So that sucks :-(

Chris



Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Freitag, 18. Oktober 2013 10:26
An: dev@flex.apache.org
Betreff: RE: UID performance

I don't have Scout :-(

I have a premium FlashBuilder 4.7 licence.

Does it come with it, or is it a separate purchase?

Maurice

-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : vendredi 18 octobre 2013 10:08
À : dev@flex.apache.org
Objet : Re: UID performance

Hi,

Well 10% or so is better than nothing.

Mind running though scout may be that getTime is more expensive on windows and 
skewing the results a little? I vaguely recall something about that in the past.

I tested on OSX.

Thanks,
Justin

AW: AW: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

[christofer.d...@c-ware.de]

Well as far as I know, you don't need a license to use Charts and the ADG with 
Apache Flex at least I wouln'd know where to get such a license, if it was 
needed ;-)
So just ignore that for now :-)

I too have several warnings that I tend to live with ... they never were such a 
pita that I bothered working on them.

Chris

-Ursprüngliche Nachricht-
Von: mscharp [mailto:michael.sch...@fmr.com] 
Gesendet: Mittwoch, 2. Oktober 2013 21:58
An: dev@flex.apache.org
Betreff: Re: AW: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and 
getAdvancedTelemetry()

I never got the warnings to go away, however testing hasn't shown any issues 
thus far.  I'm operating under the idea that those warnings aren't important, 
just annoying (like many other warnings).  I could switch over to the version 
of FM that I built against 4.10, but I feel more comfortable building with the 
version Chris put out even if it does have those warnings.

Another warning I get and haven't been able to fix is the "No license"
warning.  However, since I'm not using charts or other licence only features I 
haven't worried about this either.



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexMojos-6-Flex-sdk-4-10-0-20130801-and-getAdvancedTelemetry-tp29528p30327.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: blazeDS time zone

[christofer.d...@c-ware.de]

Hi,

I remember that using custom property proxies in BlazeDS I was able to adjust 
the serialization exactly the way I wanted to. Unfortunately this was in an 
older Project ... Hopefully I can have a look for it this Weekend and I'll post 
it here.

Chris


Von: Jack Yu [j...@appcomputing.com]
Gesendet: Dienstag, 24. September 2013 09:42
An: dev@flex.apache.org
Betreff: blazeDS time zone

Hi,



BlazeDS automatically translate the time stamp between the client time zone
setting the server time zone.



is there an easy way to disable this time zone translation in BlazeDS?



so that if the date is stored in server (which has GMT time) as 1/1/2013
00:00:00, if the client is in PT -8, the client still get date as 1/1/2013
00:00:00



currently, the blazeDS automatically translate the time to 12/31/2012
16:00:00 because the client time zone is -8



Thanks

Jack

AW: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

[christofer.d...@c-ware.de]

I built FM 6.0.1 against Flex 4.6 so per default FM will Import all of The 
framework libs in 4.6 except if you specify otherwise. I guess you didn't 
Import the Framework-POM but just the libs you needed. That causes Maven to use 
the ones you didn't specify in Version 4.6. You could avoid this by importing 
the Framework-pom AFTER declaring the dependencies you are using. Or you could 
do as I described here: 
https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Flexmojos+6.x in the 
section using the dependencyManagement poms, cause this will not add 
dependencies but manage the Versions of all of the Flex artifacts so you could 
omit the Versions in all Flex dependencies.

Chris


Von: mscharp [michael.sch...@fmr.com]
Gesendet: Freitag, 13. September 2013 01:06
An: dev@flex.apache.org
Betreff: RE: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and 
getAdvancedTelemetry()

I've updated my projects to start building with your 6.0.1 version of FM.  I 
haven't had a chance to really get into it yet, but the first things I'm seeing 
are these warnings.  Any idea why, as I'm building against 4.10.0.20130801?

[WARNING] The POM for com.adobe.flex:compiler:pom:4.6.0.23201 is missing, no 
dependency information available
Downloading: https://repo. CENSORED.com/content/groups/level0. CENSORED 
/com/adobe/flex/compiler/mxmlc/4.6.0.23201/mxmlc-4.6.0.23201.pom
[WARNING] The POM for com.adobe.flex.compiler:mxmlc:jar:4.6.0.23201 is missing, 
no dependency information available
Downloading: https://repo. CENSORED.com/content/groups/level0. CENSORED 
/com/adobe/flex/compiler/digest/4.6.0.23201/digest-4.6.0.23201.pom
[WARNING] The POM for com.adobe.flex.compiler:digest:jar:4.6.0.23201 is 
missing, no dependency information available
Downloading: https://repo. CENSORED.com/content/groups/level0. CENSORED 
/com/adobe/flex/compiler/optimizer/4.6.0.23201/optimizer-4.6.0.23201.pom
[WARNING] The POM for com.adobe.flex.compiler:optimizer:jar:4.6.0.23201 is 
missing, no dependency information available
Downloading: https://repo.CENSORED.com/content/groups/level0. CENSORED 
/com/adobe/flex/compiler/asdoc/4.6.0.23201/asdoc-4.6.0.23201.pom
[WARNING] The POM for com.adobe.flex.compiler:asdoc:jar:4.6.0.23201 is missing, 
no dependency information available
Downloading: 
https://repo.CENSORED.com/content/groups/level0.CENSORED/com/adobe/flex/compiler/swcdepends/4.6.0.23201/swcdepends-4.6.0.23201.pom
[WARNING] The POM for com.adobe.flex.compiler:swcdepends:jar:4.6.0.23201 is 
missing, no dependency information available

I can post poms if it helps.

On a the issue of the RSLs, I have them working and I will post what I have 
online so that anyone else wondering will have something to help them if needed.

Michael

From: christofer.d...@c-ware.de [via Apache Flex Development] 
[mailto:ml-node+s247n29598...@n4.nabble.com]
Sent: Thursday, September 12, 2013 10:32 AM
To: Scharp, Michael
Subject: AW: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and 
getAdvancedTelemetry()

I would expect the thing to blow up in my face ... yes :-)

Cause you would be mixing different Versions of libs ... I don't think that 
would be a good idea.
If you however want to use a library (swc/rsl) however that should be possible 
as Long as the rsl/swc doesn't rely on changed API. But if you are talking 
about modules in the same maven build, I would stronly suggest not to try that.

Chris


Von: Avi Kessner [[hidden email]]
Gesendet: Donnerstag, 12. September 2013 18:24
An: [hidden email]
Betreff: Re: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and 
getAdvancedTelemetry()

If one pom file in a project uses FM 6 and another uses 3 would you expect
that to cause conflicts?
On 12 Sep 2013 19:19, "[hidden 
email]" <[hidden 
email]>
wrote:

> Well actually FM should build your application with any mavenized FDK you
> throw at it. Unless something has changed in more recent Versions of Apache
> Flex. FM automatically uses the Compiler Version it was compiled agains, if
> you don't explicitly fix a Version by using the plugin dependency.
> Otherwise you're free to use whatever Version you like.
>
> The benefit of signed RSLs was even bigger (in my oppinion). As the Flex
> RSLs for an application were only loaded once no matter what URL you
> visited and it usually even survived a Cache cleanup. As soon as a SWZ was
> loaded, the Flashplayer sort of installed it locally and as soon as an
> application needed it again, it simply loaded it without having to download
> it again.
>
> The reason for you having to explicitly list every dependency that Needs a
> non-Default scope, is mavens inability to overload scopes. So the framworks
> master pom has normal dependencies to it's libs and if you simply reference
> that, you wouldn't utilize the shared-lib concept of

AW: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

[christofer.d...@c-ware.de]

I would expect the thing to blow up in my face ... yes :-)

Cause you would be mixing different Versions of libs ... I don't think that 
would be a good idea.
If you however want to use a library (swc/rsl) however that should be possible 
as Long as the rsl/swc doesn't rely on changed API. But if you are talking 
about modules in the same maven build, I would stronly suggest not to try that.

Chris


Von: Avi Kessner [akess...@gmail.com]
Gesendet: Donnerstag, 12. September 2013 18:24
An: dev@flex.apache.org
Betreff: Re: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and 
getAdvancedTelemetry()

If one pom file in a project uses FM 6 and another uses 3 would you expect
that to cause conflicts?
On 12 Sep 2013 19:19, "christofer.d...@c-ware.de" 
wrote:

> Well actually FM should build your application with any mavenized FDK you
> throw at it. Unless something has changed in more recent Versions of Apache
> Flex. FM automatically uses the Compiler Version it was compiled agains, if
> you don't explicitly fix a Version by using the plugin dependency.
> Otherwise you're free to use whatever Version you like.
>
> The benefit of signed RSLs was even bigger (in my oppinion). As the Flex
> RSLs for an application were only loaded once no matter what URL you
> visited and it usually even survived a Cache cleanup. As soon as a SWZ was
> loaded, the Flashplayer sort of installed it locally and as soon as an
> application needed it again, it simply loaded it without having to download
> it again.
>
> The reason for you having to explicitly list every dependency that Needs a
> non-Default scope, is mavens inability to overload scopes. So the framworks
> master pom has normal dependencies to it's libs and if you simply reference
> that, you wouldn't utilize the shared-lib concept of RSLs but use normal
> SWCs for compilation, resulting in a way bigger Output file. So if you want
> to migrate your Project to Apache Flex you have to replace every Caching
> scope with "rsl".
>
> Chris
>
>
> 
> Von: mscharp [michael.sch...@fmr.com]
> Gesendet: Donnerstag, 12. September 2013 18:03
> An: dev@flex.apache.org
> Betreff: RE: FlexMojos 6, Flex sdk 4.10.0.20130801, and
> getAdvancedTelemetry()
>
> Thanks for the responses Chris.  Yeah, FM is a beast to build.  I can't
> say enough "Thank Yous" for taking over the project.
>
> So, my understanding was that FM had to be built against the version of
> the FDK you wanted to use.  I'm assuming this is incorrect.  Has anyone
> tried using FM 6.0.1 with the 4.10 FDK?  My only question with it having to
> do with the getAdvancedTelemetry() function that I had to add to the FM
> source code.
>
> As far as the RSLs, I read in the release notes that they aren't signed,
> and that it only make sense to use RSLs if you are serving multiple flex
> applications from the same domain... which we are.  So, previously in our
> pom files we had:
>
>  
>
> com.adobe.flex.framework
>
> framework
>
> ${flex.sdk.version}
> swc
> caching
> 
> 
>
> com.adobe.flex.framework
>
> textLayout
>
> ${flex.sdk.version}
> swc
> caching
> 
> 
>
> com.adobe.flex.framework
>
> charts
>
> ${flex.sdk.version}
> swc
> caching
> 
> 
>
> com.adobe.flex.framework
>
> rpc
>
> ${flex.sdk.version}
> swc
> caching
> 
> 
>
> com.adobe.flex.framework
> mx
>
> ${flex.sdk.version}
> swc
> caching
> 
> 
>
> com.adobe.flex.framework
>
> advancedgrids
>
> ${flex.sdk.version}
> swc
> caching
> 
> 
>
> com.adobe.flex.framework

AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

[christofer.d...@c-ware.de]

${flex.sdk.version}
swc
caching



com.adobe.flex.framework

spark_dmv

${flex.sdk.version}
swc
caching


Currently I'm not listing any of these as dependencies in our new poms.  I've 
been following what I've been able to find on the web as far as standard 
practices for what needs to be included in the pom files, but a lot of them 
look a bit different than what we currently have in our poms.  So, I'm not sure 
if I still need those dependencies listed or not.  If I do, would the scope be 
"rsl" instead of "caching" and now look more like this?



com.adobe.flex.framework

spark_dmv

${flex.sdk.version}
swc
rsl
        

Again, thanks everyone for the help.

Michael

From: christofer.d...@c-ware.de [via Apache Flex Development] 
[mailto:ml-node+s247n29584...@n4.nabble.com]
Sent: Thursday, September 12, 2013 6:00 AM
To: Scharp, Michael
Subject: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

Yeah ... but in Flexmojos you can have a dependency of type "swc", "rsl" and 
"caching". Depending on the type of dependency it loads different files from 
maven "swc", "swf" or "swz". The test-cases utilizing the signed rsls have 
dependencies of type "Caching" and therefore maven Looks for swz files, which 
it doesn't find and therefore the build Fails, causing the testsuite to fail.

Chris


Von: Justin Mclean [[hidden 
email]]
Gesendet: Donnerstag, 12. September 2013 02:45
An: [hidden email]
Betreff: Re: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

Hi,

> This is because we don't have any signed RSLs (SWZ Files).
Why do you need signed files? Apache Flex does come with RSLs they are just not 
signed.

Thanks,
Justin

If you reply to this email, your message will be added to the discussion below:
http://apache-flex-development.247.n4.nabble.com/FlexMojos-6-Flex-sdk-4-10-0-20130801-and-getAdvancedTelemetry-tp29528p29584.html
To unsubscribe from FlexMojos 6, Flex sdk 4.10.0.20130801, and 
getAdvancedTelemetry(), click 
here<http://apache-flex-development.247.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=29528&code=bWljaGFlbC5zY2hhcnBAZm1yLmNvbXwyOTUyOHwtMTU2NDIyNDE0NA==>.
NAML<http://apache-flex-development.247.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexMojos-6-Flex-sdk-4-10-0-20130801-and-getAdvancedTelemetry-tp29528p29594.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

[christofer.d...@c-ware.de]

Yeah ... but in Flexmojos you can have a dependency of type "swc", "rsl" and 
"caching". Depending on the type of dependency it loads different files from 
maven "swc", "swf" or "swz". The test-cases utilizing the signed rsls have 
dependencies of type "Caching" and therefore maven Looks for swz files, which 
it doesn't find and therefore the build Fails, causing the testsuite to fail.

Chris


Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Donnerstag, 12. September 2013 02:45
An: dev@flex.apache.org
Betreff: Re: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

Hi,

> This is because we don't have any signed RSLs (SWZ Files).
Why do you need signed files? Apache Flex does come with RSLs they are just not 
signed.

Thanks,
Justin

AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

[christofer.d...@c-ware.de]

Hi Michael,

building FM is a beast ... This is mainly because it's backward compatible with 
almost all FDKs available. Unfortunately you need all of them in the Testsuite. 
But I guess that you usually don't need the testharnes to run. Especially this 
is guaranteed to fail when building FM with an Apache Flex FDK. This is because 
we don't have any signed RSLs (SWZ Files). Therefore all Tests dealing with 
signed RSLs are doomed to fail. But FM seemed to build well with Apache FDKs, I 
just had do disable one or the other test that used SWZs.

But I think you don't need to build FM at all. I recently released FM 6.0.1 
which seems to work nicely with Apache Flex FDKs that are mavenized using the 
Mavenizer (At least I haven't heard any complaints). You do however have to 
override the default Flex imports the plugin uses. So if you provide the 
Compiler in the version you want as dependency to the plugin and the framework 
in the same version as the compiler to your modules dependencies, it should 
already be ready to go.

Bob recently posted his setup at Stackoverflow ... so using this as inspiration 
should have you up and running in no-time:
http://stackoverflow.com/questions/18505129/how-do-i-get-flexunit-flexm

If you have any questions, feel free to come here and ask (Even if the 
flex-user list might be better suited for questions like this)

Chris




-Ursprüngliche Nachricht-
Von: mscharp [mailto:michael.sch...@fmr.com] 
Gesendet: Mittwoch, 11. September 2013 20:39
An: dev@flex.apache.org
Betreff: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

Hi All - I'm hoping I'm posting this in the correct space.  I've seen Chris 
Dutz around here and since Marvin shut down the old FM group, this looks like 
the best place for my questions.

Anyway - I'm currently working on updating our large flex project(s) from FM 
4.2-beta to FM 6.1.0.  I've pulled down the FM6 code from Chris' git repo, 
mavenized the 4.10.0 FDK, built FM6, and I'm now using it to build our project. 
 Everything seems to work.  However, I've got a few questions regarding the 
impact of some changes I made to FM code and questions about RSLs.

In order to get FM6 to build, I had to make some changes.  Most of them seem 
straight forward enough (no real questions) but I'll list them all for 
completeness sake.  The ones I believe most important are bolded.

- in parent pom
- update flex version to 4.10.20130801
- update air version to 3.8
- update player version to 11.8
- update org.apache.velocity version to 1.7 (this is the version we 
have in our repo)

- *comment out all sdk versions in flexmojos-test-harness pom*
- *add 4.10.20130801 sdk to flexmojos-test-harness pom*
- *comment out old player global versions from flexmojos-test-harness pom*
- *add 11.8 playerglobal to flexmojos-test-harness pom*
- add org.apache.velocity 1.7 dependency to flexmojos-maven-plugin pom 
(couldn't build without this)
- *AsdocMojo.java, CompcMojo.java, and MxmlcMojo.java override
getAdvancedTelemetry()*

It is also important to note that I was able to build everything with tests up 
till the "test-harness".  For now, my build of FM6 is running with 
maven.test.skip=true.  In order for the integration tests to pass, I need a lot 
of mavenized sdks that I currently don't have  I looked for the 2x and 3x sdks 
online so I could mavenize them, but didn't find them.  To be honest however, I 
don't really care at all about anything below sdk 4.5 so I'm not thinking that 
is a huge issue.  However, if that is wrong, please let me know.

In order to build with the 4.10.0 SDK, I added the advanced telemetry function 
to the different mojos:

@Override
public Boolean getAdvancedTelemetry()
{
return true;
}

I'm not entirely sure what this will do.  With this function as it is, am I 
just enabling my swfs to "output" advanced telemetry, or is there something 
more going on?  Should I return false instead of true?  What are the 
implications of this?

Anyway, hope all this makes sense.  Thanks for the help

Michael



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexMojos-6-Flex-sdk-4-10-0-20130801-and-getAdvancedTelemetry-tp29528.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: Problems running Mavenizer

[christofer.d...@c-ware.de]

Hi,

it's still that way ... and it's nothing I will be able to come upt with a fix 
though. The only Option would be to release Flexmojos in two flavours ... one 
that works with the Apache GID and one with the Adobe GID :-( Unfortunately as 
soon as I Switch to Apache GIDs the Testsuite completely Fails to run. This is 
the reason for me not having done this step yet). 

This is a issue releated to Maven and how you can override Default-Dependencies 
by providing a custom version, but not if the imported dependency has a 
different GID, then Maven will try to load dependencies with both GIDs and 
different Versions. So whenever you would use Flexmojos with an Apache FDK it 
would have the Default Adobe Flex dependencies it was compiled with pluss the 
ones from Apache which causes millions of Trouble. 

Sorry for not having a nicer answer ... But I guess it would be a good Idea do 
do such an 6.0.1-apache release to allow us to use our cool Apache FDKs without 
having to Name them Adobe ;-)

Chris 


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Montag, 2. September 2013 12:40
An: dev@flex.apache.org
Betreff: RE: Problems running Mavenizer

Back to one year ago, the last time I used the apache groupId, I couldn't
use the FDKs, I'm not sure to remember why but I guess that was because FM
still use a compiler ref linked to the adobe groupId, so, I would pass
always false to this parameter but maybe @Chris could remind us if it is
still like that or not.

Out of that, if you don't mind, I would like to implement that feature in
the installer, sure I would need some help to make it working on mac and
Linux (I'm thinking about the git detection), however, I've got already the
code working for the windows part.

> The README needs to be updated to reflect the fact that a third parameter
is required: "use-apache-gid"

Yep, still need to install the SDK on my new computer, given today seems to
be quiet, I guess I can handle that.

-Fred

-Message d'origine-
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash
Muppirala
Envoyé : lundi 2 septembre 2013 09:58
À : dev@flex.apache.org
Objet : Problems running Mavenizer

I am following the README from here:
https://fisheye6.atlassian.com/browse/flex-utilities/mavenizer/README.txt?hb
=true

A couple of problems:

1.  The README needs to be updated to reflect the fact that a third
parameter is required: "use-apache-gid"
2.  When I run it in this format:


C:\p\flex_os\workspace\flexroot\git\flex-utilities\mavenizer>java -cp
target\flex-sdk-converter-1.0.jar SDKGenerator "C:\Program Files
(x86)\Adobe\Adobe Flash Builder 4.6\sdks\ApacheFlex4.10.0"
"C:\temp\mavenized" true
or

C:\p\flex_os\workspace\flexroot\git\flex-utilities\mavenizer>java -cp
target\flex-sdk-converter-1.0.jar SDKGenerator "C:\Program Files
(x86)\Adobe\Adobe Flash Builder 4.6\sdks\ApacheFlex4.10.0"
"C:\temp\mavenized" false

nothing seems to happen.  No error message, no mavenized SDK, it just quits
silently.

I even tried copying the Apache Flex SDK to a directory with no spaces,
still no luck.

Before I dig in too much, any idea what could be going on here?

Thanks,
Om

AW: AW: AW: FlexUnit

[christofer.d...@c-ware.de]

Well the arguments should be source-directory and target Directory. 
I made the target-directory a Parameter because I didn't want the mavenizer to 
mess with my local repo while developing it. But it should be a valid Approach 
to use the FDK Directory as source and have a look at the mavens 
~userhome\.m2\settings.xml for the local repo path and if that's not available 
to use the Default of ~userhome\.m2\repository.

Chris


Von: Avi Kessner [akess...@gmail.com]
Gesendet: Freitag, 30. August 2013 11:31
An: dev@flex.apache.org
Betreff: Re: AW: AW: FlexUnit

Just incase it isn't clear, the command line tool requires some user
specific arguments,  so the installer needs to handle that as well
On 30 Aug 2013 10:28, "OmPrakash Muppirala"  wrote:

On Aug 29, 2013 11:44 PM, "christofer.d...@c-ware.de" <
christofer.d...@c-ware.de> wrote:
>
> Well the poms themselves don't help with the libs. I will probably be
adding functionality to download Adobe stuff after asking for confirmation
by the user as we discussed some months ago as soon as I am picking up on
the new maven plugin. Guess it would be possible to have binary Apache Flex
Releases in public repos. But for now I really like the idea of integrating
the Mavenizer and Deployer into the Installer (You Need that anyway in
order to get a new FDK)
>
> Chris
>

I am up for it.  Although I need to admit that most of what you just said
is beyond my understanding.  Let me  propose a route.  Tell me if I am in
the right track.

1.  User accepts all the licenses in the Installer.
2.  Installation completes and SDK (FDK in your terminology) is ready to be
used with an IDE.
3. We show the user an option to Mavenize the SDK.
4. If the user accepts, then we invoke the Mavenizer command-line script.
5.  We show another prompt asking if the user wants to deploy it.
6.  If the user accepts, then we invoke the Deployer command-line script.

Is this acceptable/doable?  This is doable from the Installer point if view.

Thanks,
Om

> 
> Von: Alex Harui [aha...@adobe.com]
> Gesendet: Donnerstag, 29. August 2013 23:27
> An: dev@flex.apache.org
> Betreff: Re: AW: FlexUnit
>
> On 8/29/13 8:08 AM, "christofer.d...@c-ware.de"
>  wrote:
>
> >Well the Problem are the Adobe libs ... playerglobal and some others,
> >that we are not allowed to publish. There wouldn't be any trouble with
> >deploying the rest of the FDK to public repos beyond that, I guess. But
> >unfortunately these FDKs would be completeley useless without the missing
> >Adobe libs :-(
>
> Yeah, but I thought we were going to try to put POMs on the Adobe download
> server?  What happened to that plan?
>
> -Alex

AW: AW: AW: FlexUnit

[christofer.d...@c-ware.de]

Sounds sensible and it would simplyfy stuff greatly :-)

Chris


Von: omup...@gmail.com [omup...@gmail.com] im Auftrag von OmPrakash Muppirala 
[bigosma...@gmail.com]
Gesendet: Freitag, 30. August 2013 09:27
An: dev@flex.apache.org
Betreff: Re: AW: AW: FlexUnit

On Aug 29, 2013 11:44 PM, "christofer.d...@c-ware.de" <
christofer.d...@c-ware.de> wrote:
>
> Well the poms themselves don't help with the libs. I will probably be
adding functionality to download Adobe stuff after asking for confirmation
by the user as we discussed some months ago as soon as I am picking up on
the new maven plugin. Guess it would be possible to have binary Apache Flex
Releases in public repos. But for now I really like the idea of integrating
the Mavenizer and Deployer into the Installer (You Need that anyway in
order to get a new FDK)
>
> Chris
>

I am up for it.  Although I need to admit that most of what you just said
is beyond my understanding.  Let me  propose a route.  Tell me if I am in
the right track.

1.  User accepts all the licenses in the Installer.
2.  Installation completes and SDK (FDK in your terminology) is ready to be
used with an IDE.
3. We show the user an option to Mavenize the SDK.
4. If the user accepts, then we invoke the Mavenizer command-line script.
5.  We show another prompt asking if the user wants to deploy it.
6.  If the user accepts, then we invoke the Deployer command-line script.

Is this acceptable/doable?  This is doable from the Installer point if view.

Thanks,
Om

> 
> Von: Alex Harui [aha...@adobe.com]
> Gesendet: Donnerstag, 29. August 2013 23:27
> An: dev@flex.apache.org
> Betreff: Re: AW: FlexUnit
>
> On 8/29/13 8:08 AM, "christofer.d...@c-ware.de"
>  wrote:
>
> >Well the Problem are the Adobe libs ... playerglobal and some others,
> >that we are not allowed to publish. There wouldn't be any trouble with
> >deploying the rest of the FDK to public repos beyond that, I guess. But
> >unfortunately these FDKs would be completeley useless without the missing
> >Adobe libs :-(
>
> Yeah, but I thought we were going to try to put POMs on the Adobe download
> server?  What happened to that plan?
>
> -Alex

AW: AW: FlexUnit

[christofer.d...@c-ware.de]

Well the poms themselves don't help with the libs. I will probably be adding 
functionality to download Adobe stuff after asking for confirmation by the user 
as we discussed some months ago as soon as I am picking up on the new maven 
plugin. Guess it would be possible to have binary Apache Flex Releases in 
public repos. But for now I really like the idea of integrating the Mavenizer 
and Deployer into the Installer (You Need that anyway in order to get a new 
FDK) 

Chris


Von: Alex Harui [aha...@adobe.com]
Gesendet: Donnerstag, 29. August 2013 23:27
An: dev@flex.apache.org
Betreff: Re: AW: FlexUnit

On 8/29/13 8:08 AM, "christofer.d...@c-ware.de"
 wrote:

>Well the Problem are the Adobe libs ... playerglobal and some others,
>that we are not allowed to publish. There wouldn't be any trouble with
>deploying the rest of the FDK to public repos beyond that, I guess. But
>unfortunately these FDKs would be completeley useless without the missing
>Adobe libs :-(

Yeah, but I thought we were going to try to put POMs on the Adobe download
server?  What happened to that plan?

-Alex

AW: FlexUnit

[christofer.d...@c-ware.de]

Well the Problem are the Adobe libs ... playerglobal and some others, that we 
are not allowed to publish. There wouldn't be any trouble with deploying the 
rest of the FDK to public repos beyond that, I guess. But unfortunately these 
FDKs would be completeley useless without the missing Adobe libs :-(


Von: Avi Kessner [akess...@gmail.com]
Gesendet: Donnerstag, 29. August 2013 16:06
An: dev@flex.apache.org
Betreff: Re: FlexUnit

So legally we can't store these sdks for maven publicly?  I see 4.1 is
112MB, yech.
brought to you by the letters A, V, and I
and the number 47


On Thu, Aug 29, 2013 at 2:32 PM, christofer.d...@c-ware.de
 wrote:
> And I hate "lawyers" more than "manually" ;-)
>
> It's actually a Multi Minute process to Mavenize an FDK as I created the 
> Apache Flex Mavenizer for that (It actually also mavenizes Adobe Flex FDKs) 
> together with the Auto deployer you should have any Flex FDK mavenized and 
> deployed in minutes.
>
> https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Migrating+to+6.x?src=search
>
> Chris
>
> 
> Von: Avi Kessner [akess...@gmail.com]
> Gesendet: Donnerstag, 29. August 2013 12:33
> An: dev@flex.apache.org
> Betreff: Re: FlexUnit
>
> Thanks.
> I hate that word.. "manually".
> Is there a more recent version or alternative to mockolate as well?
> And is this a multi day or multi hour process to mavenize the FDK?
> brought to you by the letters A, V, and I
> and the number 47
>
>
> On Thu, Aug 29, 2013 at 1:11 PM, christofer.d...@c-ware.de
>  wrote:
>> Hi,
>>
>> Unit testing is a pretty tricky thing in Flexmojos. That's one of the things 
>> I am intending on performing the largest changes the the new plugin. But 
>> from your question I can see you are using an about 100 year old Version of 
>> Flexmojos and Flex. I know I did quite a lot of tweaks and updates in the 
>> flexunit Support when we were working on releasing flexunit 4.x. So I would 
>> like to ask you to update so a somewhat reasonably new Version of flexmojos 
>> ... 6.0.1 would be best ... but Keep in mind that you Need to manually 
>> mavenize the FDK you want to use.
>>
>> Chris
>>
>> 
>> Von: Avi Kessner [akess...@gmail.com]
>> Gesendet: Donnerstag, 29. August 2013 09:52
>> An: dev@flex.apache.org
>> Betreff: Re: FlexUnit
>>
>> I'm sorry to go off topic, but this is really starting to fustrate me.
>>  If anyone is able to help me out over at stackOverflow I really
>> appreciate it!
>>
>> http://stackoverflow.com/questions/18505129/how-do-i-get-flexunit-flexmojos-and-mockolate-to-work-together
>> brought to you by the letters A, V, and I
>> and the number 47
>>
>>
>> On Thu, Aug 29, 2013 at 6:11 AM, Cyrill Zadra  wrote:
>>> Great! .. I pushed my changes always to "makeFlexUnitApacheReady". Shall I
>>> merge those changes also to develop branch and continue to work on this one?
>>>
>>> Cyrill
>>>
>>>
>>> On Thu, Aug 29, 2013 at 3:29 AM, Michael A. Labriola <
>>> labri...@digitalprimates.net> wrote:
>>>
>>>>
>>>> In the FlexUnit repo right now there is only a master.
>>>>
>>>> I am creating a develop branch presently and pushing some changes we made
>>>> to the flexunit tasks to support a URL instead of just a local file when
>>>> executing tests.
>>>>
>>>> We should just make sure this gets integrated into master before the next
>>>> release.
>>>>
>>>> Mike
>>>>

AW: FlexUnit

[christofer.d...@c-ware.de]

That actually sounds like a really good idea from my side ... and I really 
don't know, why nobody came up with that Suggestion yet ;-) 

It would reduce the "Manual" part to the clicking of a Checkbox. In that case I 
would also opt for a second Checkbox that is available as soon as someone 
choose to mavenize in which a user can choose to automatically deploy to an 
repository Manager (Artifactory, Nexus) using the deployer tool from within the 
installer.

Chris


Von: Nick Collins [ndcoll...@gmail.com]
Gesendet: Donnerstag, 29. August 2013 16:16
An: dev@flex.apache.org
Betreff: Re: FlexUnit

Would a reasonable compromise be to  add the "mavenizing" of the FDK as an
option to the installer? Where all I need do is check a box saying "Use
Apache Flex with Maven", and have the installer take care of converting the
FDK to the maven format and adding it to my local Maven repository.


On Thu, Aug 29, 2013 at 9:06 AM, Avi Kessner  wrote:

> Oh, and thank you.  mavenizing was very quick and easy , deploying on
> the other hand.. (atleast I don't have to do it manually)
>
> brought to you by the letters A, V, and I
> and the number 47
>
>
> On Thu, Aug 29, 2013 at 5:06 PM, Avi Kessner  wrote:
> > So legally we can't store these sdks for maven publicly?  I see 4.1 is
> > 112MB, yech.
> > brought to you by the letters A, V, and I
> > and the number 47
> >
> >
> > On Thu, Aug 29, 2013 at 2:32 PM, christofer.d...@c-ware.de
> >  wrote:
> >> And I hate "lawyers" more than "manually" ;-)
> >>
> >> It's actually a Multi Minute process to Mavenize an FDK as I created
> the Apache Flex Mavenizer for that (It actually also mavenizes Adobe Flex
> FDKs) together with the Auto deployer you should have any Flex FDK
> mavenized and deployed in minutes.
> >>
> >>
> https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Migrating+to+6.x?src=search
> >>
> >> Chris
> >>
> >> 
> >> Von: Avi Kessner [akess...@gmail.com]
> >> Gesendet: Donnerstag, 29. August 2013 12:33
> >> An: dev@flex.apache.org
> >> Betreff: Re: FlexUnit
> >>
> >> Thanks.
> >> I hate that word.. "manually".
> >> Is there a more recent version or alternative to mockolate as well?
> >> And is this a multi day or multi hour process to mavenize the FDK?
> >> brought to you by the letters A, V, and I
> >> and the number 47
> >>
> >>
> >> On Thu, Aug 29, 2013 at 1:11 PM, christofer.d...@c-ware.de
> >>  wrote:
> >>> Hi,
> >>>
> >>> Unit testing is a pretty tricky thing in Flexmojos. That's one of the
> things I am intending on performing the largest changes the the new plugin.
> But from your question I can see you are using an about 100 year old
> Version of Flexmojos and Flex. I know I did quite a lot of tweaks and
> updates in the flexunit Support when we were working on releasing flexunit
> 4.x. So I would like to ask you to update so a somewhat reasonably new
> Version of flexmojos ... 6.0.1 would be best ... but Keep in mind that you
> Need to manually mavenize the FDK you want to use.
> >>>
> >>> Chris
> >>>
> >>> 
> >>> Von: Avi Kessner [akess...@gmail.com]
> >>> Gesendet: Donnerstag, 29. August 2013 09:52
> >>> An: dev@flex.apache.org
> >>> Betreff: Re: FlexUnit
> >>>
> >>> I'm sorry to go off topic, but this is really starting to fustrate me.
> >>>  If anyone is able to help me out over at stackOverflow I really
> >>> appreciate it!
> >>>
> >>>
> http://stackoverflow.com/questions/18505129/how-do-i-get-flexunit-flexmojos-and-mockolate-to-work-together
> >>> brought to you by the letters A, V, and I
> >>> and the number 47
> >>>
> >>>
> >>> On Thu, Aug 29, 2013 at 6:11 AM, Cyrill Zadra 
> wrote:
> >>>> Great! .. I pushed my changes always to "makeFlexUnitApacheReady".
> Shall I
> >>>> merge those changes also to develop branch and continue to work on
> this one?
> >>>>
> >>>> Cyrill
> >>>>
> >>>>
> >>>> On Thu, Aug 29, 2013 at 3:29 AM, Michael A. Labriola <
> >>>> labri...@digitalprimates.net> wrote:
> >>>>
> >>>>>
> >>>>> In the FlexUnit repo right now there is only a master.
> >>>>>
> >>>>> I am creating a develop branch presently and pushing some changes we
> made
> >>>>> to the flexunit tasks to support a URL instead of just a local file
> when
> >>>>> executing tests.
> >>>>>
> >>>>> We should just make sure this gets integrated into master before the
> next
> >>>>> release.
> >>>>>
> >>>>> Mike
> >>>>>
>

AW: FlexUnit

[christofer.d...@c-ware.de]

And I hate "lawyers" more than "manually" ;-) 

It's actually a Multi Minute process to Mavenize an FDK as I created the Apache 
Flex Mavenizer for that (It actually also mavenizes Adobe Flex FDKs) together 
with the Auto deployer you should have any Flex FDK mavenized and deployed in 
minutes.

https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Migrating+to+6.x?src=search

Chris


Von: Avi Kessner [akess...@gmail.com]
Gesendet: Donnerstag, 29. August 2013 12:33
An: dev@flex.apache.org
Betreff: Re: FlexUnit

Thanks.
I hate that word.. "manually".
Is there a more recent version or alternative to mockolate as well?
And is this a multi day or multi hour process to mavenize the FDK?
brought to you by the letters A, V, and I
and the number 47


On Thu, Aug 29, 2013 at 1:11 PM, christofer.d...@c-ware.de
 wrote:
> Hi,
>
> Unit testing is a pretty tricky thing in Flexmojos. That's one of the things 
> I am intending on performing the largest changes the the new plugin. But from 
> your question I can see you are using an about 100 year old Version of 
> Flexmojos and Flex. I know I did quite a lot of tweaks and updates in the 
> flexunit Support when we were working on releasing flexunit 4.x. So I would 
> like to ask you to update so a somewhat reasonably new Version of flexmojos 
> ... 6.0.1 would be best ... but Keep in mind that you Need to manually 
> mavenize the FDK you want to use.
>
> Chris
>
> 
> Von: Avi Kessner [akess...@gmail.com]
> Gesendet: Donnerstag, 29. August 2013 09:52
> An: dev@flex.apache.org
> Betreff: Re: FlexUnit
>
> I'm sorry to go off topic, but this is really starting to fustrate me.
>  If anyone is able to help me out over at stackOverflow I really
> appreciate it!
>
> http://stackoverflow.com/questions/18505129/how-do-i-get-flexunit-flexmojos-and-mockolate-to-work-together
> brought to you by the letters A, V, and I
> and the number 47
>
>
> On Thu, Aug 29, 2013 at 6:11 AM, Cyrill Zadra  wrote:
>> Great! .. I pushed my changes always to "makeFlexUnitApacheReady". Shall I
>> merge those changes also to develop branch and continue to work on this one?
>>
>> Cyrill
>>
>>
>> On Thu, Aug 29, 2013 at 3:29 AM, Michael A. Labriola <
>> labri...@digitalprimates.net> wrote:
>>
>>>
>>> In the FlexUnit repo right now there is only a master.
>>>
>>> I am creating a develop branch presently and pushing some changes we made
>>> to the flexunit tasks to support a URL instead of just a local file when
>>> executing tests.
>>>
>>> We should just make sure this gets integrated into master before the next
>>> release.
>>>
>>> Mike
>>>

AW: FlexUnit

[christofer.d...@c-ware.de]

Hi,

Unit testing is a pretty tricky thing in Flexmojos. That's one of the things I 
am intending on performing the largest changes the the new plugin. But from 
your question I can see you are using an about 100 year old Version of 
Flexmojos and Flex. I know I did quite a lot of tweaks and updates in the 
flexunit Support when we were working on releasing flexunit 4.x. So I would 
like to ask you to update so a somewhat reasonably new Version of flexmojos ... 
6.0.1 would be best ... but Keep in mind that you Need to manually mavenize the 
FDK you want to use.

Chris


Von: Avi Kessner [akess...@gmail.com]
Gesendet: Donnerstag, 29. August 2013 09:52
An: dev@flex.apache.org
Betreff: Re: FlexUnit

I'm sorry to go off topic, but this is really starting to fustrate me.
 If anyone is able to help me out over at stackOverflow I really
appreciate it!

http://stackoverflow.com/questions/18505129/how-do-i-get-flexunit-flexmojos-and-mockolate-to-work-together
brought to you by the letters A, V, and I
and the number 47


On Thu, Aug 29, 2013 at 6:11 AM, Cyrill Zadra  wrote:
> Great! .. I pushed my changes always to "makeFlexUnitApacheReady". Shall I
> merge those changes also to develop branch and continue to work on this one?
>
> Cyrill
>
>
> On Thu, Aug 29, 2013 at 3:29 AM, Michael A. Labriola <
> labri...@digitalprimates.net> wrote:
>
>>
>> In the FlexUnit repo right now there is only a master.
>>
>> I am creating a develop branch presently and pushing some changes we made
>> to the flexunit tasks to support a URL instead of just a local file when
>> executing tests.
>>
>> We should just make sure this gets integrated into master before the next
>> release.
>>
>> Mike
>>

AW: Maven-Flex-Plugin WAS: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

[christofer.d...@c-ware.de]

Hi Carlos,

currently I haven't touched the falcon Compiler Project. But If you were to 
mavenize it, it would certainly be a great big help (This way we wouldn't Need 
to mavenize the Compiler part of Flex any more)

Chris



Von: carlos.rov...@gmail.com [carlos.rov...@gmail.com] im Auftrag von Carlos 
Rovira [carlos.rov...@codeoscopic.com]
Gesendet: Dienstag, 6. August 2013 10:23
An: dev@flex.apache.org
Betreff: Re: Maven-Flex-Plugin WAS: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

Maybe this is the same way IntelliJ use to deal with flexmojos projects?
they generate a -config.xml file based on pom.xml configuration.

Chris, I've started a work on mavenizing falcon compiler. Work is still at
the beginning, but I want to ask you if you are doing something similar or
you would want to rely in something like I'm doing...or maybe none of the
two :)



2013/8/5 christofer.d...@c-ware.de 

> Hi Alex,
>
> sorry for the late Response. I was on a short Holiday trip.
>
> I have to admit that I didn't implement the Integration in Flexmojos, but
> as far as I understood the code, Velo used some code-generation to somehow
> extract an API, that he then uses to programatically call the Compiler. But
> still I think he does rely on the -config.xml files. This was a pretty
> fragile construct and strangely was one that currently seems to cause
> test-failures when using the most recent Adobe Flex and all of the Apache
> Flex versions. I am hoping to have something more solid in Apache Falcon.
>
> Chris
>
> 
> Von: Alex Harui [aha...@adobe.com]
> Gesendet: Mittwoch, 31. Juli 2013 20:54
> An: dev@flex.apache.org
> Betreff: Re: Maven-Flex-Plugin WAS: IntelliJ - ApacheFlex4.9.1 - flexmojos
> 6.0.1
>
> On 7/31/13 9:55 AM, "christofer.d...@c-ware.de"
>  wrote:
>
> >Hi Guys :-)
> >
> >Today I think I reached an important milestone with my
> >generator-maven-plugin. This will definitely need some fine-tuning, but I
> >think I'll do that on the way. At least now I can generate any form of
> >code from any sort of Java Class File or Source File. That was the big
> >step I needed in order to continue with the maven-flex-plugin (By the way
> >... am I allowed to name it that way? The "maven" prefix of a plugin
> >seems to be reserved for official maven plugins supported by Apache ...
> >so I guess it should be ok).
> I would recommend asking at trademarks@a.o
>
> >
> >I was intending on supporting only the falcon compiler and would start to
> >support only Apache Flex and FlexUnit first (No need for high blood
> >preasure ... the other stuff should come as the plugin matures). Think I
> >will be needing quite some input from anyone on the Falcon Compiler team.
> >Is there any sort of documentation for using and configuring the compiler
> >programmatically (not using the intermediate commandline)?
> How do you interact with the current MXMLC programmatically?  Is there an
> API or are you just using -config.xml files?
>
> -Alex
>



--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

AW: Maven-Flex-Plugin WAS: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

[christofer.d...@c-ware.de]

Hi Alex, 

sorry for the late Response. I was on a short Holiday trip.

I have to admit that I didn't implement the Integration in Flexmojos, but as 
far as I understood the code, Velo used some code-generation to somehow extract 
an API, that he then uses to programatically call the Compiler. But still I 
think he does rely on the -config.xml files. This was a pretty fragile 
construct and strangely was one that currently seems to cause test-failures 
when using the most recent Adobe Flex and all of the Apache Flex versions. I am 
hoping to have something more solid in Apache Falcon. 

Chris


Von: Alex Harui [aha...@adobe.com]
Gesendet: Mittwoch, 31. Juli 2013 20:54
An: dev@flex.apache.org
Betreff: Re: Maven-Flex-Plugin WAS: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

On 7/31/13 9:55 AM, "christofer.d...@c-ware.de"
 wrote:

>Hi Guys :-)
>
>Today I think I reached an important milestone with my
>generator-maven-plugin. This will definitely need some fine-tuning, but I
>think I'll do that on the way. At least now I can generate any form of
>code from any sort of Java Class File or Source File. That was the big
>step I needed in order to continue with the maven-flex-plugin (By the way
>... am I allowed to name it that way? The "maven" prefix of a plugin
>seems to be reserved for official maven plugins supported by Apache ...
>so I guess it should be ok).
I would recommend asking at trademarks@a.o

>
>I was intending on supporting only the falcon compiler and would start to
>support only Apache Flex and FlexUnit first (No need for high blood
>preasure ... the other stuff should come as the plugin matures). Think I
>will be needing quite some input from anyone on the Falcon Compiler team.
>Is there any sort of documentation for using and configuring the compiler
>programmatically (not using the intermediate commandline)?
How do you interact with the current MXMLC programmatically?  Is there an
API or are you just using -config.xml files?

-Alex

AW: BlazeDS Software Grant was sent to Apache today.

[christofer.d...@c-ware.de]

Yay!!! ... Finally :-)

Really looking forward to streaming amf connections using asynchronous IO :-)

Chris


Von: Alex Harui [aha...@adobe.com]
Gesendet: Freitag, 2. August 2013 07:16
An: dev@flex.apache.org
Betreff: BlazeDS Software Grant was sent to Apache today.

Once the grant is recorded, we'll start in on moving the code over.  I think 
we're just going to take it without SVN history.  Extracting SVN history from 
opensource.adobe.com is quite painful.  Let me know if you disagree.

That should mean one less option and download in the installer and build 
scripts in releases after 4.10.0.

Many thanks to the BlazeDS team at Adobe for slogging through a difficult IP 
clearance process.

-Alex

Maven-Flex-Plugin WAS: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

[christofer.d...@c-ware.de]

Hi Guys :-)

Today I think I reached an important milestone with my generator-maven-plugin. 
This will definitely need some fine-tuning, but I think I'll do that on the 
way. At least now I can generate any form of code from any sort of Java Class 
File or Source File. That was the big step I needed in order to continue with 
the maven-flex-plugin (By the way ... am I allowed to name it that way? The 
"maven" prefix of a plugin seems to be reserved for official maven plugins 
supported by Apache ... so I guess it should be ok).

I was intending on supporting only the falcon compiler and would start to 
support only Apache Flex and FlexUnit first (No need for high blood preasure 
... the other stuff should come as the plugin matures). Think I will be needing 
quite some input from anyone on the Falcon Compiler team. Is there any sort of 
documentation for using and configuring the compiler programmatically (not 
using the intermediate commandline)?

Chris
 

-Ursprüngliche Nachricht-
Von: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] Im Auftrag von 
Carlos Rovira
Gesendet: Mittwoch, 31. Juli 2013 16:23
An: dev@flex.apache.org
Betreff: Re: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

Hi Chris,

yeah! Thanks to the big effort you and Jose made combined with latest IntelliJ 
IDEA 13 EAP bug fixes, I think we finaly has a dream enviroment to develop 
with. There's space to improvements and better workflows but I definitely think 
we reach an important milestone :)

As I said, I trying to get time to mavenize falcon and then flexjs and reach a 
point where we can introduce Stage3D / Starling Framework - we already have 
this one! ;) -. I'm in the believe that this are the kind of things that make 
the difference between Apache Flex and the plethora of javascript frameworks 
out there.

Thanks for all the hard work behind flexmojos 6.0.1 Chris! :)


2013/7/31 christofer.d...@c-ware.de 

> I'm happy that FM 6.0.1 seems to be working without any major hickups 
> :-)
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] Im 
> Auftrag von Carlos Rovira
> Gesendet: Dienstag, 30. Juli 2013 15:28
> An: dev@flex.apache.org
> Betreff: Re: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1
>
> Hi,
>
> just let you know that my pull request was accepted and now Apache 
> Flex
> 4.9.1 and Flexmojos 6.0.1 is the base of the starling framework maven 
> build
>
> :)
>
> Carlos
>
>
> 2013/7/30 Carlos Rovira 
>
> > Hi,
> >
> > just let you know that I made a pull request to starling framework 
> > to upgrade to flexmojos 6.0.1 and Apache Flex for building starling 
> > maven artifact.
> >
> > https://github.com/PrimaryFeather/Starling-Framework/pull/372
> >
> > still if anyone knowns something about the "Adobe" text info in the 
> > swf tag I was referring in my email and can help to unveil the 
> > mystery that is welcome :)
> >
> > Best
> >
> > Carlos
> >
> > 2013/7/29 Carlos Rovira 
> >
> >> This is the public link to my screenshot that was not attached in 
> >> my
> >> email:
> >>
> >>
> >> https://dl.dropboxusercontent.com/u/8496144/swfinspector_starlingap
> >> ac
> >> heflex_491.png
> >>
> >>
> >>
> >> 2013/7/29 Carlos Rovira 
> >>
> >>> Hi,
> >>>
> >>> I was trying to build Starling Framework with flexmojos 6.0.1 
> >>> upgrading the starling pom from 4.6.0 to 4.9.1 and testing 
> >>> IntelliJ new Cardea EAP where we finally get the fix to build with 
> >>> flexmojos
> Apache Flex SDK.
> >>>
> >>> All seems to go ok and I get successful compilation in both ways:
> >>> running pom and using "Make" with IntelliJ. This is very good news 
> >>> since we really have an IDE that supports Apache Flex SDK with 
> >>> maven using new flexmojos 6.0.1 version and is not tied to adobe 
> >>> namespace.
> >>>
> >>> To see that output is ok I use SWFInspector to search inside 
> >>> library.swf inside the generated starling output swc library
> >>>
> >>> And I see this tag (see attached screenshot capture)
> >>>
> >>>  >>> build='1447119' compileDate='Mon Jul 29 09:56:41 2013 UTC'/>
> >>>
> >>> Seems all is ok with version numbers but ProductInfo is "Adobe Flex"
> >>> instead of "Apache Flex".
> >>>
> >>> It seems that there's some "Adobe" literal yet i

AW: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

[christofer.d...@c-ware.de]

I'm happy that FM 6.0.1 seems to be working without any major hickups :-)

Chris


-Ursprüngliche Nachricht-
Von: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] Im Auftrag von 
Carlos Rovira
Gesendet: Dienstag, 30. Juli 2013 15:28
An: dev@flex.apache.org
Betreff: Re: IntelliJ - ApacheFlex4.9.1 - flexmojos 6.0.1

Hi,

just let you know that my pull request was accepted and now Apache Flex
4.9.1 and Flexmojos 6.0.1 is the base of the starling framework maven build

:)

Carlos


2013/7/30 Carlos Rovira 

> Hi,
>
> just let you know that I made a pull request to starling framework to 
> upgrade to flexmojos 6.0.1 and Apache Flex for building starling maven 
> artifact.
>
> https://github.com/PrimaryFeather/Starling-Framework/pull/372
>
> still if anyone knowns something about the "Adobe" text info in the 
> swf tag I was referring in my email and can help to unveil the mystery 
> that is welcome :)
>
> Best
>
> Carlos
>
> 2013/7/29 Carlos Rovira 
>
>> This is the public link to my screenshot that was not attached in my
>> email:
>>
>>
>> https://dl.dropboxusercontent.com/u/8496144/swfinspector_starlingapac
>> heflex_491.png
>>
>>
>>
>> 2013/7/29 Carlos Rovira 
>>
>>> Hi,
>>>
>>> I was trying to build Starling Framework with flexmojos 6.0.1 
>>> upgrading the starling pom from 4.6.0 to 4.9.1 and testing IntelliJ 
>>> new Cardea EAP where we finally get the fix to build with flexmojos Apache 
>>> Flex SDK.
>>>
>>> All seems to go ok and I get successful compilation in both ways:
>>> running pom and using "Make" with IntelliJ. This is very good news 
>>> since we really have an IDE that supports Apache Flex SDK with maven 
>>> using new flexmojos 6.0.1 version and is not tied to adobe namespace.
>>>
>>> To see that output is ok I use SWFInspector to search inside 
>>> library.swf inside the generated starling output swc library
>>>
>>> And I see this tag (see attached screenshot capture)
>>>
>>> >> build='1447119' compileDate='Mon Jul 29 09:56:41 2013 UTC'/>
>>>
>>> Seems all is ok with version numbers but ProductInfo is "Adobe Flex"
>>> instead of "Apache Flex".
>>>
>>> It seems that there's some "Adobe" literal yet in the SDK code? 
>>> Someone knows what could be happen?
>>>
>>> Thanks
>>>
>>>
>>> --
>>> Carlos Rovira
>>> Director de Tecnología
>>> M: +34 607 22 60 05
>>> F:  +34 912 94 80 80
>>> http://www.codeoscopic.com
>>> http://www.directwriter.es
>>> http://www.avant2.es
>>>
>>
>>
>>
>> --
>> Carlos Rovira
>> Director de Tecnología
>> M: +34 607 22 60 05
>> F:  +34 912 94 80 80
>> http://www.codeoscopic.com
>> http://www.directwriter.es
>> http://www.avant2.es
>>
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F:  +34 912 94 80 80
> http://www.codeoscopic.com
> http://www.directwriter.es
> http://www.avant2.es
>



--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

AW: Trying to mavenize project flex-asjs with IntelliJ fails

[christofer.d...@c-ware.de]

Yay!!! Glad it worked :)

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] 
Gesendet: Samstag, 13. Juli 2013 17:04
An: dev@flex.apache.org
Betreff: Re: Trying to mavenize project flex-asjs with IntelliJ fails

Anyway, I rebuilt my whiteboard project with FM6.0.1 successfully !

-Message d'origine-
From: Frédéric THOMAS
Sent: Saturday, July 13, 2013 4:30 PM
To: dev@flex.apache.org
Subject: Re: AW: AW: AW: Trying to mavenize project flex-asjs with IntelliJ 
fails

Oh maybe I didn't get what you meant, was you talking about create a simple 
project to demonstrate your fix works or something else ?

-Fred

-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Saturday, July 13, 2013 4:02 PM
To: dev@flex.apache.org
Subject: AW: AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

But you probably have them in 6.1.0 and these are in version 6.0.1 ;-)

Chris

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Gesendet: Samstag, 13. Juli 2013 16:00
An: dev@flex.apache.org
Betreff: Re: AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Well, as you may guess, I've got all of them too, so, maybe someone else could 
give it a try ?

-Fred

-Message d'origine-----
From: christofer.d...@c-ware.de
Sent: Saturday, July 13, 2013 3:54 PM
To: dev@flex.apache.org
Subject: AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Would be cool if you could give it a test-drive ;-) Strangely I have all the 
stuff available in all my repos  would be cool if someone could check if it 
really worked.

Chris

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Gesendet: Samstag, 13. Juli 2013 15:52
An: dev@flex.apache.org
Betreff: Re: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Nice, thanks :-)

-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Saturday, July 13, 2013 3:48 PM
To: dev@flex.apache.org
Subject: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ... so it's done ... Flexmojos 6.0.1 is available in the Sonatype public 
repo ... think it might take some time to reach maven central repo.
https://oss.sonatype.org/content/repositories/releases/net/flexmojos/oss/flexmojos-parent/6.0.1/flexmojos-parent-6.0.1.pom

Have phun,
Chris

PS: Releasing FM is a real PITA ... hopefully this will become a lot easier 
with the new plugin.

-Ursprüngliche Nachricht-
Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Gesendet: Freitag, 12. Juli 2013 16:33
An: dev@flex.apache.org
Betreff: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ok you got me ;-)

think I'll go home now and start the release process for FM6.0.1

I see this is a serious Problem for People and after all, I want the People to 
be able to use it without Problems ;-)

Chris



Von: carlos.rov...@gmail.com [carlos.rov...@gmail.com] im Auftrag von Carlos 
Rovira [carlos.rov...@codeoscopic.com]
Gesendet: Freitag, 12. Juli 2013 10:33
An: dev@flex.apache.org
Betreff: Re: Trying to mavenize project flex-asjs with IntelliJ fails

Hi Frederic,

I just see your comment in you track first and responded there.

As I stated there, I think my environment is slight different since:

a) I have a internal flexmojos version 6.1 deployed with the fix Chris Dutz 
made. Jose Barragan deployed it to our internal repository for testing since 
he's working closely with Chris.
This fixes the namespace dependency problem from "com.adobe*" to "org.apache"

b) I have all SDKs from com.adobe and org.apache deployed starting from 2.x.x.x 
to 4.9.1.x

At maven level it seems to work all ok, but at IntelliJ level I have the 
commented problem with the autogeneration of flexmojos SDK. If I use com.adobe 
and 4.6 all works. If I use org.apache and 4.9.1 IntelliJ is not capable of 
generating the internal reference of flexmojos sdk 4.9.1

I think it will be important to have flexmojos 6.1 released soon since the 
solved bug is very important since is a real stopper for people wanting to use 
flexmojos with apache flex sdk.

Thanks

Carlos




2013/7/12 Frédéric THOMAS 

> The good links can be found here [1] [2], maybe someone would like to 
> add them to the wiki.
>
> [1]
> Find & Use FM6:
> https://oss.sonatype.org/**index.html#nexus-search;gav~**
> net.flexmojos.oss~flexmojos-**maven-plugin~~~<https://oss.sonatype.org
> /index.html#nexus-search;gav~net.flexmojos.oss~flexmojos-maven-plugin~
> ~~>
> https://git-wip-us.apache.org/**repos/asf?p=flex-utilities.**
> git;a=blob;f=mavenizer/README.**txt;h=**d962139fb50f787f608a6f84a94335
> **
> 5153306edc;hb=HEAD<https://git-wip-us.apache.org/repos/asf?p=flex-util
> ities.git;a=blob;f=mavenizer/README.txt;h=d962139fb50f787f

AW: AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

[christofer.d...@c-ware.de]

But you probably have them in 6.1.0 and these are in version 6.0.1 ;-)

Chris

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] 
Gesendet: Samstag, 13. Juli 2013 16:00
An: dev@flex.apache.org
Betreff: Re: AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Well, as you may guess, I've got all of them too, so, maybe someone else could 
give it a try ?

-Fred

-Message d'origine-----
From: christofer.d...@c-ware.de
Sent: Saturday, July 13, 2013 3:54 PM
To: dev@flex.apache.org
Subject: AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Would be cool if you could give it a test-drive ;-) Strangely I have all the 
stuff available in all my repos  would be cool if someone could check if it 
really worked.

Chris

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Gesendet: Samstag, 13. Juli 2013 15:52
An: dev@flex.apache.org
Betreff: Re: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Nice, thanks :-)

-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Saturday, July 13, 2013 3:48 PM
To: dev@flex.apache.org
Subject: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ... so it's done ... Flexmojos 6.0.1 is available in the Sonatype public 
repo ... think it might take some time to reach maven central repo.
https://oss.sonatype.org/content/repositories/releases/net/flexmojos/oss/flexmojos-parent/6.0.1/flexmojos-parent-6.0.1.pom

Have phun,
Chris

PS: Releasing FM is a real PITA ... hopefully this will become a lot easier 
with the new plugin.

-Ursprüngliche Nachricht-----
Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Gesendet: Freitag, 12. Juli 2013 16:33
An: dev@flex.apache.org
Betreff: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ok you got me ;-)

think I'll go home now and start the release process for FM6.0.1

I see this is a serious Problem for People and after all, I want the People to 
be able to use it without Problems ;-)

Chris



Von: carlos.rov...@gmail.com [carlos.rov...@gmail.com] im Auftrag von Carlos 
Rovira [carlos.rov...@codeoscopic.com]
Gesendet: Freitag, 12. Juli 2013 10:33
An: dev@flex.apache.org
Betreff: Re: Trying to mavenize project flex-asjs with IntelliJ fails

Hi Frederic,

I just see your comment in you track first and responded there.

As I stated there, I think my environment is slight different since:

a) I have a internal flexmojos version 6.1 deployed with the fix Chris Dutz 
made. Jose Barragan deployed it to our internal repository for testing since 
he's working closely with Chris.
This fixes the namespace dependency problem from "com.adobe*" to "org.apache"

b) I have all SDKs from com.adobe and org.apache deployed starting from 2.x.x.x 
to 4.9.1.x

At maven level it seems to work all ok, but at IntelliJ level I have the 
commented problem with the autogeneration of flexmojos SDK. If I use com.adobe 
and 4.6 all works. If I use org.apache and 4.9.1 IntelliJ is not capable of 
generating the internal reference of flexmojos sdk 4.9.1

I think it will be important to have flexmojos 6.1 released soon since the 
solved bug is very important since is a real stopper for people wanting to use 
flexmojos with apache flex sdk.

Thanks

Carlos




2013/7/12 Frédéric THOMAS 

> The good links can be found here [1] [2], maybe someone would like to 
> add them to the wiki.
>
> [1]
> Find & Use FM6:
> https://oss.sonatype.org/**index.html#nexus-search;gav~**
> net.flexmojos.oss~flexmojos-**maven-plugin~~~<https://oss.sonatype.org
> /index.html#nexus-search;gav~net.flexmojos.oss~flexmojos-maven-plugin~
> ~~>
> https://git-wip-us.apache.org/**repos/asf?p=flex-utilities.**
> git;a=blob;f=mavenizer/README.**txt;h=**d962139fb50f787f608a6f84a94335
> **
> 5153306edc;hb=HEAD<https://git-wip-us.apache.org/repos/asf?p=flex-util
> ities.git;a=blob;f=mavenizer/README.txt;h=d962139fb50f787f608a6f84a943
> 355153306edc;hb=HEAD>
> https://flexmojos.atlassian.**net/wiki/display/FLEXMOJOS/**Flexmojos+6
> .x<https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Flexmojos+6.
> x>
>
> [2]
> Building FM6:
> https://github.com/chrisdutz/**flexmojos<https://github.com/chrisdutz/
> flexmojos>
> https://docs.sonatype.org/**display/FLEXMOJOS/Building+**
> Flexmojos+from+sources<https://docs.sonatype.org/display/FLEXMOJOS/Bui
> Flexmojos+from+lding+Flexmojos+from+sources>
>
> And as I stated before, you can check my whiteboard (fthomas) to get a 
> model of pom.xml built for air/swf/swc using FM6 and a recent Apache 
> Flex SDK, that's an Air project but still, it might help.
>
> -Fred
>
> -Message d'origine- From: Gary Young
> Sent: Friday, July 12, 2013 4:34 AM
> To: 

AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

[christofer.d...@c-ware.de]

Would be cool if you could give it a test-drive ;-)
Strangely I have all the stuff available in all my repos  would be cool if 
someone could check if it really worked.

Chris

-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] 
Gesendet: Samstag, 13. Juli 2013 15:52
An: dev@flex.apache.org
Betreff: Re: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Nice, thanks :-)

-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Saturday, July 13, 2013 3:48 PM
To: dev@flex.apache.org
Subject: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ... so it's done ... Flexmojos 6.0.1 is available in the Sonatype public 
repo ... think it might take some time to reach maven central repo.
https://oss.sonatype.org/content/repositories/releases/net/flexmojos/oss/flexmojos-parent/6.0.1/flexmojos-parent-6.0.1.pom

Have phun,
Chris

PS: Releasing FM is a real PITA ... hopefully this will become a lot easier 
with the new plugin.

-Ursprüngliche Nachricht-
Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Gesendet: Freitag, 12. Juli 2013 16:33
An: dev@flex.apache.org
Betreff: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ok you got me ;-)

think I'll go home now and start the release process for FM6.0.1

I see this is a serious Problem for People and after all, I want the People to 
be able to use it without Problems ;-)

Chris



Von: carlos.rov...@gmail.com [carlos.rov...@gmail.com] im Auftrag von Carlos 
Rovira [carlos.rov...@codeoscopic.com]
Gesendet: Freitag, 12. Juli 2013 10:33
An: dev@flex.apache.org
Betreff: Re: Trying to mavenize project flex-asjs with IntelliJ fails

Hi Frederic,

I just see your comment in you track first and responded there.

As I stated there, I think my environment is slight different since:

a) I have a internal flexmojos version 6.1 deployed with the fix Chris Dutz 
made. Jose Barragan deployed it to our internal repository for testing since 
he's working closely with Chris.
This fixes the namespace dependency problem from "com.adobe*" to "org.apache"

b) I have all SDKs from com.adobe and org.apache deployed starting from 2.x.x.x 
to 4.9.1.x

At maven level it seems to work all ok, but at IntelliJ level I have the 
commented problem with the autogeneration of flexmojos SDK. If I use com.adobe 
and 4.6 all works. If I use org.apache and 4.9.1 IntelliJ is not capable of 
generating the internal reference of flexmojos sdk 4.9.1

I think it will be important to have flexmojos 6.1 released soon since the 
solved bug is very important since is a real stopper for people wanting to use 
flexmojos with apache flex sdk.

Thanks

Carlos




2013/7/12 Frédéric THOMAS 

> The good links can be found here [1] [2], maybe someone would like to 
> add them to the wiki.
>
> [1]
> Find & Use FM6:
> https://oss.sonatype.org/**index.html#nexus-search;gav~**
> net.flexmojos.oss~flexmojos-**maven-plugin~~~<https://oss.sonatype.org
> /index.html#nexus-search;gav~net.flexmojos.oss~flexmojos-maven-plugin~
> ~~>
> https://git-wip-us.apache.org/**repos/asf?p=flex-utilities.**
> git;a=blob;f=mavenizer/README.**txt;h=**d962139fb50f787f608a6f84a94335
> **
> 5153306edc;hb=HEAD<https://git-wip-us.apache.org/repos/asf?p=flex-util
> ities.git;a=blob;f=mavenizer/README.txt;h=d962139fb50f787f608a6f84a943
> 355153306edc;hb=HEAD>
> https://flexmojos.atlassian.**net/wiki/display/FLEXMOJOS/**Flexmojos+6
> .x<https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Flexmojos+6.
> x>
>
> [2]
> Building FM6:
> https://github.com/chrisdutz/**flexmojos<https://github.com/chrisdutz/
> flexmojos>
> https://docs.sonatype.org/**display/FLEXMOJOS/Building+**
> Flexmojos+from+sources<https://docs.sonatype.org/display/FLEXMOJOS/Bui
> Flexmojos+from+lding+Flexmojos+from+sources>
>
> And as I stated before, you can check my whiteboard (fthomas) to get a 
> model of pom.xml built for air/swf/swc using FM6 and a recent Apache 
> Flex SDK, that's an Air project but still, it might help.
>
> -Fred
>
> -Message d'origine- From: Gary Young
> Sent: Friday, July 12, 2013 4:34 AM
> To: dev@flex.apache.org
> Subject: Re: Trying to mavenize project flex-asjs with IntelliJ fails
>
>
> I am still using Flexmojos 3.9+ Flex 4.6+AIR3.1, I want to use the 
> most recent version, it just won't work. I have to exclude old 
> playerglobal.swc and include new version in pom. -Gary
>
>
> On Thu, Jul 11, 2013 at 7:43 PM, Frédéric THOMAS 
> 
> **wrote:
>
>  It has been answered
> http://youtrack.jetbrains.com/issue/IDEA-110462<http://youtrack.je
> tbrains.com/**issue/IDEA-110462>
>> <http://**youtrack.jetbrains.com/issue/**IDEA-110462<htt

AW: Trying to mavenize project flex-asjs with IntelliJ fails

[christofer.d...@c-ware.de]

Ok ... so it's done ... Flexmojos 6.0.1 is available in the Sonatype public 
repo ... think it might take some time to reach maven central repo.
https://oss.sonatype.org/content/repositories/releases/net/flexmojos/oss/flexmojos-parent/6.0.1/flexmojos-parent-6.0.1.pom

Have phun,
Chris

PS: Releasing FM is a real PITA ... hopefully this will become a lot easier 
with the new plugin.

-Ursprüngliche Nachricht-
Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] 
Gesendet: Freitag, 12. Juli 2013 16:33
An: dev@flex.apache.org
Betreff: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ok you got me ;-)

think I'll go home now and start the release process for FM6.0.1

I see this is a serious Problem for People and after all, I want the People to 
be able to use it without Problems ;-)

Chris



Von: carlos.rov...@gmail.com [carlos.rov...@gmail.com] im Auftrag von Carlos 
Rovira [carlos.rov...@codeoscopic.com]
Gesendet: Freitag, 12. Juli 2013 10:33
An: dev@flex.apache.org
Betreff: Re: Trying to mavenize project flex-asjs with IntelliJ fails

Hi Frederic,

I just see your comment in you track first and responded there.

As I stated there, I think my environment is slight different since:

a) I have a internal flexmojos version 6.1 deployed with the fix Chris Dutz 
made. Jose Barragan deployed it to our internal repository for testing since 
he's working closely with Chris.
This fixes the namespace dependency problem from "com.adobe*" to "org.apache"

b) I have all SDKs from com.adobe and org.apache deployed starting from 2.x.x.x 
to 4.9.1.x

At maven level it seems to work all ok, but at IntelliJ level I have the 
commented problem with the autogeneration of flexmojos SDK. If I use com.adobe 
and 4.6 all works. If I use org.apache and 4.9.1 IntelliJ is not capable of 
generating the internal reference of flexmojos sdk 4.9.1

I think it will be important to have flexmojos 6.1 released soon since the 
solved bug is very important since is a real stopper for people wanting to use 
flexmojos with apache flex sdk.

Thanks

Carlos




2013/7/12 Frédéric THOMAS 

> The good links can be found here [1] [2], maybe someone would like to 
> add them to the wiki.
>
> [1]
> Find & Use FM6:
> https://oss.sonatype.org/**index.html#nexus-search;gav~**
> net.flexmojos.oss~flexmojos-**maven-plugin~~~<https://oss.sonatype.org
> /index.html#nexus-search;gav~net.flexmojos.oss~flexmojos-maven-plugin~
> ~~>
> https://git-wip-us.apache.org/**repos/asf?p=flex-utilities.**
> git;a=blob;f=mavenizer/README.**txt;h=**d962139fb50f787f608a6f84a94335
> ** 
> 5153306edc;hb=HEAD<https://git-wip-us.apache.org/repos/asf?p=flex-util
> ities.git;a=blob;f=mavenizer/README.txt;h=d962139fb50f787f608a6f84a943
> 355153306edc;hb=HEAD> 
> https://flexmojos.atlassian.**net/wiki/display/FLEXMOJOS/**Flexmojos+6
> .x<https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Flexmojos+6.
> x>
>
> [2]
> Building FM6:
> https://github.com/chrisdutz/**flexmojos<https://github.com/chrisdutz/
> flexmojos>
> https://docs.sonatype.org/**display/FLEXMOJOS/Building+**
> Flexmojos+from+sources<https://docs.sonatype.org/display/FLEXMOJOS/Bui
> Flexmojos+from+lding+Flexmojos+from+sources>
>
> And as I stated before, you can check my whiteboard (fthomas) to get a 
> model of pom.xml built for air/swf/swc using FM6 and a recent Apache 
> Flex SDK, that's an Air project but still, it might help.
>
> -Fred
>
> -Message d'origine- From: Gary Young
> Sent: Friday, July 12, 2013 4:34 AM
> To: dev@flex.apache.org
> Subject: Re: Trying to mavenize project flex-asjs with IntelliJ fails
>
>
> I am still using Flexmojos 3.9+ Flex 4.6+AIR3.1, I want to use the 
> most recent version, it just won't work. I have to exclude old 
> playerglobal.swc and include new version in pom. -Gary
>
>
> On Thu, Jul 11, 2013 at 7:43 PM, Frédéric THOMAS 
> 
> **wrote:
>
>  It has been answered 
> http://youtrack.jetbrains.com/issue/IDEA-110462<http://youtrack.je
> tbrains.com/**issue/IDEA-110462>
>> <http://**youtrack.jetbrains.com/issue/**IDEA-110462<http://youtrack.
>> jetbrains.com/issue/IDEA-110462>
>> >
>>
>> Check my whiteboard (fthomas) to get a model of a pom.xml building 
>> for air/swf/swc using FM6 and a recent Apache Flex SDK (replace it by 
>> 4.9.1), that's an Air project but still, it might help.
>>
>> -Fred
>>
>> -Message d'origine- From: Carlos Rovira
>> Sent: Thursday, July 11, 2013 10:47 PM
>> To: dev@flex.apache.org
>> Subject: Trying to mavenize project flex-asjs with IntelliJ fails
>>
>>
>> Hi,
>>

AW: AW: Trying to mavenize project flex-asjs with IntelliJ fails

[christofer.d...@c-ware.de]

Hi Fred,

Actually FLEXMOJOS-878 will be almost the only thing it will contain. That's 
why I don't think a 6.1 would be appropriate ;-)
Not many bugs have been reported lately. Don't know if this is because of Velo 
not letting any posts pass in the list or simply no one is having any trouble 
or no one is using FM ;-)

There will be nothing I can do about the group id thing. I could switch FM 
entirely to the apache group id, but I would have to disable big parts of FM as 
I can only support one of the group ids.

It was my intention to create a completely new Flex Maven plugin and am 
currently working on a universal Maven code generator plugin that I will use to 
build that plugin, but it's quite some work, but I'm making good progress :-) 
As soon as that's done, I can continue my work on the flex plugin.

Chris



-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] 
Gesendet: Freitag, 12. Juli 2013 17:27
An: dev@flex.apache.org
Betreff: Re: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Well, actually this minor version (6.0.1) will include FLEXMOJOS-878 + What you 
are doing at the moment with Carlos and Jose about the "org.apache" 
groupId prefix, right ?

-Fred

-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Friday, July 12, 2013 4:32 PM
To: dev@flex.apache.org
Subject: AW: Trying to mavenize project flex-asjs with IntelliJ fails

Ok ok you got me ;-)

think I'll go home now and start the release process for FM6.0.1

I see this is a serious Problem for People and after all, I want the People to 
be able to use it without Problems ;-)

Chris



Von: carlos.rov...@gmail.com [carlos.rov...@gmail.com] im Auftrag von Carlos 
Rovira [carlos.rov...@codeoscopic.com]
Gesendet: Freitag, 12. Juli 2013 10:33
An: dev@flex.apache.org
Betreff: Re: Trying to mavenize project flex-asjs with IntelliJ fails

Hi Frederic,

I just see your comment in you track first and responded there.

As I stated there, I think my environment is slight different since:

a) I have a internal flexmojos version 6.1 deployed with the fix Chris Dutz 
made. Jose Barragan deployed it to our internal repository for testing since 
he's working closely with Chris.
This fixes the namespace dependency problem from "com.adobe*" to "org.apache"

b) I have all SDKs from com.adobe and org.apache deployed starting from 2.x.x.x 
to 4.9.1.x

At maven level it seems to work all ok, but at IntelliJ level I have the 
commented problem with the autogeneration of flexmojos SDK. If I use com.adobe 
and 4.6 all works. If I use org.apache and 4.9.1 IntelliJ is not capable of 
generating the internal reference of flexmojos sdk 4.9.1

I think it will be important to have flexmojos 6.1 released soon since the 
solved bug is very important since is a real stopper for people wanting to use 
flexmojos with apache flex sdk.

Thanks

Carlos




2013/7/12 Frédéric THOMAS 

> The good links can be found here [1] [2], maybe someone would like to 
> add them to the wiki.
>
> [1]
> Find & Use FM6:
> https://oss.sonatype.org/**index.html#nexus-search;gav~**
> net.flexmojos.oss~flexmojos-**maven-plugin~~~<https://oss.sonatype.org
> /index.html#nexus-search;gav~net.flexmojos.oss~flexmojos-maven-plugin~
> ~~>
> https://git-wip-us.apache.org/**repos/asf?p=flex-utilities.**
> git;a=blob;f=mavenizer/README.**txt;h=**d962139fb50f787f608a6f84a94335
> ** 
> 5153306edc;hb=HEAD<https://git-wip-us.apache.org/repos/asf?p=flex-util
> ities.git;a=blob;f=mavenizer/README.txt;h=d962139fb50f787f608a6f84a943
> 355153306edc;hb=HEAD> 
> https://flexmojos.atlassian.**net/wiki/display/FLEXMOJOS/**Flexmojos+6
> .x<https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Flexmojos+6.
> x>
>
> [2]
> Building FM6:
> https://github.com/chrisdutz/**flexmojos<https://github.com/chrisdutz/
> flexmojos>
> https://docs.sonatype.org/**display/FLEXMOJOS/Building+**
> Flexmojos+from+sources<https://docs.sonatype.org/display/FLEXMOJOS/Bui
> Flexmojos+from+lding+Flexmojos+from+sources>
>
> And as I stated before, you can check my whiteboard (fthomas) to get a 
> model of pom.xml built for air/swf/swc using FM6 and a recent Apache 
> Flex SDK, that's an Air project but still, it might help.
>
> -Fred
>
> -Message d'origine- From: Gary Young
> Sent: Friday, July 12, 2013 4:34 AM
> To: dev@flex.apache.org
> Subject: Re: Trying to mavenize project flex-asjs with IntelliJ fails
>
>
> I am still using Flexmojos 3.9+ Flex 4.6+AIR3.1, I want to use the 
> most recent version, it just won't work. I have to exclude old 
> playerglobal.swc and include new version in pom. -Gary
>
>
> On Thu, Jul 11, 2013 at 7:43 PM, Frédéric THOMAS 
> 
> **wrot

AW: Trying to mavenize project flex-asjs with IntelliJ fails

[christofer.d...@c-ware.de]

Ok ok you got me ;-)

think I'll go home now and start the release process for FM6.0.1

I see this is a serious Problem for People and after all, I want the People to 
be able to use it without Problems ;-)

Chris



Von: carlos.rov...@gmail.com [carlos.rov...@gmail.com] im Auftrag von Carlos 
Rovira [carlos.rov...@codeoscopic.com]
Gesendet: Freitag, 12. Juli 2013 10:33
An: dev@flex.apache.org
Betreff: Re: Trying to mavenize project flex-asjs with IntelliJ fails

Hi Frederic,

I just see your comment in you track first and responded there.

As I stated there, I think my environment is slight different since:

a) I have a internal flexmojos version 6.1 deployed with the fix Chris Dutz
made. Jose Barragan deployed it to our internal repository for testing
since he's working closely with Chris.
This fixes the namespace dependency problem from "com.adobe*" to
"org.apache"

b) I have all SDKs from com.adobe and org.apache deployed starting from
2.x.x.x to 4.9.1.x

At maven level it seems to work all ok, but at IntelliJ level I have the
commented problem with the autogeneration of flexmojos SDK. If I use
com.adobe and 4.6 all works. If I use org.apache and 4.9.1
IntelliJ is not capable of generating the internal reference of flexmojos
sdk 4.9.1

I think it will be important to have flexmojos 6.1 released soon since the
solved bug is very important since is a real stopper for people wanting to
use flexmojos with apache flex sdk.

Thanks

Carlos




2013/7/12 Frédéric THOMAS 

> The good links can be found here [1] [2], maybe someone would like to add
> them to the wiki.
>
> [1]
> Find & Use FM6:
> https://oss.sonatype.org/**index.html#nexus-search;gav~**
> net.flexmojos.oss~flexmojos-**maven-plugin~~~
> https://git-wip-us.apache.org/**repos/asf?p=flex-utilities.**
> git;a=blob;f=mavenizer/README.**txt;h=**d962139fb50f787f608a6f84a94335**
> 5153306edc;hb=HEAD
> https://flexmojos.atlassian.**net/wiki/display/FLEXMOJOS/**Flexmojos+6.x
>
> [2]
> Building FM6:
> https://github.com/chrisdutz/**flexmojos
> https://docs.sonatype.org/**display/FLEXMOJOS/Building+**
> Flexmojos+from+sources
>
> And as I stated before, you can check my whiteboard (fthomas) to get a
> model of pom.xml built for air/swf/swc using FM6 and a recent Apache Flex
> SDK, that's an Air project but still, it might help.
>
> -Fred
>
> -Message d'origine- From: Gary Young
> Sent: Friday, July 12, 2013 4:34 AM
> To: dev@flex.apache.org
> Subject: Re: Trying to mavenize project flex-asjs with IntelliJ fails
>
>
> I am still using Flexmojos 3.9+ Flex 4.6+AIR3.1, I want to use the most
> recent version, it just won't work. I have to exclude old playerglobal.swc
> and include new version in pom. -Gary
>
>
> On Thu, Jul 11, 2013 at 7:43 PM, Frédéric THOMAS 
> **wrote:
>
>  It has been answered 
> http://youtrack.jetbrains.com/issue/IDEA-110462
>> 
>> >
>>
>> Check my whiteboard (fthomas) to get a model of a pom.xml building for
>> air/swf/swc using FM6 and a recent Apache Flex SDK (replace it by 4.9.1),
>> that's an Air project but still, it might help.
>>
>> -Fred
>>
>> -Message d'origine- From: Carlos Rovira
>> Sent: Thursday, July 11, 2013 10:47 PM
>> To: dev@flex.apache.org
>> Subject: Trying to mavenize project flex-asjs with IntelliJ fails
>>
>>
>> Hi,
>>
>> I'm trying to create a project in IntelliJ for flex-asjs with mavenized
>> SDK 4.9.1.1447119
>> But seems that IDEA can't generate Apache Flex SDK from pom.xml. It works
>> for Adobe Flex SDKs but not for Apache Flex.
>>
>> I created a youtrack ticket:
>>
>> http://youtrack.jetbrains.com/issues/IDEA#
>> 
>> >
>>
>> I'm missing something or it's really a bug?
>>
>> In the ticket I attached a draft of the pom.xml
>>
>> If you get the same error please vote the ticket
>>
>> --
>> Carlos Rovira
>>
>>
>


--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

AW: AW: [jira] [Commented] (FLEX-33086) Make SDK build with Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven repository

[christofer.d...@c-ware.de]

Hi Frederic ...

I'll have a look into this ... I agree that I should release that pretty soon 
... but I guess it will be a 6.0.1 ... don't want the People to Think there is 
something new in this release ;-)

Fortunately I have been making quite good Progress with my 
maven-generator-plugin and I will be able to continue my work on the 
maven-flex-plugin ... really looking forward to this.

Chris



Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Donnerstag, 4. Juli 2013 17:48
An: dev@flex.apache.org
Betreff: Re: AW: [jira] [Commented] (FLEX-33086) Make SDK build with 
Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven 
repository

Hi Chris,

What about deploying the the 6.1.0-SNAPSHOT to the snapshot Sonatype repo if
you don't want to have the burden to release ?

-Fred

-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Monday, June 17, 2013 1:05 PM
To: dev@flex.apache.org
Subject: AW: [jira] [Commented] (FLEX-33086) Make SDK build with
Maven/Flexmojos and deploy release and snapshot artifacts to the Apache
Maven repository

Well if there aren't any other things that should be fixed, perhaps I should
do a 6.0.1 release.
Just didn't want do to such a minor release just to do it again the next
week ;-)

And the Problem of deploying the FDKs are not a technical Problem but a
licensing one ;-)

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Sonntag, 16. Juni 2013 08:48
An: dev@flex.apache.org
Betreff: Re: [jira] [Commented] (FLEX-33086) Make SDK build with
Maven/Flexmojos and deploy release and snapshot artifacts to the Apache
Maven repository

> It seems like flexmojos 6.0.0, deployed to maven central repository,
> working fine with Adobe Flex SDK 4.6.0.23201, but I didn't find a way to
> use it with Apache Flex SDK 4.9.1. Maybe because flexmojos compiled with
> 4.6.0, and working only with it? I think that is not right.

Actually, FM 6.0.1 fixed the things, the problem is that it hadn't been
deployed yet, so you need to build it from the sources and it works well.

For the other part of your topic, yes, until now, because we didn't find a
way to deploy it automatically yet, you will need to mavenized the SDKs too
to be able to use FM.

I hope I answered.

-Fred

-Message d'origine-
From: Rotnov Alexander (JIRA)
Sent: Sunday, June 16, 2013 12:21 AM
To: dev@flex.apache.org
Subject: [jira] [Commented] (FLEX-33086) Make SDK build with Maven/Flexmojos
and deploy release and snapshot artifacts to the Apache Maven repository


[
https://issues.apache.org/jira/browse/FLEX-33086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684427#comment-13684427
]

Rotnov Alexander commented on FLEX-33086:
-

It seems like flexmojos 6.0.0, deployed to maven central repository, working
fine with Adobe Flex SDK 4.6.0.23201, but I didn't find a way to use it with
Apache Flex SDK 4.9.1. Maybe because flexmojos compiled with 4.6.0, and
working only with it? I think that is not right.
By the way, why Flex SDK must be mavenized? So far as I know, Java SDK, for
example, is not needed in this.
Ok, maybe mavenizing Flex SDK is a good simple way to use it. But I can't
understand, why I should mavenize this? Where is no way to deploy release
version of SDK and plugins to maven central repo automaticaly?


> Make SDK build with Maven/Flexmojos and deploy release and snapshot
> artifacts to the Apache Maven repository
> 
>
> Key: FLEX-33086
> URL: https://issues.apache.org/jira/browse/FLEX-33086
> Project: Apache Flex
>  Issue Type: Story
>Reporter: Alex Harui
>  Time Spent: 2h
>  Remaining Estimate: 0h
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

AW: [jira] [Commented] (FLEX-33086) Make SDK build with Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven repository

[christofer.d...@c-ware.de]

Well if there aren't any other things that should be fixed, perhaps I should do 
a 6.0.1 release.
Just didn't want do to such a minor release just to do it again the next week 
;-)

And the Problem of deploying the FDKs are not a technical Problem but a 
licensing one ;-)

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Sonntag, 16. Juni 2013 08:48
An: dev@flex.apache.org
Betreff: Re: [jira] [Commented] (FLEX-33086) Make SDK build with 
Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven 
repository

> It seems like flexmojos 6.0.0, deployed to maven central repository,
> working fine with Adobe Flex SDK 4.6.0.23201, but I didn't find a way to
> use it with Apache Flex SDK 4.9.1. Maybe because flexmojos compiled with
> 4.6.0, and working only with it? I think that is not right.

Actually, FM 6.0.1 fixed the things, the problem is that it hadn't been
deployed yet, so you need to build it from the sources and it works well.

For the other part of your topic, yes, until now, because we didn't find a
way to deploy it automatically yet, you will need to mavenized the SDKs too
to be able to use FM.

I hope I answered.

-Fred

-Message d'origine-
From: Rotnov Alexander (JIRA)
Sent: Sunday, June 16, 2013 12:21 AM
To: dev@flex.apache.org
Subject: [jira] [Commented] (FLEX-33086) Make SDK build with Maven/Flexmojos
and deploy release and snapshot artifacts to the Apache Maven repository


[
https://issues.apache.org/jira/browse/FLEX-33086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684427#comment-13684427
 ]

Rotnov Alexander commented on FLEX-33086:
-

It seems like flexmojos 6.0.0, deployed to maven central repository, working
fine with Adobe Flex SDK 4.6.0.23201, but I didn't find a way to use it with
Apache Flex SDK 4.9.1. Maybe because flexmojos compiled with 4.6.0, and
working only with it? I think that is not right.
By the way, why Flex SDK must be mavenized? So far as I know, Java SDK, for
example, is not needed in this.
Ok, maybe mavenizing Flex SDK is a good simple way to use it. But I can't
understand, why I should mavenize this? Where is no way to deploy release
version of SDK and plugins to maven central repo automaticaly?


> Make SDK build with Maven/Flexmojos and deploy release and snapshot
> artifacts to the Apache Maven repository
> 
>
> Key: FLEX-33086
> URL: https://issues.apache.org/jira/browse/FLEX-33086
> Project: Apache Flex
>  Issue Type: Story
>Reporter: Alex Harui
>  Time Spent: 2h
>  Remaining Estimate: 0h
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

AW: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts and dialogs in FlexJS)

[christofer.d...@c-ware.de]

Regarding the callback-functionality, I would prefer the event based approach 
over the old one where you provide the callbac functionality.

As far as I understood it, I can still programatically create Alerts and 
addEventListeners for the CloseEvents. I would really like to be able to 
continue to be able to create Alerts programatically.

Regarding the discussion of what Buttons the Allert should have, what about 
implementing an abstract BaseAlert (or something similar that contains a 
command-bar which can be filled with Buttons and a concrete subclass Alert that 
mimics the functionality of the original Alert?

Chris


Von: Maxime Cowez [maxime.co...@gmail.com]
Gesendet: Montag, 10. Juni 2013 22:08
An: dev@flex.apache.org
Betreff: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts and 
dialogs in FlexJS)

As we were discussing some options in the thread "Alerts and dialogs in
FlexJS", we started to elaborate on dialog implementation in general. This
was carrying us away from the initial question so I started this new thread.

One of the initial topics was the possibility to declare Alerts/Dialogs as
mxml tags instead of using the old static function, something like this:







I mentioned that I had already created such an implementation, which can be
found at https://github.com/RIAstar/SkinnablePopUpFx
There's also a live demo at http://riastar.github.io/SkinnablePopUpFx/

Some people seemed to like the idea and asked some questions, which I'll
try to answer next.

Max

AW: Thoughts about CSS and Flex

[christofer.d...@c-ware.de]

Something I would certainly like to have woud be the ability to Import other 
CSS files :-)

Chris


Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Freitag, 7. Juni 2013 08:37
An: dev@flex.apache.org
Betreff: Re: Thoughts about CSS and Flex

Hi,

> the CSS support in Flex is highly limited in its present state.

What do you think it's missing?

Flex 4 added a lot of advanced CSS support and it now supports class, type, 
compound, id, descendant and pseudo selectors and media queries.

http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf62883-7ff2.html

Thanks,
Justin

AW: [VOTE] Let's move JIRA emails to a new list

[christofer.d...@c-ware.de]

+1


-Ursprüngliche Nachricht-
Von: Harbs [mailto:harbs.li...@gmail.com] 
Gesendet: Freitag, 31. Mai 2013 16:12
An: dev@flex.apache.org
Betreff: Re: [VOTE] Let's move JIRA emails to a new list

+1

Harbs

AW: BlazeDS

[christofer.d...@c-ware.de]

As far as I know there are a lot of tutorials about creating NIO adapters for 
BlazeDS ... 
The ones out there make use of properitary Jetty features and I have not yet 
come across one generic servlet 3.0 spec endpoint. I would much more prefer to 
start working on such an endpoint. It's something I have on my todo list for 
quite some time now ;-)

Chris

-Ursprüngliche Nachricht-
Von: Nick Collins [mailto:ndcoll...@gmail.com] 
Gesendet: Mittwoch, 29. Mai 2013 23:58
An: dev@flex.apache.org
Betreff: Re: BlazeDS

I may or may not have missed it, but does anyone know if there is any chance of 
the guys at Farata donating their extensions along with BlazeDS that add NIO 
support and such? That would make the Apache BlazeDS even more competitive 
against ADEP DS.

Nick


On Tue, May 28, 2013 at 10:47 PM, Alex Harui  wrote:

> I keep seeing signs that they are making slow progress toward getting 
> it donated.
>
> On 5/28/13 7:48 PM, "Justin Mclean"  wrote:
>
> >HI,
> >
> >A question just come up on the user list about BlazeDS. Alex do you 
> >know if it still likely to be donated?
> >
> >Thanks,
> >Justin
>
>

AW: Jenkins builds and Mustella

[christofer.d...@c-ware.de]

The payment strategy for Azure seems to be rather strange anyway. I just 
deleted my Azure VM hosting ma TeamCity build agent as the VM costs keep 
running even if the VM is shut down. The Support told me that in order to 
pevent MS from billing me for the idle time, I would have to delete the VMs 
after using them and setting them up the next time I want to use them (Very 
disapointing)

Would have been the ideal setup for CI Flex builds :-|

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Freitag, 24. Mai 2013 16:01
An: dev@flex.apache.org
Betreff: Re: Jenkins builds and Mustella

A little update:

- flex-tlf (-): succeeds
- flex-sdk (main checkintests): succeeds
- flex-sdk_release (release): waiting for Extension Manager install
- flex-sdk_asdoc (asdoc): succeeds
- flex-falcon (all) - succeeds, marked 'unstable' because some
FalconJx tests fail

I'll let these run a week or so, just to see if they keep up and react
correctly to commits etc., after that I'll retire the 'old' jobs and
put these in production (have them report failures and restores to
dev@a.o. and the 'breaking' contributor).

On the Mustella Azure VM: had two runs of about 7 hrs (doh!) fail
because the JavaVM ran out of memory. Have set ANT_OPTS system
variable to give the JavaVM 512MB to play with, see if that fixes
things. Also have downsized the Azure VM to a Medium instance, which
(if it has the horsepower to run Mustella: 2 cores, 3.5GB) should give
us enough credits to run it full time. The previous size (Full) only
allowed us to run it for the first half of each month :-)

Plans for the Azure VM:
- install Apache to serve 'localhost' to Mustella
- install Jenkins to automated the git pulls, Mustella run and report
the results

Once I'm satisfied with the setup, I'll give the entire PMC access to
the VM via RDP. That way we can all work on getting all the tests to
pass and tweak the system.

EdB


On Thu, May 23, 2013 at 7:31 PM, Erik de Bruin  wrote:
> Hi,
>
> Just to let you know what I'm working on:
>
> I'm working on the build machines to create new/updated Jenkins jobs
> for the following builds:
> - flex-tlf (-): succeeds
> - flex-sdk (main checkintests): succeeds
> - flex-sdk_release (release): fails, waiting for Extension Manager install
> - flex-sdk_asdoc (asdoc): succeeds
> - flex-falcon (?) - this is a work in progress
>
> Once all these jobs pass, I'll disable/remove the older versions.
>
> I've also create a Windows Azure Win2008 VM that I've set up with all
> the stuff needed to run Mustella. It did a successful (failureless)
> run of 'tests/components/Label'. It's currently running 'vanilla'
> Mustella (./mini_run.sh -all) to see what remains to be fixed on that
> machine. For one: I haven't set up a server to handle 'localhost' yet,
> so I expect plenty of failures. It's a work in progress ;-)
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

AW: Reducing the number of Jira Posts to the Mailinglist?

[christofer.d...@c-ware.de]

Well that would be an option for anyone with an Exchange server ... most others 
to these filters on client-side and people using these would probably have 
trouble when accessing the list on a smartphone. I actually turned of 
email-push notifications on my smartphone because of these emails, because they 
were totally driving me nuts.

Chris

-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com] 
Gesendet: Freitag, 10. Mai 2013 14:11
An: dev@flex.apache.org
Betreff: Re: Reducing the number of Jira Posts to the Mailinglist?

Hi,

Easy solution is to use an email filter all JIRA emails come from 
j...@apache.org.

I do and I probably generate most of the emails.

Thanks,
Justin

AW: [FalconJX] Using RIATest

[christofer.d...@c-ware.de]

Oh ... ok so that's a feature that seems to have been added ... that's cool :-)


Von: João Fernandes [joaopedromartinsfernan...@gmail.com]
Gesendet: Freitag, 3. Mai 2013 13:06
An: dev@flex.apache.org
Betreff: Re: [FalconJX] Using RIATest

Chris, RiaTest does support JUnit output to integrate in a CI server


On 3 May 2013 11:48, christofer.d...@c-ware.de wrote:

> As I mentioned, I am just adding my 50ct to the discussion.
>
> RIATest did leave a very good impression with me when evaluating it and I
> think I did give the tool a good overall result. However I really liked the
> tools for which I was able to write my testcases in Junit or TestNG just
> because this way it was easy to have the test-results included in the CI
> build servers results. With all the others that ran tests using any wrapper
> usually only returned an "ok" or "fail" which no CI server could pick up
> the details.
>
> Chris
>
>
> 
> Von: Tigran Najaryan [tig...@gmail.com]
> Gesendet: Freitag, 3. Mai 2013 09:45
> An: dev@flex.apache.org
> Betreff: RE: [FalconJX] Using RIATest
>
> > From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
> >
> > Just to add my 50ct.
> >
> > Wouldn't it be good to use a tool for writing test that you can write
> tests in
> > Java? As far as I remember there was only a hand-full of tools supporting
> > this when I evaluated a lot of these tools:
> > https://dev.c-
> > ware.de/confluence/display/PUBLIC/Functional+Testing+Tools
>
> By all means use whatever you think is best for Apache Flex team. I am
> naturally biased so I will not try to argue. :-) I will only speak if you
> want to hear my reasoning for RIATest.
>
> Tigran.
>



--

João Fernandes

AW: [FalconJX] Using RIATest

[christofer.d...@c-ware.de]

As I mentioned, I am just adding my 50ct to the discussion.

RIATest did leave a very good impression with me when evaluating it and I think 
I did give the tool a good overall result. However I really liked the tools for 
which I was able to write my testcases in Junit or TestNG just because this way 
it was easy to have the test-results included in the CI build servers results. 
With all the others that ran tests using any wrapper usually only returned an 
"ok" or "fail" which no CI server could pick up the details.

Chris



Von: Tigran Najaryan [tig...@gmail.com]
Gesendet: Freitag, 3. Mai 2013 09:45
An: dev@flex.apache.org
Betreff: RE: [FalconJX] Using RIATest

> From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
>
> Just to add my 50ct.
>
> Wouldn't it be good to use a tool for writing test that you can write
tests in
> Java? As far as I remember there was only a hand-full of tools supporting
> this when I evaluated a lot of these tools:
> https://dev.c-
> ware.de/confluence/display/PUBLIC/Functional+Testing+Tools

By all means use whatever you think is best for Apache Flex team. I am
naturally biased so I will not try to argue. :-) I will only speak if you
want to hear my reasoning for RIATest.

Tigran.

AW: [FalconJX] Using RIATest

[christofer.d...@c-ware.de]

Just to add my 50ct.

Wouldn't it be good to use a tool for writing test that you can write tests in 
Java? As far as I remember there was only a hand-full of tools supporting this 
when I evaluated a lot of these tools:
https://dev.c-ware.de/confluence/display/PUBLIC/Functional+Testing+Tools

Chris


Von: Tigran Najaryan [tig...@gmail.com]
Gesendet: Freitag, 3. Mai 2013 08:30
An: dev@flex.apache.org
Betreff: RE: [FalconJX] Using RIATest

> From: Alex Harui 
> I'm wondering how this will work.  In an open-source development model,
> both
> committers and non-committers should be able to get the source and run
> tests
> in order to prove that changes they make don't cause any problems.  The
> only
> difference is that non-committers submit patches, but committers can check
> in directly.
>
> Hopefully, many of these people are going to be legitimate RIATest
> customers.  Do they get to use the free license to test their
applications?
> If not, how does the license checker determine whether that person is
> testing the Flex SDK or their application?

Let us consider separately a) committers who will be creating tests,
debugging them, doing actual test development using RIATest and b) the rest
of the world.

a) I believe there will be very few committers who will actually work with
RIATest and will develop tests. For this activity my company will grant
several full Professional edition licenses to Apache Flex team. I believe 5
or 10 licenses will be sufficient, I do not think there will ever be more
than that number of committers who will work on RIATest tests. These will be
regular licenses that we sell to our customers, the only difference will be
that we will donate these free of charge to Apache Flex. Any committer who
needs to write a test can grab one of those licenses and work with a copy of
RIATest downloaded online.

b) For the rest of the world there will be a special license. This special
license for Apache Flex will simply allow anyone in the world who builds
Flex SDK to use RIATest to run tests that are part of Flex SDK. This license
will be granted for free to anyone who runs Flex SDK build. The license will
be activated once RIATest is registered by a special "master" license key
that we will issue for Apache Flex. I think we can even automate this
registration so that a blank build of the SDK downloads RIATest (like it
currently does for other external dependencies) and registers it with the
special key, making RIATest ready to run tests that are part of the build.

Does this make sense?


>
> > 4. I will need someone's help to integrate RIATest into Flex SDK build.
> It would probably be best if you submit patches to build scripts and the
> readme.  You would likely earn committer rights that way and then would be
> able to make changes directly going forward.

Do we expect the tests to be part of FalconJX or part of FlexJS? Which repo
will they go to? The FlexJSTest_again example is in flex-asjs repo. For the
sample tests that I created for FlexJSTest_again I put the files in a
"tests" directory which is sibling to "src" directory under
FlexJSTest_again. Is this location OK?

Are there any other existing Flex examples that can be compiled using
FalconJX for which I can write tests?

Tigran.

AW: Meet 'marmotinni', an ASJS testing framework

[christofer.d...@c-ware.de]

I would guess that when compiling to JS FlexUnit won't work as FlexUnit 
requires the Unit Tests to run in a FlashPlayer instance ... Am I correct? So 
without a unit-testing framework to support JS Flex, I guess we couldn't 
actually do any Unit Tests with it. 

Guess this problem is similar to the debugging problem as we currently wouldn't 
have any decent Debugging support to debug JS Flex applications from inside the 
IDE.

Chris

Von: Alex Harui [aha...@adobe.com]
Gesendet: Freitag, 12. April 2013 18:14
An: dev@flex.apache.org
Betreff: Re: Meet 'marmotinni', an ASJS testing framework

I haven't really looked yet, but why aren't we going to use FlexUnit?


On 4/12/13 7:02 AM, "Erik de Bruin"  wrote:

> Hi,
>
> I've just committed a new testing framework to the ASJS repo. This
> testing framework, which I've called 'marmotinni', following the
> 'mustella' convention (Google it ;-), consists of FalconJX, asjs
> projects, Java test classes (using the Selenium browser testing
> classes) and an ant script to tie them all together.
>
> Right now there's only one test. It consists of a FlexJS project that
> displays a single TextButton 100px from the left side of the browser
> window. The ant script builds a JS release version using FalconJX. The
> 'TextButton' Java class uses the Selenium framework to display the
> FlexJS release build in a Firefox window, see if the button is there
> and in the correct position. The result of the test is passed back to
> ant and all artefacts are cleaned up.
>
> Please take a look and let me know what you think.
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Status on the maven-flex-plugin

[christofer.d...@c-ware.de]

Hi guys.

juts to give you a short update on what I'm currently working on.

A working complete maven-flex-plugin needs code generation in place at several 
locations. Besides normal code generation when generating an ActionScript model 
from a Java Model, especially the Unit-Test support also needs quite a lot of 
generated code.

At first I was intending on migrating the flexmojos generation, but flexmojos 
makes use of several different code-generators. It seems that there is 
currently not a single "universal" code generator maven-plugin available. So 
this is what I'm currently working on. As this plugin will be able to generate 
any sort of sources, resources, test-sources and test-resources from existing 
Java Sources, Java Classes, Property files and Maven models, I am working on 
this outside of Apache Flex and am intending on giving this to the Apache Maven 
guys as soon as I have a version that is actually worth reviewing.

I just wanted to give you a short update and assure you that I am still working 
on things, even though I am currently not very active on the list (mainly 
because it has become impossible to follow the list in reasonable time because 
of 99,9% Git related postings ;-) ).

Chris

Debugging FlexJS applications

[christofer.d...@c-ware.de]

Just a question ...

how would we actually debug a FlexJS application? I am just asking, cause I 
currently have to work with GWT and I am really really anoyed with how you have 
to debug these applications (Actually I am anoyed by a lot more ;-) ). Would 
this be just as tricky as with GWT? Or is no debugging support at all included 
and the idea is more of a "develop and debug as flex and export the finished 
application to JavaScript"?

Chris

AW: Git Migration Reset

[christofer.d...@c-ware.de]

Just as a suggestion ... why not clone the GIT version as soon as it's finished.
Then delete the ".git" or ".svn" stuff from the copy you are currently working 
on.
Then simply copy all the stuff from the SCM-less copy containing your changes 
into your clean clone.
Git should detect unchanged, modified and new files ... only thing is that it 
won't detect moved or deleted files. 

After that ... commit ... push ... all's good and no kittens get's killed :-)

Think this should work without the need to actually patch anything at all 
(Assuming you were the only one working on the Falcon code ... if there were 
more people working on this, this would be a problem though).

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Mittwoch, 13. März 2013 20:45
An: dev@flex.apache.org
Betreff: Re: Git Migration Reset

> Ah, so you made changes to the supposedly read-only git repo in the
> meantime.  Why would you do something like that?  While at the same time
> you were asking for a do over.  Does not compute.  What did you expect?

There was nothing "read-only" about my local copy. The understanding
at the time was that write enableing of the the remote copy (branch?)
would be a matter of hours, subject only to a check by the PMC. Before
starting work, I did check the Falcon git repo, and it looked good. It
thing it was not unreasonable for me to expect the 'write' switch to
be throw with the same expediency with which INFRA moved at the start
of this episode.

On the point of the "do over": I don't recall asking for such a thing.
I understand no that the confusion might have come from the [DISCUSS]
thread I started - note: this was AFTER INFRA took their unilateral
action by removing the git repos and re-enabling SVN - was about
postponing the migration until INFRA had taken their 'git' support out
of beta and was ready to fully support it, presumably months if not
years in the future. That thread is not VOTE or LAZY but DISCUSS. I
specifically chose that subject so no action would be taken until a
discussion had taken place.

> Theoretically, that would work.  But given that you are not too familiar
> with Git, it would be a risky proposition.  It is up to you.

Well, "up to me" is not really the case, as I explained, but I
understand it's "out of your hands." I'll make a full backup of the
actual source files, just to make sure no code is lost when trying to
manage the move to git.

Now, before this gets out of hand, let me re-iterate: by now - by way
of a healthy serving of tutorials and some needed distraction on
/r/aww - I nearly understand the basics of git. I accept the project
is moving to git, unless a new consensus on the DISCUSS thread leads
to a new VOTE :-) I am doing my best to have my code ready for the
migration and by sharing my experiences and frustrations with the list
I try to smooth the way for others.

TL;DR: confusion all over the place, but really there's nothing to see
here, we're moving forward to a 'git' future.

EdB



> Thanks,
> Om
>
>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

AW: SVN to Git migration in progress

[christofer.d...@c-ware.de]

Well in our case this would simply could be any committer of the project. At 
the time of me writing that article Velo was the only person with commit rights 
to the central repo :-)


Von: Gordon Smith [gosm...@adobe.com]
Gesendet: Dienstag, 12. März 2013 18:32
An: dev@flex.apache.org
Betreff: RE: SVN to Git migration in progress

> "What happens here is that you commit to a publically accessible repository 
> clone on GitHub that only you can commit to and then issue a "Pull Request" 
> to Velo. He can now review your changes and pull these changes from your 
> private fork at GitHub. If he likes what you did, he will apply your patches 
> to the trunk and you're done."

Who is going to be the Velo for Apache Flex? That person is going to be very 
busy!

- Gordon


-Original Message-
From: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Sent: Tuesday, March 12, 2013 9:00 AM
To: dev@flex.apache.org
Subject: AW: SVN to Git migration in progress

I once wrote up the workflow of contributing to Flexmojos using Git ... as the 
workflow for Flex is now the same, perhaps it explains a little and helps clear 
the confusion with git:
https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and my 
co-contributors. I need to 'commit' to my local repo and then 'push' to get it 
out to the world, where before only a 'commit' was needed...

EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira  
wrote:
> commit is like SVN, you are making a commit in your *local* repo.
>
> When GIT will became RW, you will be able to "push" to the remote repo
> sharing your changes.
>
> In Git you have a fully functional local repo, and there's a shared
> one remotely while in SVN there's only one remotely...
>
>
>
> 2013/3/12 Erik de Bruin 
>
>> Joao,
>>
>> Thank you... but that went right over my head. I'm still at the stage
>> where I'm trying to grok the difference between 'commit' and 'push'...
>> I'll get there, but I'm so not pleased with (the timing) of this move
>> that you all get to enjoy my wining about it until I have the
>> FalconJx stuff - which I had nicely lined up for a SVN commit -
>> working again in the new git repos I've been forced to make, and my
>> code is safely 'staged/committed/pushed' for all to enjoy.
>>
>> EdB
>>
>>
>>
>> On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
>>  wrote:
>> > Eric, If you want to learn the basics behind git you can try
>> > http://pcottle.github.com/learnGitBranching/ , it helped me.
>> >
>> >
>> > On 12 March 2013 09:14, Erik de Bruin  wrote:
>> >
>> >> Are you sure?
>> >>
>> >> I did a 'git clone' and 'build.properties' shows:
>> >>
>> >> # flex-sdk-description values
>> >> release = Apache Flex 4.9.1
>> >> release.version = 4.9.1
>> >>
>> >> While the develop branch in SVN has:
>> >>
>> >> # flex-sdk-description values
>> >> release = Apache Flex 4.10.0
>> >> release.version = 4.10.0
>> >>
>> >> Oops?
>> >>
>> >> EdB
>> >>
>> >>
>> >> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>> >>  wrote:
>> >> > it contains a copy of the develop branch you should do: git
>> >> > clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it
>> >> > will create
>> a
>> >> new
>> >> > directory called flex-sdk, if you prefer 'develop' append ' develop'
>> to
>> >> the
>> >> > clone command
>> >> >
>> >> > -Fred
>> >> >
>> >> > -Message d'origine- From: Erik de Bruin
>> >> > Sent: Tuesday, March 12, 2013 9:40 AM
>> >> >
>> >> > To: dev@flex.apache.org
>> >> > Subject: Re: SVN to Git migration in progress
>> >> >
>> >> > Just trying to understand what just happened:
>> >> >
>> >> > https://git-wip-us.apache.org/repos/asf/flex-sdk.git
>> >> >
>

AW: SVN to Git migration in progress

[christofer.d...@c-ware.de]

I once wrote up the workflow of contributing to Flexmojos using Git ... as the 
workflow for Flex is now the same, perhaps it explains a little and helps clear 
the confusion with git:
https://dev.c-ware.de/confluence/display/PUBLIC/Contributing+to+Flexmojos

Chris


Von: Erik de Bruin [e...@ixsoftware.nl]
Gesendet: Dienstag, 12. März 2013 13:08
An: dev@flex.apache.org
Betreff: Re: SVN to Git migration in progress

What advantage is having a local repo to having a local working copy?
It seems to me that all it does is add an extra layer between me and
my co-contributors. I need to 'commit' to my local repo and then
'push' to get it out to the world, where before only a 'commit' was
needed...

EdB



On Tue, Mar 12, 2013 at 1:03 PM, Carlos Rovira
 wrote:
> commit is like SVN, you are making a commit in your *local* repo.
>
> When GIT will became RW, you will be able to "push" to the remote repo
> sharing your changes.
>
> In Git you have a fully functional local repo, and there's a shared one
> remotely while in SVN there's only one remotely...
>
>
>
> 2013/3/12 Erik de Bruin 
>
>> Joao,
>>
>> Thank you... but that went right over my head. I'm still at the stage
>> where I'm trying to grok the difference between 'commit' and 'push'...
>> I'll get there, but I'm so not pleased with (the timing) of this move
>> that you all get to enjoy my wining about it until I have the FalconJx
>> stuff - which I had nicely lined up for a SVN commit - working again
>> in the new git repos I've been forced to make, and my code is safely
>> 'staged/committed/pushed' for all to enjoy.
>>
>> EdB
>>
>>
>>
>> On Tue, Mar 12, 2013 at 12:14 PM, João Fernandes
>>  wrote:
>> > Eric, If you want to learn the basics behind git you can try
>> > http://pcottle.github.com/learnGitBranching/ , it helped me.
>> >
>> >
>> > On 12 March 2013 09:14, Erik de Bruin  wrote:
>> >
>> >> Are you sure?
>> >>
>> >> I did a 'git clone' and 'build.properties' shows:
>> >>
>> >> # flex-sdk-description values
>> >> release = Apache Flex 4.9.1
>> >> release.version = 4.9.1
>> >>
>> >> While the develop branch in SVN has:
>> >>
>> >> # flex-sdk-description values
>> >> release = Apache Flex 4.10.0
>> >> release.version = 4.10.0
>> >>
>> >> Oops?
>> >>
>> >> EdB
>> >>
>> >>
>> >> On Tue, Mar 12, 2013 at 10:04 AM, Frédéric THOMAS
>> >>  wrote:
>> >> > it contains a copy of the develop branch you should do: git clone
>> >> > https://git-wip-us.apache.org/repos/asf/flex-sdk.git, it will create
>> a
>> >> new
>> >> > directory called flex-sdk, if you prefer 'develop' append ' develop'
>> to
>> >> the
>> >> > clone command
>> >> >
>> >> > -Fred
>> >> >
>> >> > -Message d'origine- From: Erik de Bruin
>> >> > Sent: Tuesday, March 12, 2013 9:40 AM
>> >> >
>> >> > To: dev@flex.apache.org
>> >> > Subject: Re: SVN to Git migration in progress
>> >> >
>> >> > Just trying to understand what just happened:
>> >> >
>> >> > https://git-wip-us.apache.org/repos/asf/flex-sdk.git
>> >> >
>> >> > Does that contain a copy of 'trunk' or of 'branches/develop'?
>> >> >
>> >> > EdB
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Mar 12, 2013 at 9:16 AM, Frédéric THOMAS
>> >> >  wrote:
>> >> >>
>> >> >> I'm currently cloning the repo to see how it has been done...
>> >> >>
>> >> >> -Fred
>> >> >>
>> >> >> -Message d'origine- From: Justin Mclean
>> >> >> Sent: Tuesday, March 12, 2013 9:11 AM
>> >> >>
>> >> >> To: dev@flex.apache.org
>> >> >> Subject: Re: SVN to Git migration in progress
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >>> Hey, textLayout is converted to git too, so a git submodule init and
>> >> then
>> >> >>> git submodule update should do the trick, non ?
>> >> >>
>> >> >>
>> >> >> No because we need a subdirectory of the textLayout git repo.
>> >> >>
>> >> >> Justin
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Ix Multimedia Software
>> >> >
>> >> > Jan Luykenstraat 27
>> >> > 3521 VB Utrecht
>> >> >
>> >> > T. 06-51952295
>> >> > I. www.ixsoftware.nl
>> >>
>> >>
>> >>
>> >> --
>> >> Ix Multimedia Software
>> >>
>> >> Jan Luykenstraat 27
>> >> 3521 VB Utrecht
>> >>
>> >> T. 06-51952295
>> >> I. www.ixsoftware.nl
>> >>
>> >
>> >
>> >
>> > --
>> >
>> > João Fernandes
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F:  +34 912 94 80 80
> http://www.codeoscopic.com
> http://www.directwriter.es
> http://www.avant2.es



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

AW: [jira] [Resolved] (FLEX-33245) Apache Flex Mavenizer needs a review of the licenses used

[christofer.d...@c-ware.de]

I use jersey to query the central maven repo for artifact hashes. I guess any 
other JSON rest client would do.

Chris

-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com] 
Gesendet: Montag, 11. März 2013 22:52
An: dev@flex.apache.org
Betreff: Re: [jira] [Resolved] (FLEX-33245) Apache Flex Mavenizer needs a 
review of the licenses used

Hi,

I just have to point out that GPL is not a compatible license with Apache.

http://www.apache.org/licenses/GPL-compatibility.html
http://www.apache.org/legal/3party.html

CDDL is a category B license so that may be OK, however GPL is an excluded 
license.

Can you give some more info on how jersey is used. 

I assume this is the license in question:
http://jersey.java.net/CDDL+GPL.html

Thanks,
Justin

AW: Maven JIRA issues

[christofer.d...@c-ware.de]

Well I just checked them and closed some of them. But most of the "Maven" 
issues simply used the Word "Maven" when discribing an issue. But at least I 
could close some of them :-)

Chris




Von: Justin Mclean [jus...@classsoftware.com]
Gesendet: Montag, 11. März 2013 01:18
An: dev@flex.apache.org
Betreff: Maven JIRA issues

Hi,

There's about a dozen or so outstanding Maven issues. Can someone more familiar 
with Maven (I don't use it) take a look and see if any of the JIRA issues can 
be resolved and/or clarify what the progress is.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLEX%20AND%20text%20~%20maven%20and%20status%20!%3D%20%22closed%22%20and%20status%20!%3D%20%22resolved%22

Thanks,
Justin

AW: Apache Flex 4.91 compatibility with ILOG Elixir Enterprise 3.5

[christofer.d...@c-ware.de]

My experience with IBM and especially Elixir is that I wanted to give IBM a 
which patched Elixir to work with Flex 4 a while ago ... as a thank-you I got a 
law-suite threat from IBM if I was to make this patch public. So much for IBMs 
kindness :-)


Von: Mark Fuqua [m...@availdata.com]
Gesendet: Donnerstag, 7. März 2013 00:39
An: dev@flex.apache.org
Betreff: RE: Apache Flex 4.91 compatibility with ILOG Elixir Enterprise 3.5

If anyone at Apache Flex or Apache has any contacts with IBM (they support a
couple other open source projects)...I am sure they bought Ilog for all the
other parts, not the elixir (flex) part...plus Flash is not in with the hip
crowd these days...

IMHO, few things could give a boost to Apache Flex adoption like having Ilog
Elixir components as part of Apache Flex.  I seriously doubt IBM makes much
money on them...I don't even think they notice numbers with less than 6
digits. But the component set sells for $3200, which is pretty steep (plus
there are deployment costs).

Anybody on the list know someone at IBM...It sure would be nice.

@Scott...sorry for not actually answering your question.  But I think IBM
would like a graceful way to end their support for Ilog Elixir.

Mark

-Original Message-
From: Scott Peterson [mailto:meg...@gmail.com]
Sent: Wednesday, March 06, 2013 3:15 PM
To: dev@flex.apache.org
Subject: Apache Flex 4.91 compatibility with ILOG Elixir Enterprise 3.5

Has anyone successfully configured the ILOG Elixir Enterprise 3.5 (Patch 7)
Calendar Component to build with Apache Flex 4.91? My AIR application builds
without error but doesn't launch, exhibiting *ReferenceError: **Error
#1065: Variable com.ibm.ilog.elixir.utils::LicenseHandler is not defined.
*along with the other errors below. Note my AIR application builds/launches
without issue when compiled with Flashbuilder 4.7 and the Flex 4.6 SDK.



I've posted this question to the IBM ILOG Elixir Enterprise support forum
but have yet to receive a reply. Most concerning is another forum user's
unanswered question last month about IBM's commitment to support Apache
Flex.



I appreciate any insights others can provide.




Many thanks,

Scott





Flashbuilder 4.7 64-bit

ILOG Elixir Enterprise 3.5 (Patch 7)

Apache Flex 4.91

Adobe AIR 3.6 SDK



Complete error message



*ReferenceError: Error #1065: Variable
com.ibm.ilog.elixir.utils::LicenseHandler is not defined.
*at
com.ibm.ilog.elixir.calendar.components::Calendar/initWM()[/data/flex/tools/
branches/release-3.5/enterprise/build/product_build/patch_target/sources/ent
erprise/library/elixir/spark-calendar/src/flex/com/ibm/ilog/elixir/calendar/
components/Calendar.as:7686]
at
com.ibm.ilog.elixir.calendar.components::Calendar/attachSkin()[/data/flex/to
ols/branches/release-3.5/enterprise/build/product_build/patch_target/sources
/enterprise/library/elixir/spark-calendar/src/flex/com/ibm/ilog/elixir/calen
dar/components/Calendar.as:7638]
at
spark.components.supportClasses::SkinnableComponent/validateSkinChange()[/Us
ers/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark
/components/supportClasses/SkinnableComponent.as:453]
at
spark.components.supportClasses::SkinnableComponent/createChildren()[/Users/
justinmclean/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/com
ponents/supportClasses/SkinnableComponent.as:412]
at
mx.core::UIComponent/initialize()[/Users/justinmclean/Documents/ApacheFlexSD
K/frameworks/projects/framework/src/mx/core/UIComponent.as:7642]
at mx.core::UIComponent/
http://www.adobe.com/2006/flex/mx/internal::childAdded()[/Users/justinmclean
/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UICompone
nt.as:7503]
at
mx.core::UIComponent/addChildAt()[/Users/justinmclean/Documents/ApacheFlexSD
K/frameworks/projects/framework/src/mx/core/UIComponent.as:7207]
at
spark.components::Group/addDisplayObjectToDisplayList()[/Users/justinmclean/
Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/Group
.as:2090]
at spark.components::Group/
http://www.adobe.com/2006/flex/mx/internal::elementAdded()[/Users/justinmcle
an/Documents/ApacheFlexSDK/frameworks/projects/spark/src/spark/components/Gr
oup.as:1681]
at
spark.components::Group/setMXMLContent()[/Users/justinmclean/Documents/Apach
eFlexSDK/frameworks/projects/spark/src/spark/components/Group.as:644]
at
spark.components::Group/createChildren()[/Users/justinmclean/Documents/Apach
eFlexSDK/frameworks/projects/spark/src/spark/components/Group.as:897]
at
mx.core::UIComponent/initialize()[/Users/justinmclean/Documents/ApacheFlexSD
K/frameworks/projects/framework/src/mx/core/UIComponent.as:7642]
at mx.core::UIComponent/
http://www.adobe.com/2006/flex/mx/internal::childAdded()[/Users/justinmclean
/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/core/UICompone
nt.as:7503]
at
mx.core::UIComponent/addChildAt()[/Users/justinmclean/Documents/ApacheFlexSD
K/frameworks/projects/framework/src/mx/co

AW: [jira] [Commented] (FLEX-33086) Make SDK build with Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven repository

[christofer.d...@c-ware.de]

Ahem ... Have to say "no" ... I guess the old one was run on Sonatype servers. 
As Velo no longer is at Sonatype I guess noone is maintaining that anymore and 
I can't see a way how to deploy the maven site there :-(

I would be really glad, if we could switch off the old Sonatype site as this 
causes more trouble than it helps solve.

Chris


Von: Miguel Serrano [mserra...@gmail.com]
Gesendet: Dienstag, 26. Februar 2013 13:41
An: dev@flex.apache.org
Betreff: Re: [jira] [Commented] (FLEX-33086) Make SDK build with 
Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven 
repository

Thanks Chris, that's amazing news!
I see the new entries in flexmojos confluence. Is the maven-generated site
available too?


On 25 February 2013 09:24, Christofer Dutz (JIRA)  wrote:

>
> [
> https://issues.apache.org/jira/browse/FLEX-33086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585746#comment-13585746]
>
> Christofer Dutz commented on FLEX-33086:
> 
>
> Seems that I have completely missed this discussion ;-)
>
> Well I'm pleased to report that Flexmojos 6.0.0 has just been deployed to
> sonatypes public maven repo. Using the Mavenizer you can now start to build
> Apache Flex applications using maven. So one part of this Ticket could be
> closed :-)
>
> And to add my 50ct to the discussion: I have never had real trouble
> setting up Maven projects and I have setup a lot of them and usually tricky
> configurations. Whenever I was called to fix a Maven setup, it was because
> people setting it up initially weren't thinking in Maven ... it's sort of
> like a C Programmer switching to Java, but wrappling his head around the
> Concept of OO-development.
>
> @Martin Heidegger: I personally don't know a single developer that works
> with gradle.
> @Oleg Sivokon: What trouble are you having? I know that Velo really had
> some motivation problems, that's why I took over Flexmojos development. I
> am personally using Flexmojos in about 6 different projects and am not
> having any real issues with it and I have come to know quite a lot of
> people on the flex-list that are actively using it too. I think we were
> able to address the one or the other problem they were having and the
> current solution seems to be pretty solid.
>
> > Make SDK build with Maven/Flexmojos and deploy release and snapshot
> artifacts to the Apache Maven repository
> >
> 
> >
> > Key: FLEX-33086
> > URL: https://issues.apache.org/jira/browse/FLEX-33086
> > Project: Apache Flex
> >  Issue Type: Story
> >Reporter: Alex Harui
> >  Time Spent: 2h
> >  Remaining Estimate: 0h
> >
>
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>



--
Miguel Serrano Milano
mserra...@gmail.com

CI Agent on MS Azure

[christofer.d...@c-ware.de]

Hi,

this weekend, while releasing Flexmojos, I took the opportunity to checkout 
Microsoft Azure.
Seems to do the job nicely. I allready was able to setup a TeamCity agent on a 
Windows VM that is now the Build Agent for Flexmojos CI builds. I documented 
the setup on my Wiki: 
https://dev.c-ware.de/confluence/display/PUBLIC/Setting+up+a+TeamCity+agent+on+an+Azure+VM

What I particularly liked in contrast to EC2 was that your virtual harddrive is 
not reset every time you shutdown your VM and the Management UI is a lot less 
confusing.

Unfortunately there is no plugin available to automatically start/stop an Azure 
VM on demand, but they do provide a rest-service to do that and I'm currently 
working on a TeamCity Cloud Plugin ... so eventually that gap might be 
closeable.

Today I was called back by Microsoft and the Lady wanted to know how I liked 
Azure. While I was talking to her, I switched the topic to if MS would be 
willing to provide Apache Flex with a small Windows VM free of charge ... She 
told me that this might be possible and that I should send her an Email ... 
well I did this ... so let's see what the answer is.

Chris