You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "christofer.dutz@c-ware.de" <ch...@c-ware.de> on 2012/08/26 18:35:03 UTC
[OT] Current status on Flexunit4?
Hi,
This topic might be a liitle off-topic, but as I have read quite a few statements on Adobe and Flexunit here, I thougt it would be the best place to ask. As it seems that the Flexunit.org mailinglist isn't really active anymore.
I just finished some work on Flexmojos unittesting support, especially supporting parametrized tests in conjunction with Flexunit4. Currently I don't want to push my changes back to FMs trunk, because I am not quite sure what the current status on Flexunit is.
Currently Flexmojos supports two flex unit testing frameworks called "flexunit"
- com.adobe.flexunit:flexunit:0.85:swc (called flexunit in FM)
- com.adobe.flexunit:flexunit: 4.0-beta-2:swc (called flexunit4 in FM)
I am quite unsure about the later one of them. On the Project page http://www.flexunit.org/ I can see no reference to adobe at all. Even the package structure is different and all refer to "org.flexunit". So I'm guessing this is a second project unluckily also called "Flexunit". Am I correct about this? In this case the current groupId used in FM shouldn't be "com.apache.flexunit" but something different . but what should it be instead?
My second area of uncertainty regarding flexunit (from flexunit.org) is what the latest version is. The Blog on the page claims to be 4.1 RC2, but the download page states 4.1 ("stable" without the RC2).
Assuming the flexunit.org project is different from adobes project and that RC2 has become the final release I was thinking about using org.flexunit:flexunit:4.1.0:swc as version and would like to have this published in a public repo.
It would be great if you could help me sort this out.
Chris
[ C h r i s t o f e r D u t z ]
C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Karlstraße. 104, 64285 Darmstadt
fon: 0 61 51 / 27315 - 61
fax: 0 61 51 / 27315 - 64
mobil: 0171 / 7 444 2 33
email: christofer.dutz@c-ware.de
http://www.c-ware.de
UStId-Nr. DE195700962
AW: [OT] Current status on Flexunit4?
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Well I have converted all FDKs from 2.0 to 4.8 and updated Flexmojos to work with these FDKs.
I was looking for volounteers to test them, before I was going to start trying to have them published somewhere.
The good thing would be, that I could make sure Flexmojos is compatable with the official FDKs and then start work on a new lightweight plugin.
Chris
[ C h r i s t o f e r D u t z ]
C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Karlstraße. 104, 64285 Darmstadt
fon: 0 61 51 / 27315 - 61
fax: 0 61 51 / 27315 - 64
mobil: 0171 / 7 444 2 33
email: christofer.dutz@c-ware.de
http://www.c-ware.de
UStId-Nr. DE195700962
-----Ursprüngliche Nachricht-----
Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im Auftrag von Carlos Rovira
Gesendet: Sonntag, 26. August 2012 20:05
An: flex-dev@incubator.apache.org
Betreff: Re: [OT] Current status on Flexunit4?
Hi Chris,
I think you're right for most of you explained here. I think the most important think right now is to get, in some way, mavenized version of apache flex sdk brought to users soon. This should be done with the consensus of PPMC members here to provide this option along the classic download options.
My main concern is that lots of us are stuck in flex 4.5.1 since this was the last one deployed, so I'd like that all people using flex in mavenized projects could enter apache flex ASAP...to make this real, we need the maven versions deployed in some official repository. We are loosing lots of developers and groups right now that have their apps in 4.5.1...we are one of them ;)
2012/8/26 christofer.dutz@c-ware.de <ch...@c-ware.de>:
> Hi Carlos,
>
> well I think that after Flex becoming an ASF project it sounds sensible to think about moving a maven plugin for building flex there too. Currently I think it wouldn't be the best option to simply move Flexmojos under the hood of the ASF. And after all Velo would have to give his Ok for that.
>
> Flexmojos in its current state supports building Flex projects starting with Flex 2.0.1.180927 and hereby is full of code handling all this downgrading.
>
> Second thing is that Flexmojos includes a lot of other stuff that is also not under the hood of the ASF.
>
> Third and in my opinion the thing that sometimes disturbs me most, is that flexmojos is far from the simple "compile this stuff into an swf for me please" tool. During time it has grown to support more and more stuff. This makes it difficult for tool providers to validate all the configuration options. For example IntelliJ complains about me not setting a storepass config option, which is actually only needed when packaging Air applications. So splitting this up into a simple flex-compiler and air-packaging plugin would allow configuration support to be a lot cleaner.
>
> The solution I would opt on would be do two steps:
> - Start publishing official Mavenized Flex SDKs.
> - Create a new set of lightweight maven plugins each with its individual purpose.
>
> For the first step I could provide you with my Generator, that I am currently working on (Almost finished). You could evaluate the resulting FDKs and fine-tune them, if you think they need optimizing. These FDKs should then be officially hosted on the ASF Maven servers. After this is done these FDKs would then be the base for building a set of lightweight maven plugins. Each one dealing with its individual part of a flex projects build lifecycle:
> - Compiling AS and MXML files to SWFs and SWCs
> (maven-flex-compiler-plugin)
> - Code Generation (maven-flex-code-generator-plugin)
> - UnitTesting (maven-flex-unittest-plugin)
> - Air Packaging (maven-air-packaging-plugin)
> - Optimizing the SWFs and SWCs (maven-flex-optimizer-plugin)
> - Deploying all needed Flex artifacts in a WAR project
> (maven-flex-war-deployment-plugin)
> - ...
> The good thing about this would be that they could be developed, maintained, versioned and released independently.
>
> I would be more than glad to help working on this and even already have a bunch of improvements I would like to introduce while doing so. Most of these would make it necessary for me to re-implement quite some portions of Flexmojos anyway.
>
> Chris
>
>
>
>
> [ C h r i s t o f e r D u t z ]
>
> C-Ware IT-Service
> Inhaber
> Dipl. Inf. Christofer Dutz
> Karlstraße. 104, 64285 Darmstadt
>
> fon: 0 61 51 / 27315 - 61
> fax: 0 61 51 / 27315 - 64
> mobil: 0171 / 7 444 2 33
> email: christofer.dutz@c-ware.de
>
> http://www.c-ware.de
>
> UStId-Nr. DE195700962
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im
> Auftrag von Carlos Rovira
> Gesendet: Sonntag, 26. August 2012 18:43
> An: flex-dev@incubator.apache.org
> Betreff: Re: [OT] Current status on Flexunit4?
>
> Hi Chris,
>
> could flexmojos be as well in ASF? (only a thought ;))
>
> best,
>
> Carlos
>
> 2012/8/26 Omar Gonzalez <om...@gmail.com>:
>> On Sunday, August 26, 2012, christofer.dutz@c-ware.de wrote:
>>
>>> Hi,
>>>
>>> This topic might be a liitle off-topic, but as I have read quite a
>>> few statements on Adobe and Flexunit here, I thougt it would be the
>>> best place to ask. As it seems that the Flexunit.org mailinglist
>>> isn't really active anymore.
>>>
>>> I just finished some work on Flexmojos unittesting support,
>>> especially supporting parametrized tests in conjunction with
>>> Flexunit4. Currently I don't want to push my changes back to FMs
>>> trunk, because I am not quite sure what the current status on Flexunit is.
>>>
>>> Currently Flexmojos supports two flex unit testing frameworks called
>>> "flexunit"
>>> - com.adobe.flexunit:flexunit:0.85:swc (called flexunit in FM)
>>> - com.adobe.flexunit:flexunit: 4.0-beta-2:swc (called flexunit4 in
>>> FM) I am quite unsure about the later one of them. On the Project
>>> page http://www.flexunit.org/ I can see no reference to adobe at all.
>>> Even the package structure is different and all refer to
>>> "org.flexunit". So I'm guessing this is a second project unluckily
>>> also called "Flexunit". Am I correct about this? In this case the
>>> current groupId used in FM shouldn't be "com.apache.flexunit" but
>>> something different . but what should it be instead?
>>> My second area of uncertainty regarding flexunit (from flexunit.org)
>>> is what the latest version is. The Blog on the page claims to be 4.1
>>> RC2, but the download page states 4.1 ("stable" without the RC2).
>>> Assuming the flexunit.org project is different from adobes project
>>> and that RC2 has become the final release I was thinking about using
>>> org.flexunit:flexunit:4.1.0:swc as version and would like to have
>>> this published in a public repo.
>>>
>>> It would be great if you could help me sort this out.
>>>
>>> Chris
>>>
>>>
>>> [ C h r i s t o f e r D u t z ]
>>>
>>> C-Ware IT-Service
>>> Inhaber
>>> Dipl. Inf. Christofer Dutz
>>> Karlstraße. 104, 64285 Darmstadt
>>>
>>> fon: 0 61 51 / 27315 - 61
>>> fax: 0 61 51 / 27315 - 64
>>> mobil: 0171 / 7 444 2 33
>>> email: christofer.dutz@c-ware.de <javascript:;>
>>>
>>> http://www.c-ware.de
>>>
>>> UStId-Nr. DE195700962
>>>
>>>
>>>
>> Michael Labriola and Digital Primates are currently in the process of
>> making the software grant to the ASF and FlexUnit will soon be in
>> Apache repositories. I would sit tight. ;)
>>
>> -omar
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F: +34 912 35 57 77
> CODEOSCOPIC S.A.
> Avd. del General Perón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
Re: [OT] Current status on Flexunit4?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Chris,
I think you're right for most of you explained here. I think the most
important think right now is to get, in some way, mavenized version of
apache flex sdk brought to users soon. This should be done with the
consensus of PPMC members here to provide this option along the
classic download options.
My main concern is that lots of us are stuck in flex 4.5.1 since this
was the last one deployed, so I'd like that all people using flex in
mavenized projects could enter apache flex ASAP...to make this real,
we need the maven versions deployed in some official repository. We
are loosing lots of developers and groups right now that have their
apps in 4.5.1...we are one of them ;)
2012/8/26 christofer.dutz@c-ware.de <ch...@c-ware.de>:
> Hi Carlos,
>
> well I think that after Flex becoming an ASF project it sounds sensible to think about moving a maven plugin for building flex there too. Currently I think it wouldn't be the best option to simply move Flexmojos under the hood of the ASF. And after all Velo would have to give his Ok for that.
>
> Flexmojos in its current state supports building Flex projects starting with Flex 2.0.1.180927 and hereby is full of code handling all this downgrading.
>
> Second thing is that Flexmojos includes a lot of other stuff that is also not under the hood of the ASF.
>
> Third and in my opinion the thing that sometimes disturbs me most, is that flexmojos is far from the simple "compile this stuff into an swf for me please" tool. During time it has grown to support more and more stuff. This makes it difficult for tool providers to validate all the configuration options. For example IntelliJ complains about me not setting a storepass config option, which is actually only needed when packaging Air applications. So splitting this up into a simple flex-compiler and air-packaging plugin would allow configuration support to be a lot cleaner.
>
> The solution I would opt on would be do two steps:
> - Start publishing official Mavenized Flex SDKs.
> - Create a new set of lightweight maven plugins each with its individual purpose.
>
> For the first step I could provide you with my Generator, that I am currently working on (Almost finished). You could evaluate the resulting FDKs and fine-tune them, if you think they need optimizing. These FDKs should then be officially hosted on the ASF Maven servers. After this is done these FDKs would then be the base for building a set of lightweight maven plugins. Each one dealing with its individual part of a flex projects build lifecycle:
> - Compiling AS and MXML files to SWFs and SWCs (maven-flex-compiler-plugin)
> - Code Generation (maven-flex-code-generator-plugin)
> - UnitTesting (maven-flex-unittest-plugin)
> - Air Packaging (maven-air-packaging-plugin)
> - Optimizing the SWFs and SWCs (maven-flex-optimizer-plugin)
> - Deploying all needed Flex artifacts in a WAR project (maven-flex-war-deployment-plugin)
> - ...
> The good thing about this would be that they could be developed, maintained, versioned and released independently.
>
> I would be more than glad to help working on this and even already have a bunch of improvements I would like to introduce while doing so. Most of these would make it necessary for me to re-implement quite some portions of Flexmojos anyway.
>
> Chris
>
>
>
>
> [ C h r i s t o f e r D u t z ]
>
> C-Ware IT-Service
> Inhaber
> Dipl. Inf. Christofer Dutz
> Karlstraße. 104, 64285 Darmstadt
>
> fon: 0 61 51 / 27315 - 61
> fax: 0 61 51 / 27315 - 64
> mobil: 0171 / 7 444 2 33
> email: christofer.dutz@c-ware.de
>
> http://www.c-ware.de
>
> UStId-Nr. DE195700962
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im Auftrag von Carlos Rovira
> Gesendet: Sonntag, 26. August 2012 18:43
> An: flex-dev@incubator.apache.org
> Betreff: Re: [OT] Current status on Flexunit4?
>
> Hi Chris,
>
> could flexmojos be as well in ASF? (only a thought ;))
>
> best,
>
> Carlos
>
> 2012/8/26 Omar Gonzalez <om...@gmail.com>:
>> On Sunday, August 26, 2012, christofer.dutz@c-ware.de wrote:
>>
>>> Hi,
>>>
>>> This topic might be a liitle off-topic, but as I have read quite a
>>> few statements on Adobe and Flexunit here, I thougt it would be the
>>> best place to ask. As it seems that the Flexunit.org mailinglist
>>> isn't really active anymore.
>>>
>>> I just finished some work on Flexmojos unittesting support,
>>> especially supporting parametrized tests in conjunction with
>>> Flexunit4. Currently I don't want to push my changes back to FMs
>>> trunk, because I am not quite sure what the current status on Flexunit is.
>>>
>>> Currently Flexmojos supports two flex unit testing frameworks called
>>> "flexunit"
>>> - com.adobe.flexunit:flexunit:0.85:swc (called flexunit in FM)
>>> - com.adobe.flexunit:flexunit: 4.0-beta-2:swc (called flexunit4 in
>>> FM) I am quite unsure about the later one of them. On the Project
>>> page http://www.flexunit.org/ I can see no reference to adobe at all.
>>> Even the package structure is different and all refer to
>>> "org.flexunit". So I'm guessing this is a second project unluckily
>>> also called "Flexunit". Am I correct about this? In this case the
>>> current groupId used in FM shouldn't be "com.apache.flexunit" but
>>> something different . but what should it be instead?
>>> My second area of uncertainty regarding flexunit (from flexunit.org)
>>> is what the latest version is. The Blog on the page claims to be 4.1
>>> RC2, but the download page states 4.1 ("stable" without the RC2).
>>> Assuming the flexunit.org project is different from adobes project
>>> and that RC2 has become the final release I was thinking about using
>>> org.flexunit:flexunit:4.1.0:swc as version and would like to have
>>> this published in a public repo.
>>>
>>> It would be great if you could help me sort this out.
>>>
>>> Chris
>>>
>>>
>>> [ C h r i s t o f e r D u t z ]
>>>
>>> C-Ware IT-Service
>>> Inhaber
>>> Dipl. Inf. Christofer Dutz
>>> Karlstraße. 104, 64285 Darmstadt
>>>
>>> fon: 0 61 51 / 27315 - 61
>>> fax: 0 61 51 / 27315 - 64
>>> mobil: 0171 / 7 444 2 33
>>> email: christofer.dutz@c-ware.de <javascript:;>
>>>
>>> http://www.c-ware.de
>>>
>>> UStId-Nr. DE195700962
>>>
>>>
>>>
>> Michael Labriola and Digital Primates are currently in the process of
>> making the software grant to the ASF and FlexUnit will soon be in
>> Apache repositories. I would sit tight. ;)
>>
>> -omar
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F: +34 912 35 57 77
> CODEOSCOPIC S.A.
> Avd. del General Perón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
AW: [OT] Current status on Flexunit4?
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Hi Carlos,
well I think that after Flex becoming an ASF project it sounds sensible to think about moving a maven plugin for building flex there too. Currently I think it wouldn't be the best option to simply move Flexmojos under the hood of the ASF. And after all Velo would have to give his Ok for that.
Flexmojos in its current state supports building Flex projects starting with Flex 2.0.1.180927 and hereby is full of code handling all this downgrading.
Second thing is that Flexmojos includes a lot of other stuff that is also not under the hood of the ASF.
Third and in my opinion the thing that sometimes disturbs me most, is that flexmojos is far from the simple "compile this stuff into an swf for me please" tool. During time it has grown to support more and more stuff. This makes it difficult for tool providers to validate all the configuration options. For example IntelliJ complains about me not setting a storepass config option, which is actually only needed when packaging Air applications. So splitting this up into a simple flex-compiler and air-packaging plugin would allow configuration support to be a lot cleaner.
The solution I would opt on would be do two steps:
- Start publishing official Mavenized Flex SDKs.
- Create a new set of lightweight maven plugins each with its individual purpose.
For the first step I could provide you with my Generator, that I am currently working on (Almost finished). You could evaluate the resulting FDKs and fine-tune them, if you think they need optimizing. These FDKs should then be officially hosted on the ASF Maven servers. After this is done these FDKs would then be the base for building a set of lightweight maven plugins. Each one dealing with its individual part of a flex projects build lifecycle:
- Compiling AS and MXML files to SWFs and SWCs (maven-flex-compiler-plugin)
- Code Generation (maven-flex-code-generator-plugin)
- UnitTesting (maven-flex-unittest-plugin)
- Air Packaging (maven-air-packaging-plugin)
- Optimizing the SWFs and SWCs (maven-flex-optimizer-plugin)
- Deploying all needed Flex artifacts in a WAR project (maven-flex-war-deployment-plugin)
- ...
The good thing about this would be that they could be developed, maintained, versioned and released independently.
I would be more than glad to help working on this and even already have a bunch of improvements I would like to introduce while doing so. Most of these would make it necessary for me to re-implement quite some portions of Flexmojos anyway.
Chris
[ C h r i s t o f e r D u t z ]
C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Karlstraße. 104, 64285 Darmstadt
fon: 0 61 51 / 27315 - 61
fax: 0 61 51 / 27315 - 64
mobil: 0171 / 7 444 2 33
email: christofer.dutz@c-ware.de
http://www.c-ware.de
UStId-Nr. DE195700962
-----Ursprüngliche Nachricht-----
Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im Auftrag von Carlos Rovira
Gesendet: Sonntag, 26. August 2012 18:43
An: flex-dev@incubator.apache.org
Betreff: Re: [OT] Current status on Flexunit4?
Hi Chris,
could flexmojos be as well in ASF? (only a thought ;))
best,
Carlos
2012/8/26 Omar Gonzalez <om...@gmail.com>:
> On Sunday, August 26, 2012, christofer.dutz@c-ware.de wrote:
>
>> Hi,
>>
>> This topic might be a liitle off-topic, but as I have read quite a
>> few statements on Adobe and Flexunit here, I thougt it would be the
>> best place to ask. As it seems that the Flexunit.org mailinglist
>> isn't really active anymore.
>>
>> I just finished some work on Flexmojos unittesting support,
>> especially supporting parametrized tests in conjunction with
>> Flexunit4. Currently I don't want to push my changes back to FMs
>> trunk, because I am not quite sure what the current status on Flexunit is.
>>
>> Currently Flexmojos supports two flex unit testing frameworks called
>> "flexunit"
>> - com.adobe.flexunit:flexunit:0.85:swc (called flexunit in FM)
>> - com.adobe.flexunit:flexunit: 4.0-beta-2:swc (called flexunit4 in
>> FM) I am quite unsure about the later one of them. On the Project
>> page http://www.flexunit.org/ I can see no reference to adobe at all.
>> Even the package structure is different and all refer to
>> "org.flexunit". So I'm guessing this is a second project unluckily
>> also called "Flexunit". Am I correct about this? In this case the
>> current groupId used in FM shouldn't be "com.apache.flexunit" but
>> something different . but what should it be instead?
>> My second area of uncertainty regarding flexunit (from flexunit.org)
>> is what the latest version is. The Blog on the page claims to be 4.1
>> RC2, but the download page states 4.1 ("stable" without the RC2).
>> Assuming the flexunit.org project is different from adobes project
>> and that RC2 has become the final release I was thinking about using
>> org.flexunit:flexunit:4.1.0:swc as version and would like to have
>> this published in a public repo.
>>
>> It would be great if you could help me sort this out.
>>
>> Chris
>>
>>
>> [ C h r i s t o f e r D u t z ]
>>
>> C-Ware IT-Service
>> Inhaber
>> Dipl. Inf. Christofer Dutz
>> Karlstraße. 104, 64285 Darmstadt
>>
>> fon: 0 61 51 / 27315 - 61
>> fax: 0 61 51 / 27315 - 64
>> mobil: 0171 / 7 444 2 33
>> email: christofer.dutz@c-ware.de <javascript:;>
>>
>> http://www.c-ware.de
>>
>> UStId-Nr. DE195700962
>>
>>
>>
> Michael Labriola and Digital Primates are currently in the process of
> making the software grant to the ASF and FlexUnit will soon be in
> Apache repositories. I would sit tight. ;)
>
> -omar
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
Re: [OT] Current status on Flexunit4?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Chris,
could flexmojos be as well in ASF? (only a thought ;))
best,
Carlos
2012/8/26 Omar Gonzalez <om...@gmail.com>:
> On Sunday, August 26, 2012, christofer.dutz@c-ware.de wrote:
>
>> Hi,
>>
>> This topic might be a liitle off-topic, but as I have read quite a few
>> statements on Adobe and Flexunit here, I thougt it would be the best place
>> to ask. As it seems that the Flexunit.org mailinglist isn't really active
>> anymore.
>>
>> I just finished some work on Flexmojos unittesting support, especially
>> supporting parametrized tests in conjunction with Flexunit4. Currently I
>> don't want to push my changes back to FMs trunk, because I am not quite
>> sure what the current status on Flexunit is.
>>
>> Currently Flexmojos supports two flex unit testing frameworks called
>> "flexunit"
>> - com.adobe.flexunit:flexunit:0.85:swc (called flexunit in FM)
>> - com.adobe.flexunit:flexunit: 4.0-beta-2:swc (called flexunit4 in FM)
>> I am quite unsure about the later one of them. On the Project page
>> http://www.flexunit.org/ I can see no reference to adobe at all. Even the
>> package structure is different and all refer to "org.flexunit". So I'm
>> guessing this is a second project unluckily also called "Flexunit". Am I
>> correct about this? In this case the current groupId used in FM shouldn't
>> be "com.apache.flexunit" but something different . but what should it be
>> instead?
>> My second area of uncertainty regarding flexunit (from flexunit.org) is
>> what the latest version is. The Blog on the page claims to be 4.1 RC2, but
>> the download page states 4.1 ("stable" without the RC2).
>> Assuming the flexunit.org project is different from adobes project and
>> that RC2 has become the final release I was thinking about using
>> org.flexunit:flexunit:4.1.0:swc as version and would like to have this
>> published in a public repo.
>>
>> It would be great if you could help me sort this out.
>>
>> Chris
>>
>>
>> [ C h r i s t o f e r D u t z ]
>>
>> C-Ware IT-Service
>> Inhaber
>> Dipl. Inf. Christofer Dutz
>> Karlstraße. 104, 64285 Darmstadt
>>
>> fon: 0 61 51 / 27315 - 61
>> fax: 0 61 51 / 27315 - 64
>> mobil: 0171 / 7 444 2 33
>> email: christofer.dutz@c-ware.de <javascript:;>
>>
>> http://www.c-ware.de
>>
>> UStId-Nr. DE195700962
>>
>>
>>
> Michael Labriola and Digital Primates are currently in the process of
> making the software grant to the ASF and FlexUnit will soon be in Apache
> repositories. I would sit tight. ;)
>
> -omar
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid
Re: [OT] Current status on Flexunit4?
Posted by Omar Gonzalez <om...@gmail.com>.
On Sunday, August 26, 2012, christofer.dutz@c-ware.de wrote:
> Hi,
>
> This topic might be a liitle off-topic, but as I have read quite a few
> statements on Adobe and Flexunit here, I thougt it would be the best place
> to ask. As it seems that the Flexunit.org mailinglist isn't really active
> anymore.
>
> I just finished some work on Flexmojos unittesting support, especially
> supporting parametrized tests in conjunction with Flexunit4. Currently I
> don't want to push my changes back to FMs trunk, because I am not quite
> sure what the current status on Flexunit is.
>
> Currently Flexmojos supports two flex unit testing frameworks called
> "flexunit"
> - com.adobe.flexunit:flexunit:0.85:swc (called flexunit in FM)
> - com.adobe.flexunit:flexunit: 4.0-beta-2:swc (called flexunit4 in FM)
> I am quite unsure about the later one of them. On the Project page
> http://www.flexunit.org/ I can see no reference to adobe at all. Even the
> package structure is different and all refer to "org.flexunit". So I'm
> guessing this is a second project unluckily also called "Flexunit". Am I
> correct about this? In this case the current groupId used in FM shouldn't
> be "com.apache.flexunit" but something different . but what should it be
> instead?
> My second area of uncertainty regarding flexunit (from flexunit.org) is
> what the latest version is. The Blog on the page claims to be 4.1 RC2, but
> the download page states 4.1 ("stable" without the RC2).
> Assuming the flexunit.org project is different from adobes project and
> that RC2 has become the final release I was thinking about using
> org.flexunit:flexunit:4.1.0:swc as version and would like to have this
> published in a public repo.
>
> It would be great if you could help me sort this out.
>
> Chris
>
>
> [ C h r i s t o f e r D u t z ]
>
> C-Ware IT-Service
> Inhaber
> Dipl. Inf. Christofer Dutz
> Karlstraße. 104, 64285 Darmstadt
>
> fon: 0 61 51 / 27315 - 61
> fax: 0 61 51 / 27315 - 64
> mobil: 0171 / 7 444 2 33
> email: christofer.dutz@c-ware.de <javascript:;>
>
> http://www.c-ware.de
>
> UStId-Nr. DE195700962
>
>
>
Michael Labriola and Digital Primates are currently in the process of
making the software grant to the ASF and FlexUnit will soon be in Apache
repositories. I would sit tight. ;)
-omar
RE: [OT] Current status on Flexunit4?
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
Chris,
Since this isn't actually at the ASF yet, why don't we take this off list for the moment. Email me: labriola at acm.org
I will explain the few hurdles I see. I am not particularly fluent with Maven so it may be that you see easy work arounds and that we can get this all up and running easily with Yennick's fixes.
Thanks,
Mike
-----Original Message-----
From: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]
Sent: Tuesday, August 28, 2012 10:02 AM
To: flex-dev@incubator.apache.org
Subject: AW: [OT] Current status on Flexunit4?
Hi Mike,
Glad that you sorted out the confusion about FlexUnit and its versions ... this really had me worried a little now and then :-)
Seems you are having the same problem I was having with Flexmojos. Velo as the main contributor also seems to have left the Flex road and I was willing to keep it alive. So I joined that project and took over its development.
What exactly do you need help with? My current solution was to upload 4.1.0-flex to my companies repo and to make Flexmojos work with that (Had to do a little refactoring of FM to support parameterized tests, but got it working nicely). Currently the only problem I am having is that I can't push my FM changes back to the main trunk because the dependency to flexunit-4.1.0-flex is hosted nowhere. Would it be possible to simply upload the artifact somewhere publically? Or would there be any problems with this (It seems the 4.0-RC2 was uploaded by Velo into the Sonatype Maven Repo). I didn't want to do this on my own as it's not my software. If you could do that however it would be great and I would be pleased to push my stuff back to trunk.
Chris
-----Ursprüngliche Nachricht-----
Von: Michael A. Labriola [mailto:labriola@digitalprimates.net]
Gesendet: Dienstag, 28. August 2012 15:40
An: flex-dev@incubator.apache.org
Betreff: RE: [OT] Current status on Flexunit4?
>My second area of uncertainty regarding flexunit (from flexunit.org) is what the latest version is. The Blog on the page claims to be 4.1 RC2, but the download page states 4.1 ("stable" without the RC2).
>Assuming the flexunit.org project is different from adobes project and that RC2 has become the final release I was thinking about using org.flexunit:flexunit:4.1.0:swc as version and would like to have this published >in a public repo.
FlexUnit 4.x is the successor to the FlexUnit .85 version you discussed.
FlexUnit 4.1 is the current release (http://www.flexunit.org/?page_id=14) it is slightly different than the RCs before it.
FlexUnit 4.2 is the version that will be contributed to Apache
Part of the confusion comes from the fact that only the older (RC) versions were submitted to a public repo. A number of people have contributed infrastructure fixes to the project to make it easier to push it to a repo, however, none of them are complete. Part of the issue is that FlexUnit really has two flavors. There is an AS only version and a version with Flex dependencies. This is an unfortunate side effect of trying to marry to Flex, which is light on interfaces and heavy on implementations.
At the time that development last stopped, the project was being refactored to handle this differently and hence make it all a little more maven friendly (slated to be version 4.2). That is the version which will be contributed to ASF.
Yennick did some excellent work getting us 99.5% to submitting automatically to a Maven repo (https://github.com/SlevinBE/flexunit/commit/d9dc78955ed31e7ed11d390c2c38fb639b2227bc) so, to that end, I am happy to have any help getting things finalized and actually brought over. The reality of the situation is that everyone actively working on FlexUnit has left the Flex community. This means that any work on FlexUnit presently is being done solely by me and between a million other things. That means its slow going so happy to have anyone who wants to help, contribute.
Mike
AW: [OT] Current status on Flexunit4?
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Hi Mike,
Glad that you sorted out the confusion about FlexUnit and its versions ... this really had me worried a little now and then :-)
Seems you are having the same problem I was having with Flexmojos. Velo as the main contributor also seems to have left the Flex road and I was willing to keep it alive. So I joined that project and took over its development.
What exactly do you need help with? My current solution was to upload 4.1.0-flex to my companies repo and to make Flexmojos work with that (Had to do a little refactoring of FM to support parameterized tests, but got it working nicely). Currently the only problem I am having is that I can't push my FM changes back to the main trunk because the dependency to flexunit-4.1.0-flex is hosted nowhere. Would it be possible to simply upload the artifact somewhere publically? Or would there be any problems with this (It seems the 4.0-RC2 was uploaded by Velo into the Sonatype Maven Repo). I didn't want to do this on my own as it's not my software. If you could do that however it would be great and I would be pleased to push my stuff back to trunk.
Chris
-----Ursprüngliche Nachricht-----
Von: Michael A. Labriola [mailto:labriola@digitalprimates.net]
Gesendet: Dienstag, 28. August 2012 15:40
An: flex-dev@incubator.apache.org
Betreff: RE: [OT] Current status on Flexunit4?
>My second area of uncertainty regarding flexunit (from flexunit.org) is what the latest version is. The Blog on the page claims to be 4.1 RC2, but the download page states 4.1 ("stable" without the RC2).
>Assuming the flexunit.org project is different from adobes project and that RC2 has become the final release I was thinking about using org.flexunit:flexunit:4.1.0:swc as version and would like to have this published >in a public repo.
FlexUnit 4.x is the successor to the FlexUnit .85 version you discussed.
FlexUnit 4.1 is the current release (http://www.flexunit.org/?page_id=14) it is slightly different than the RCs before it.
FlexUnit 4.2 is the version that will be contributed to Apache
Part of the confusion comes from the fact that only the older (RC) versions were submitted to a public repo. A number of people have contributed infrastructure fixes to the project to make it easier to push it to a repo, however, none of them are complete. Part of the issue is that FlexUnit really has two flavors. There is an AS only version and a version with Flex dependencies. This is an unfortunate side effect of trying to marry to Flex, which is light on interfaces and heavy on implementations.
At the time that development last stopped, the project was being refactored to handle this differently and hence make it all a little more maven friendly (slated to be version 4.2). That is the version which will be contributed to ASF.
Yennick did some excellent work getting us 99.5% to submitting automatically to a Maven repo (https://github.com/SlevinBE/flexunit/commit/d9dc78955ed31e7ed11d390c2c38fb639b2227bc) so, to that end, I am happy to have any help getting things finalized and actually brought over. The reality of the situation is that everyone actively working on FlexUnit has left the Flex community. This means that any work on FlexUnit presently is being done solely by me and between a million other things. That means its slow going so happy to have anyone who wants to help, contribute.
Mike
RE: [OT] Current status on Flexunit4?
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>My second area of uncertainty regarding flexunit (from flexunit.org) is what the latest version is. The Blog on the page claims to be 4.1 RC2, but the download page states 4.1 ("stable" without the RC2).
>Assuming the flexunit.org project is different from adobes project and that RC2 has become the final release I was thinking about using org.flexunit:flexunit:4.1.0:swc as version and would like to have this published >in a public repo.
FlexUnit 4.x is the successor to the FlexUnit .85 version you discussed.
FlexUnit 4.1 is the current release (http://www.flexunit.org/?page_id=14) it is slightly different than the RCs before it.
FlexUnit 4.2 is the version that will be contributed to Apache
Part of the confusion comes from the fact that only the older (RC) versions were submitted to a public repo. A number of people have contributed infrastructure fixes to the project to make it easier to push it to a repo, however, none of them are complete. Part of the issue is that FlexUnit really has two flavors. There is an AS only version and a version with Flex dependencies. This is an unfortunate side effect of trying to marry to Flex, which is light on interfaces and heavy on implementations.
At the time that development last stopped, the project was being refactored to handle this differently and hence make it all a little more maven friendly (slated to be version 4.2). That is the version which will be contributed to ASF.
Yennick did some excellent work getting us 99.5% to submitting automatically to a Maven repo (https://github.com/SlevinBE/flexunit/commit/d9dc78955ed31e7ed11d390c2c38fb639b2227bc) so, to that end, I am happy to have any help getting things finalized and actually brought over. The reality of the situation is that everyone actively working on FlexUnit has left the Flex community. This means that any work on FlexUnit presently is being done solely by me and between a million other things. That means its slow going so happy to have anyone who wants to help, contribute.
Mike