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 2013/01/24 12:22:12 UTC
Donation of Flexmojos
Hi,
after me telling the other Flexmojos users on the FM Mailinglist that we are working on a brand-new flex plugin for maven. Velo said that he would be willing to donate Flexmojos to Apache. We just should tell him where to sign and what to do (Even if the "doing" would be something that would have to be done by me)
I think it would be a good idea to take this offer. But I wouldn't recommend directly using this code as a directly as the official Flex Plugin. More I would like to add it as some sort of scratchpad project and use the existing parts to build a new plugin and to do things differently where things aren't solved ideally.
The reason for this is that Flexmojos has become a beast to maintain, as it supports Adobe Flex 2 up to 4.6 and with my changes in the Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9. Currently you need about 8 complete FDKs to have the Testsuite working and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has made everything even worse.
The testsuite is full of tests which made sense once, but today it seems impossible to find out what they were initially meant to test. Usually when adding support for a new FDK the testsuite had errors and I simply made them pass again. I would like to setup a clean testsuite that has a more clean structure AND has documented Tests to avoid problems like this in the future.
Flexmojos has grown more and more over the years making it one monolithic plugin. Everybody using IntelliJ will probably have noticed one problem that is related to this ... IntelliJ keeps on complaining about no storagePass property being configured. This property is mandatory for creating signed Air application, and therefore is a required property, but for normal Flex application it is optional. Splitting up everything into separate mojos would make a lot of stuff easier.
The next thing is that I would like to completely overwork the Test-support. Currently Flexmojos opens a set of sockets and compiles a dedicated testrunner SWF to connect to these sockets. There have been quite some problems with this. I would therefore like to change this that the swf is served by a mini-webserver (20 LOC) and simply communicates with a rudimentary webservice on the same port.
In the TestSupport I am also thinking about using the Flex Log-Framework to support several concurrent streams of log-data and provide the means to save the log output together with the test-results. Currently debugging tests is pretty nasty.
Last not Least I think with a new plugin we could optimize tool support much better by including the Tool vendors in the process (I'm just thinking about the copy-resources problems with IntelliJ).
What do you think?
Chris
Re: Donation of Flexmojos
Posted by Avi Kessner <ak...@gmail.com>.
A godsend +1
On Jan 24, 2013 5:58 PM, "James Roland Cabresos" <j....@gmail.com>
wrote:
> I'm starting to love what I read in the mailing list lately, lots of things
> going on!
>
> +1 for Apache FlexMojos!
>
> On Thu, Jan 24, 2013 at 10:51 PM, Jose Barragan <
> jose.barragan@codeoscopic.com> wrote:
>
> > +1 I'm absolutely involve in flexmojos/flex-maven-plugin initiative :)
> >
> > For backward compatibility "Apache Flexmojos" sounds great too
> >
> > As well with Chris, flex-maven-plugin from the scratch looks like the
> best
> > way for the future Apache Flex SDK's life
> >
> > --
> > Jose Barragan
> > Software Architect Chief
> > Codeoscopic Madrid
> > C/. Infanta Mercedes, 92.
> > Planta 5. 505.
> > 28020 Madrid.
> > Tel.: +34 912 94 80 80
> >
> > On Jan 24, 2013, at 3:18 PM, Carlos Rovira <
> carlos.rovira@codeoscopic.com>
> > wrote:
> >
> > > +1 as well to Chris's plans.
> > >
> > > The future is Flex 4.9+ so better to do something from scratch that
> will
> > > learn from all flexmojos experience. People that need old SDKs and
> > > workflows always can stay in old SDKs and plugins.
> > >
> > > Like the idea to support IDEs so they can integrate more easily the
> > > workflow of the plugin.
> > >
> > >
> > >
> > > 2013/1/24 Patrick Heinzelmann <pa...@gmail.com>
> > >
> > >> +1
> > >>
> > >> Great to see where our yesterday's discussion on the flexmojos list
> > ended
> > >> ;) Great respect to Velo (and Chris now) for pushing the Flexmojos and
> > >> supporting the community by answering thousands of questions on the
> > >> flexmojos dev list.
> > >>
> > >> I think that Chris approach is the right way, to reuse some of the
> stuff
> > >> and remove a some of the legacy stuff from flexmojos to build a Apache
> > Flex
> > >> version of flexmojos. Especially that you need to deploy 8 FDKs is a
> > >> nightmare for people trying and use to build flexmojos 6.
> > >>
> > >> About IDE support, like I mentioned yesterday on the flexmojos list.
> I'm
> > >> currently working a new m2e-connector for Flexmojos and FlashBuilder,
> > which
> > >> I will hopefully release this weekend and also donate to Apache Flex.
> > >>
> > >> Regards Patrick
> > >>
> > >>
> > >> Am 24.01.2013 um 14:38 schrieb John Cunliffe <ma...@gmail.com>:
> > >>
> > >>> +1 for solid maven support in flex
> > >>>
> > >>>
> > >>> On Thu, Jan 24, 2013 at 1:21 PM, Roland Zwaga <
> roland@stackandheap.com
> > >>> wrote:
> > >>>
> > >>>> from what I know of the process:
> > >>>> -Velo needs to sign an ICLA
> > >>>> -Code can be donated as a JIRA issue, but it can also just be sent
> to
> > >> one
> > >>>> of the committers who puts it in SVN
> > >>>> -When the source is actually released by Apache Flex I believe the
> > >> headers
> > >>>> and packages need to be in order, bot for
> > >>>> the inital donation this isn't required (please correct me if I'm
> > wrong
> > >>>> anyone)
> > >>>>
> > >>>> Oh, and I'm not sure if the current open source license if
> compatible
> > >> with
> > >>>> the Apache license, so how that would
> > >>>> work exactly I don't know either. Please, people who are in the
> know,
> > >>>> comment on this :)
> > >>>>
> > >>>> cheers,
> > >>>>
> > >>>> Roland
> > >>>>
> > >>>> On 24 January 2013 13:12, christofer.dutz@c-ware.de <
> > >>>> christofer.dutz@c-ware.de> wrote:
> > >>>>
> > >>>>> Yeah ... the problem is ... could someone please write down what
> > would
> > >> be
> > >>>>> needed?
> > >>>>> - Which agreements have to be signed?
> > >>>>> - How is the code actually donated? (Jira Issue with 60MB
> > attachment?)
> > >>>>> - What steps have to be done before the code is allowed to be added
> > to
> > >>>> the
> > >>>>> Apache code repo (Headers, Package Names, Artifact IDs? And does
> his
> > >> have
> > >>>>> to happen also for "scratchpad code"?)
> > >>>>>
> > >>>>> Chris
> > >>>>>
> > >>>>> -----Ursprüngliche Nachricht-----
> > >>>>> Von: Roland Zwaga [mailto:roland@stackandheap.com]
> > >>>>> Gesendet: Donnerstag, 24. Januar 2013 12:57
> > >>>>> An: dev@flex.apache.org
> > >>>>> Betreff: Re: Donation of Flexmojos
> > >>>>>
> > >>>>> I think you you make a very clear and sensible case.
> > >>>>> +1 to accepting Velo's donation.
> > >>>>>
> > >>>>> On 24 January 2013 12:22, christofer.dutz@c-ware.de <
> > >>>>> christofer.dutz@c-ware.de> wrote:
> > >>>>>
> > >>>>>> Hi,
> > >>>>>>
> > >>>>>> after me telling the other Flexmojos users on the FM Mailinglist
> > that
> > >>>>>> we are working on a brand-new flex plugin for maven. Velo said
> that
> > he
> > >>>>>> would be willing to donate Flexmojos to Apache. We just should
> tell
> > >>>>>> him where to sign and what to do (Even if the "doing" would be
> > >>>>>> something that would have to be done by me)
> > >>>>>>
> > >>>>>> I think it would be a good idea to take this offer. But I wouldn't
> > >>>>>> recommend directly using this code as a directly as the official
> > Flex
> > >>>>>> Plugin. More I would like to add it as some sort of scratchpad
> > project
> > >>>>>> and use the existing parts to build a new plugin and to do things
> > >>>>>> differently where things aren't solved ideally.
> > >>>>>>
> > >>>>>> The reason for this is that Flexmojos has become a beast to
> > maintain,
> > >>>>>> as it supports Adobe Flex 2 up to 4.6 and with my changes in the
> > >>>>>> Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
> > >>>>>> Currently you need about 8 complete FDKs to have the Testsuite
> > working
> > >>>>>> and the mixing of group-Ids (com.adobe.flex and org.apache.flex)
> has
> > >>>>> made everything even worse.
> > >>>>>>
> > >>>>>> The testsuite is full of tests which made sense once, but today it
> > >>>>>> seems impossible to find out what they were initially meant to
> test.
> > >>>>>> Usually when adding support for a new FDK the testsuite had errors
> > and
> > >>>>>> I simply made them pass again. I would like to setup a clean
> > testsuite
> > >>>>>> that has a more clean structure AND has documented Tests to avoid
> > >>>>>> problems like this in the future.
> > >>>>>>
> > >>>>>> Flexmojos has grown more and more over the years making it one
> > >>>>>> monolithic plugin. Everybody using IntelliJ will probably have
> > noticed
> > >>>>>> one problem that is related to this ... IntelliJ keeps on
> > complaining
> > >>>>>> about no storagePass property being configured. This property is
> > >>>>>> mandatory for creating signed Air application, and therefore is a
> > >>>>>> required property, but for normal Flex application it is optional.
> > >>>>>> Splitting up everything into separate mojos would make a lot of
> > stuff
> > >>>>> easier.
> > >>>>>>
> > >>>>>> The next thing is that I would like to completely overwork the
> > >>>>>> Test-support. Currently Flexmojos opens a set of sockets and
> > compiles
> > >>>>>> a dedicated testrunner SWF to connect to these sockets. There have
> > >>>>>> been quite some problems with this. I would therefore like to
> change
> > >>>>>> this that the swf is served by a mini-webserver (20 LOC) and
> simply
> > >>>>>> communicates with a rudimentary webservice on the same port.
> > >>>>>>
> > >>>>>> In the TestSupport I am also thinking about using the Flex
> > >>>>>> Log-Framework to support several concurrent streams of log-data
> and
> > >>>>>> provide the means to save the log output together with the
> > >>>>>> test-results. Currently debugging tests is pretty nasty.
> > >>>>>>
> > >>>>>> Last not Least I think with a new plugin we could optimize tool
> > >>>>>> support much better by including the Tool vendors in the process
> > (I'm
> > >>>>>> just thinking about the copy-resources problems with IntelliJ).
> > >>>>>>
> > >>>>>> What do you think?
> > >>>>>>
> > >>>>>> Chris
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> regards,
> > >>>>> Roland
> > >>>>>
> > >>>>> --
> > >>>>> Roland Zwaga
> > >>>>> Senior Consultant | Stack & Heap BVBA
> > >>>>>
> > >>>>> +32 (0)486 16 12 62 | roland@stackandheap.com |
> > >>>>> +http://www.stackandheap.com
> > >>>>>
> > >>>>> http://zwaga.blogspot.com
> > >>>>> http://www.springactionscript.org
> > >>>>> http://www.as3commons.org
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> regards,
> > >>>> Roland
> > >>>>
> > >>>> --
> > >>>> Roland Zwaga
> > >>>> Senior Consultant | Stack & Heap BVBA
> > >>>>
> > >>>> +32 (0)486 16 12 62 | roland@stackandheap.com |
> > >>>> http://www.stackandheap.com
> > >>>>
> > >>>> http://zwaga.blogspot.com
> > >>>> http://www.springactionscript.org
> > >>>> http://www.as3commons.org
> > >>>>
> > >>
> > >>
> > >
> > >
> > > --
> > > 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
> >
> >
>
Re: Donation of Flexmojos
Posted by James Roland Cabresos <j....@gmail.com>.
I'm starting to love what I read in the mailing list lately, lots of things
going on!
+1 for Apache FlexMojos!
On Thu, Jan 24, 2013 at 10:51 PM, Jose Barragan <
jose.barragan@codeoscopic.com> wrote:
> +1 I'm absolutely involve in flexmojos/flex-maven-plugin initiative :)
>
> For backward compatibility "Apache Flexmojos" sounds great too
>
> As well with Chris, flex-maven-plugin from the scratch looks like the best
> way for the future Apache Flex SDK's life
>
> --
> Jose Barragan
> Software Architect Chief
> Codeoscopic Madrid
> C/. Infanta Mercedes, 92.
> Planta 5. 505.
> 28020 Madrid.
> Tel.: +34 912 94 80 80
>
> On Jan 24, 2013, at 3:18 PM, Carlos Rovira <ca...@codeoscopic.com>
> wrote:
>
> > +1 as well to Chris's plans.
> >
> > The future is Flex 4.9+ so better to do something from scratch that will
> > learn from all flexmojos experience. People that need old SDKs and
> > workflows always can stay in old SDKs and plugins.
> >
> > Like the idea to support IDEs so they can integrate more easily the
> > workflow of the plugin.
> >
> >
> >
> > 2013/1/24 Patrick Heinzelmann <pa...@gmail.com>
> >
> >> +1
> >>
> >> Great to see where our yesterday's discussion on the flexmojos list
> ended
> >> ;) Great respect to Velo (and Chris now) for pushing the Flexmojos and
> >> supporting the community by answering thousands of questions on the
> >> flexmojos dev list.
> >>
> >> I think that Chris approach is the right way, to reuse some of the stuff
> >> and remove a some of the legacy stuff from flexmojos to build a Apache
> Flex
> >> version of flexmojos. Especially that you need to deploy 8 FDKs is a
> >> nightmare for people trying and use to build flexmojos 6.
> >>
> >> About IDE support, like I mentioned yesterday on the flexmojos list. I'm
> >> currently working a new m2e-connector for Flexmojos and FlashBuilder,
> which
> >> I will hopefully release this weekend and also donate to Apache Flex.
> >>
> >> Regards Patrick
> >>
> >>
> >> Am 24.01.2013 um 14:38 schrieb John Cunliffe <ma...@gmail.com>:
> >>
> >>> +1 for solid maven support in flex
> >>>
> >>>
> >>> On Thu, Jan 24, 2013 at 1:21 PM, Roland Zwaga <roland@stackandheap.com
> >>> wrote:
> >>>
> >>>> from what I know of the process:
> >>>> -Velo needs to sign an ICLA
> >>>> -Code can be donated as a JIRA issue, but it can also just be sent to
> >> one
> >>>> of the committers who puts it in SVN
> >>>> -When the source is actually released by Apache Flex I believe the
> >> headers
> >>>> and packages need to be in order, bot for
> >>>> the inital donation this isn't required (please correct me if I'm
> wrong
> >>>> anyone)
> >>>>
> >>>> Oh, and I'm not sure if the current open source license if compatible
> >> with
> >>>> the Apache license, so how that would
> >>>> work exactly I don't know either. Please, people who are in the know,
> >>>> comment on this :)
> >>>>
> >>>> cheers,
> >>>>
> >>>> Roland
> >>>>
> >>>> On 24 January 2013 13:12, christofer.dutz@c-ware.de <
> >>>> christofer.dutz@c-ware.de> wrote:
> >>>>
> >>>>> Yeah ... the problem is ... could someone please write down what
> would
> >> be
> >>>>> needed?
> >>>>> - Which agreements have to be signed?
> >>>>> - How is the code actually donated? (Jira Issue with 60MB
> attachment?)
> >>>>> - What steps have to be done before the code is allowed to be added
> to
> >>>> the
> >>>>> Apache code repo (Headers, Package Names, Artifact IDs? And does his
> >> have
> >>>>> to happen also for "scratchpad code"?)
> >>>>>
> >>>>> Chris
> >>>>>
> >>>>> -----Ursprüngliche Nachricht-----
> >>>>> Von: Roland Zwaga [mailto:roland@stackandheap.com]
> >>>>> Gesendet: Donnerstag, 24. Januar 2013 12:57
> >>>>> An: dev@flex.apache.org
> >>>>> Betreff: Re: Donation of Flexmojos
> >>>>>
> >>>>> I think you you make a very clear and sensible case.
> >>>>> +1 to accepting Velo's donation.
> >>>>>
> >>>>> On 24 January 2013 12:22, christofer.dutz@c-ware.de <
> >>>>> christofer.dutz@c-ware.de> wrote:
> >>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> after me telling the other Flexmojos users on the FM Mailinglist
> that
> >>>>>> we are working on a brand-new flex plugin for maven. Velo said that
> he
> >>>>>> would be willing to donate Flexmojos to Apache. We just should tell
> >>>>>> him where to sign and what to do (Even if the "doing" would be
> >>>>>> something that would have to be done by me)
> >>>>>>
> >>>>>> I think it would be a good idea to take this offer. But I wouldn't
> >>>>>> recommend directly using this code as a directly as the official
> Flex
> >>>>>> Plugin. More I would like to add it as some sort of scratchpad
> project
> >>>>>> and use the existing parts to build a new plugin and to do things
> >>>>>> differently where things aren't solved ideally.
> >>>>>>
> >>>>>> The reason for this is that Flexmojos has become a beast to
> maintain,
> >>>>>> as it supports Adobe Flex 2 up to 4.6 and with my changes in the
> >>>>>> Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
> >>>>>> Currently you need about 8 complete FDKs to have the Testsuite
> working
> >>>>>> and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has
> >>>>> made everything even worse.
> >>>>>>
> >>>>>> The testsuite is full of tests which made sense once, but today it
> >>>>>> seems impossible to find out what they were initially meant to test.
> >>>>>> Usually when adding support for a new FDK the testsuite had errors
> and
> >>>>>> I simply made them pass again. I would like to setup a clean
> testsuite
> >>>>>> that has a more clean structure AND has documented Tests to avoid
> >>>>>> problems like this in the future.
> >>>>>>
> >>>>>> Flexmojos has grown more and more over the years making it one
> >>>>>> monolithic plugin. Everybody using IntelliJ will probably have
> noticed
> >>>>>> one problem that is related to this ... IntelliJ keeps on
> complaining
> >>>>>> about no storagePass property being configured. This property is
> >>>>>> mandatory for creating signed Air application, and therefore is a
> >>>>>> required property, but for normal Flex application it is optional.
> >>>>>> Splitting up everything into separate mojos would make a lot of
> stuff
> >>>>> easier.
> >>>>>>
> >>>>>> The next thing is that I would like to completely overwork the
> >>>>>> Test-support. Currently Flexmojos opens a set of sockets and
> compiles
> >>>>>> a dedicated testrunner SWF to connect to these sockets. There have
> >>>>>> been quite some problems with this. I would therefore like to change
> >>>>>> this that the swf is served by a mini-webserver (20 LOC) and simply
> >>>>>> communicates with a rudimentary webservice on the same port.
> >>>>>>
> >>>>>> In the TestSupport I am also thinking about using the Flex
> >>>>>> Log-Framework to support several concurrent streams of log-data and
> >>>>>> provide the means to save the log output together with the
> >>>>>> test-results. Currently debugging tests is pretty nasty.
> >>>>>>
> >>>>>> Last not Least I think with a new plugin we could optimize tool
> >>>>>> support much better by including the Tool vendors in the process
> (I'm
> >>>>>> just thinking about the copy-resources problems with IntelliJ).
> >>>>>>
> >>>>>> What do you think?
> >>>>>>
> >>>>>> Chris
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> regards,
> >>>>> Roland
> >>>>>
> >>>>> --
> >>>>> Roland Zwaga
> >>>>> Senior Consultant | Stack & Heap BVBA
> >>>>>
> >>>>> +32 (0)486 16 12 62 | roland@stackandheap.com |
> >>>>> +http://www.stackandheap.com
> >>>>>
> >>>>> http://zwaga.blogspot.com
> >>>>> http://www.springactionscript.org
> >>>>> http://www.as3commons.org
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> regards,
> >>>> Roland
> >>>>
> >>>> --
> >>>> Roland Zwaga
> >>>> Senior Consultant | Stack & Heap BVBA
> >>>>
> >>>> +32 (0)486 16 12 62 | roland@stackandheap.com |
> >>>> http://www.stackandheap.com
> >>>>
> >>>> http://zwaga.blogspot.com
> >>>> http://www.springactionscript.org
> >>>> http://www.as3commons.org
> >>>>
> >>
> >>
> >
> >
> > --
> > 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
>
>
Re: Donation of Flexmojos
Posted by Jose Barragan <jo...@codeoscopic.com>.
+1 I'm absolutely involve in flexmojos/flex-maven-plugin initiative :)
For backward compatibility "Apache Flexmojos" sounds great too
As well with Chris, flex-maven-plugin from the scratch looks like the best way for the future Apache Flex SDK's life
--
Jose Barragan
Software Architect Chief
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta 5. 505.
28020 Madrid.
Tel.: +34 912 94 80 80
On Jan 24, 2013, at 3:18 PM, Carlos Rovira <ca...@codeoscopic.com> wrote:
> +1 as well to Chris's plans.
>
> The future is Flex 4.9+ so better to do something from scratch that will
> learn from all flexmojos experience. People that need old SDKs and
> workflows always can stay in old SDKs and plugins.
>
> Like the idea to support IDEs so they can integrate more easily the
> workflow of the plugin.
>
>
>
> 2013/1/24 Patrick Heinzelmann <pa...@gmail.com>
>
>> +1
>>
>> Great to see where our yesterday's discussion on the flexmojos list ended
>> ;) Great respect to Velo (and Chris now) for pushing the Flexmojos and
>> supporting the community by answering thousands of questions on the
>> flexmojos dev list.
>>
>> I think that Chris approach is the right way, to reuse some of the stuff
>> and remove a some of the legacy stuff from flexmojos to build a Apache Flex
>> version of flexmojos. Especially that you need to deploy 8 FDKs is a
>> nightmare for people trying and use to build flexmojos 6.
>>
>> About IDE support, like I mentioned yesterday on the flexmojos list. I'm
>> currently working a new m2e-connector for Flexmojos and FlashBuilder, which
>> I will hopefully release this weekend and also donate to Apache Flex.
>>
>> Regards Patrick
>>
>>
>> Am 24.01.2013 um 14:38 schrieb John Cunliffe <ma...@gmail.com>:
>>
>>> +1 for solid maven support in flex
>>>
>>>
>>> On Thu, Jan 24, 2013 at 1:21 PM, Roland Zwaga <roland@stackandheap.com
>>> wrote:
>>>
>>>> from what I know of the process:
>>>> -Velo needs to sign an ICLA
>>>> -Code can be donated as a JIRA issue, but it can also just be sent to
>> one
>>>> of the committers who puts it in SVN
>>>> -When the source is actually released by Apache Flex I believe the
>> headers
>>>> and packages need to be in order, bot for
>>>> the inital donation this isn't required (please correct me if I'm wrong
>>>> anyone)
>>>>
>>>> Oh, and I'm not sure if the current open source license if compatible
>> with
>>>> the Apache license, so how that would
>>>> work exactly I don't know either. Please, people who are in the know,
>>>> comment on this :)
>>>>
>>>> cheers,
>>>>
>>>> Roland
>>>>
>>>> On 24 January 2013 13:12, christofer.dutz@c-ware.de <
>>>> christofer.dutz@c-ware.de> wrote:
>>>>
>>>>> Yeah ... the problem is ... could someone please write down what would
>> be
>>>>> needed?
>>>>> - Which agreements have to be signed?
>>>>> - How is the code actually donated? (Jira Issue with 60MB attachment?)
>>>>> - What steps have to be done before the code is allowed to be added to
>>>> the
>>>>> Apache code repo (Headers, Package Names, Artifact IDs? And does his
>> have
>>>>> to happen also for "scratchpad code"?)
>>>>>
>>>>> Chris
>>>>>
>>>>> -----Ursprüngliche Nachricht-----
>>>>> Von: Roland Zwaga [mailto:roland@stackandheap.com]
>>>>> Gesendet: Donnerstag, 24. Januar 2013 12:57
>>>>> An: dev@flex.apache.org
>>>>> Betreff: Re: Donation of Flexmojos
>>>>>
>>>>> I think you you make a very clear and sensible case.
>>>>> +1 to accepting Velo's donation.
>>>>>
>>>>> On 24 January 2013 12:22, christofer.dutz@c-ware.de <
>>>>> christofer.dutz@c-ware.de> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> after me telling the other Flexmojos users on the FM Mailinglist that
>>>>>> we are working on a brand-new flex plugin for maven. Velo said that he
>>>>>> would be willing to donate Flexmojos to Apache. We just should tell
>>>>>> him where to sign and what to do (Even if the "doing" would be
>>>>>> something that would have to be done by me)
>>>>>>
>>>>>> I think it would be a good idea to take this offer. But I wouldn't
>>>>>> recommend directly using this code as a directly as the official Flex
>>>>>> Plugin. More I would like to add it as some sort of scratchpad project
>>>>>> and use the existing parts to build a new plugin and to do things
>>>>>> differently where things aren't solved ideally.
>>>>>>
>>>>>> The reason for this is that Flexmojos has become a beast to maintain,
>>>>>> as it supports Adobe Flex 2 up to 4.6 and with my changes in the
>>>>>> Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
>>>>>> Currently you need about 8 complete FDKs to have the Testsuite working
>>>>>> and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has
>>>>> made everything even worse.
>>>>>>
>>>>>> The testsuite is full of tests which made sense once, but today it
>>>>>> seems impossible to find out what they were initially meant to test.
>>>>>> Usually when adding support for a new FDK the testsuite had errors and
>>>>>> I simply made them pass again. I would like to setup a clean testsuite
>>>>>> that has a more clean structure AND has documented Tests to avoid
>>>>>> problems like this in the future.
>>>>>>
>>>>>> Flexmojos has grown more and more over the years making it one
>>>>>> monolithic plugin. Everybody using IntelliJ will probably have noticed
>>>>>> one problem that is related to this ... IntelliJ keeps on complaining
>>>>>> about no storagePass property being configured. This property is
>>>>>> mandatory for creating signed Air application, and therefore is a
>>>>>> required property, but for normal Flex application it is optional.
>>>>>> Splitting up everything into separate mojos would make a lot of stuff
>>>>> easier.
>>>>>>
>>>>>> The next thing is that I would like to completely overwork the
>>>>>> Test-support. Currently Flexmojos opens a set of sockets and compiles
>>>>>> a dedicated testrunner SWF to connect to these sockets. There have
>>>>>> been quite some problems with this. I would therefore like to change
>>>>>> this that the swf is served by a mini-webserver (20 LOC) and simply
>>>>>> communicates with a rudimentary webservice on the same port.
>>>>>>
>>>>>> In the TestSupport I am also thinking about using the Flex
>>>>>> Log-Framework to support several concurrent streams of log-data and
>>>>>> provide the means to save the log output together with the
>>>>>> test-results. Currently debugging tests is pretty nasty.
>>>>>>
>>>>>> Last not Least I think with a new plugin we could optimize tool
>>>>>> support much better by including the Tool vendors in the process (I'm
>>>>>> just thinking about the copy-resources problems with IntelliJ).
>>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>> Chris
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> regards,
>>>>> Roland
>>>>>
>>>>> --
>>>>> Roland Zwaga
>>>>> Senior Consultant | Stack & Heap BVBA
>>>>>
>>>>> +32 (0)486 16 12 62 | roland@stackandheap.com |
>>>>> +http://www.stackandheap.com
>>>>>
>>>>> http://zwaga.blogspot.com
>>>>> http://www.springactionscript.org
>>>>> http://www.as3commons.org
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> regards,
>>>> Roland
>>>>
>>>> --
>>>> Roland Zwaga
>>>> Senior Consultant | Stack & Heap BVBA
>>>>
>>>> +32 (0)486 16 12 62 | roland@stackandheap.com |
>>>> http://www.stackandheap.com
>>>>
>>>> http://zwaga.blogspot.com
>>>> http://www.springactionscript.org
>>>> http://www.as3commons.org
>>>>
>>
>>
>
>
> --
> 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
Re: Donation of Flexmojos
Posted by Carlos Rovira <ca...@codeoscopic.com>.
+1 as well to Chris's plans.
The future is Flex 4.9+ so better to do something from scratch that will
learn from all flexmojos experience. People that need old SDKs and
workflows always can stay in old SDKs and plugins.
Like the idea to support IDEs so they can integrate more easily the
workflow of the plugin.
2013/1/24 Patrick Heinzelmann <pa...@gmail.com>
> +1
>
> Great to see where our yesterday's discussion on the flexmojos list ended
> ;) Great respect to Velo (and Chris now) for pushing the Flexmojos and
> supporting the community by answering thousands of questions on the
> flexmojos dev list.
>
> I think that Chris approach is the right way, to reuse some of the stuff
> and remove a some of the legacy stuff from flexmojos to build a Apache Flex
> version of flexmojos. Especially that you need to deploy 8 FDKs is a
> nightmare for people trying and use to build flexmojos 6.
>
> About IDE support, like I mentioned yesterday on the flexmojos list. I'm
> currently working a new m2e-connector for Flexmojos and FlashBuilder, which
> I will hopefully release this weekend and also donate to Apache Flex.
>
> Regards Patrick
>
>
> Am 24.01.2013 um 14:38 schrieb John Cunliffe <ma...@gmail.com>:
>
> > +1 for solid maven support in flex
> >
> >
> > On Thu, Jan 24, 2013 at 1:21 PM, Roland Zwaga <roland@stackandheap.com
> >wrote:
> >
> >> from what I know of the process:
> >> -Velo needs to sign an ICLA
> >> -Code can be donated as a JIRA issue, but it can also just be sent to
> one
> >> of the committers who puts it in SVN
> >> -When the source is actually released by Apache Flex I believe the
> headers
> >> and packages need to be in order, bot for
> >> the inital donation this isn't required (please correct me if I'm wrong
> >> anyone)
> >>
> >> Oh, and I'm not sure if the current open source license if compatible
> with
> >> the Apache license, so how that would
> >> work exactly I don't know either. Please, people who are in the know,
> >> comment on this :)
> >>
> >> cheers,
> >>
> >> Roland
> >>
> >> On 24 January 2013 13:12, christofer.dutz@c-ware.de <
> >> christofer.dutz@c-ware.de> wrote:
> >>
> >>> Yeah ... the problem is ... could someone please write down what would
> be
> >>> needed?
> >>> - Which agreements have to be signed?
> >>> - How is the code actually donated? (Jira Issue with 60MB attachment?)
> >>> - What steps have to be done before the code is allowed to be added to
> >> the
> >>> Apache code repo (Headers, Package Names, Artifact IDs? And does his
> have
> >>> to happen also for "scratchpad code"?)
> >>>
> >>> Chris
> >>>
> >>> -----Ursprüngliche Nachricht-----
> >>> Von: Roland Zwaga [mailto:roland@stackandheap.com]
> >>> Gesendet: Donnerstag, 24. Januar 2013 12:57
> >>> An: dev@flex.apache.org
> >>> Betreff: Re: Donation of Flexmojos
> >>>
> >>> I think you you make a very clear and sensible case.
> >>> +1 to accepting Velo's donation.
> >>>
> >>> On 24 January 2013 12:22, christofer.dutz@c-ware.de <
> >>> christofer.dutz@c-ware.de> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> after me telling the other Flexmojos users on the FM Mailinglist that
> >>>> we are working on a brand-new flex plugin for maven. Velo said that he
> >>>> would be willing to donate Flexmojos to Apache. We just should tell
> >>>> him where to sign and what to do (Even if the "doing" would be
> >>>> something that would have to be done by me)
> >>>>
> >>>> I think it would be a good idea to take this offer. But I wouldn't
> >>>> recommend directly using this code as a directly as the official Flex
> >>>> Plugin. More I would like to add it as some sort of scratchpad project
> >>>> and use the existing parts to build a new plugin and to do things
> >>>> differently where things aren't solved ideally.
> >>>>
> >>>> The reason for this is that Flexmojos has become a beast to maintain,
> >>>> as it supports Adobe Flex 2 up to 4.6 and with my changes in the
> >>>> Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
> >>>> Currently you need about 8 complete FDKs to have the Testsuite working
> >>>> and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has
> >>> made everything even worse.
> >>>>
> >>>> The testsuite is full of tests which made sense once, but today it
> >>>> seems impossible to find out what they were initially meant to test.
> >>>> Usually when adding support for a new FDK the testsuite had errors and
> >>>> I simply made them pass again. I would like to setup a clean testsuite
> >>>> that has a more clean structure AND has documented Tests to avoid
> >>>> problems like this in the future.
> >>>>
> >>>> Flexmojos has grown more and more over the years making it one
> >>>> monolithic plugin. Everybody using IntelliJ will probably have noticed
> >>>> one problem that is related to this ... IntelliJ keeps on complaining
> >>>> about no storagePass property being configured. This property is
> >>>> mandatory for creating signed Air application, and therefore is a
> >>>> required property, but for normal Flex application it is optional.
> >>>> Splitting up everything into separate mojos would make a lot of stuff
> >>> easier.
> >>>>
> >>>> The next thing is that I would like to completely overwork the
> >>>> Test-support. Currently Flexmojos opens a set of sockets and compiles
> >>>> a dedicated testrunner SWF to connect to these sockets. There have
> >>>> been quite some problems with this. I would therefore like to change
> >>>> this that the swf is served by a mini-webserver (20 LOC) and simply
> >>>> communicates with a rudimentary webservice on the same port.
> >>>>
> >>>> In the TestSupport I am also thinking about using the Flex
> >>>> Log-Framework to support several concurrent streams of log-data and
> >>>> provide the means to save the log output together with the
> >>>> test-results. Currently debugging tests is pretty nasty.
> >>>>
> >>>> Last not Least I think with a new plugin we could optimize tool
> >>>> support much better by including the Tool vendors in the process (I'm
> >>>> just thinking about the copy-resources problems with IntelliJ).
> >>>>
> >>>> What do you think?
> >>>>
> >>>> Chris
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> regards,
> >>> Roland
> >>>
> >>> --
> >>> Roland Zwaga
> >>> Senior Consultant | Stack & Heap BVBA
> >>>
> >>> +32 (0)486 16 12 62 | roland@stackandheap.com |
> >>> +http://www.stackandheap.com
> >>>
> >>> http://zwaga.blogspot.com
> >>> http://www.springactionscript.org
> >>> http://www.as3commons.org
> >>>
> >>
> >>
> >>
> >> --
> >> regards,
> >> Roland
> >>
> >> --
> >> Roland Zwaga
> >> Senior Consultant | Stack & Heap BVBA
> >>
> >> +32 (0)486 16 12 62 | roland@stackandheap.com |
> >> http://www.stackandheap.com
> >>
> >> http://zwaga.blogspot.com
> >> http://www.springactionscript.org
> >> http://www.as3commons.org
> >>
>
>
--
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
Re: Donation of Flexmojos
Posted by Patrick Heinzelmann <pa...@gmail.com>.
+1
Great to see where our yesterday's discussion on the flexmojos list ended ;) Great respect to Velo (and Chris now) for pushing the Flexmojos and supporting the community by answering thousands of questions on the flexmojos dev list.
I think that Chris approach is the right way, to reuse some of the stuff and remove a some of the legacy stuff from flexmojos to build a Apache Flex version of flexmojos. Especially that you need to deploy 8 FDKs is a nightmare for people trying and use to build flexmojos 6.
About IDE support, like I mentioned yesterday on the flexmojos list. I'm currently working a new m2e-connector for Flexmojos and FlashBuilder, which I will hopefully release this weekend and also donate to Apache Flex.
Regards Patrick
Am 24.01.2013 um 14:38 schrieb John Cunliffe <ma...@gmail.com>:
> +1 for solid maven support in flex
>
>
> On Thu, Jan 24, 2013 at 1:21 PM, Roland Zwaga <ro...@stackandheap.com>wrote:
>
>> from what I know of the process:
>> -Velo needs to sign an ICLA
>> -Code can be donated as a JIRA issue, but it can also just be sent to one
>> of the committers who puts it in SVN
>> -When the source is actually released by Apache Flex I believe the headers
>> and packages need to be in order, bot for
>> the inital donation this isn't required (please correct me if I'm wrong
>> anyone)
>>
>> Oh, and I'm not sure if the current open source license if compatible with
>> the Apache license, so how that would
>> work exactly I don't know either. Please, people who are in the know,
>> comment on this :)
>>
>> cheers,
>>
>> Roland
>>
>> On 24 January 2013 13:12, christofer.dutz@c-ware.de <
>> christofer.dutz@c-ware.de> wrote:
>>
>>> Yeah ... the problem is ... could someone please write down what would be
>>> needed?
>>> - Which agreements have to be signed?
>>> - How is the code actually donated? (Jira Issue with 60MB attachment?)
>>> - What steps have to be done before the code is allowed to be added to
>> the
>>> Apache code repo (Headers, Package Names, Artifact IDs? And does his have
>>> to happen also for "scratchpad code"?)
>>>
>>> Chris
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Roland Zwaga [mailto:roland@stackandheap.com]
>>> Gesendet: Donnerstag, 24. Januar 2013 12:57
>>> An: dev@flex.apache.org
>>> Betreff: Re: Donation of Flexmojos
>>>
>>> I think you you make a very clear and sensible case.
>>> +1 to accepting Velo's donation.
>>>
>>> On 24 January 2013 12:22, christofer.dutz@c-ware.de <
>>> christofer.dutz@c-ware.de> wrote:
>>>
>>>> Hi,
>>>>
>>>> after me telling the other Flexmojos users on the FM Mailinglist that
>>>> we are working on a brand-new flex plugin for maven. Velo said that he
>>>> would be willing to donate Flexmojos to Apache. We just should tell
>>>> him where to sign and what to do (Even if the "doing" would be
>>>> something that would have to be done by me)
>>>>
>>>> I think it would be a good idea to take this offer. But I wouldn't
>>>> recommend directly using this code as a directly as the official Flex
>>>> Plugin. More I would like to add it as some sort of scratchpad project
>>>> and use the existing parts to build a new plugin and to do things
>>>> differently where things aren't solved ideally.
>>>>
>>>> The reason for this is that Flexmojos has become a beast to maintain,
>>>> as it supports Adobe Flex 2 up to 4.6 and with my changes in the
>>>> Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
>>>> Currently you need about 8 complete FDKs to have the Testsuite working
>>>> and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has
>>> made everything even worse.
>>>>
>>>> The testsuite is full of tests which made sense once, but today it
>>>> seems impossible to find out what they were initially meant to test.
>>>> Usually when adding support for a new FDK the testsuite had errors and
>>>> I simply made them pass again. I would like to setup a clean testsuite
>>>> that has a more clean structure AND has documented Tests to avoid
>>>> problems like this in the future.
>>>>
>>>> Flexmojos has grown more and more over the years making it one
>>>> monolithic plugin. Everybody using IntelliJ will probably have noticed
>>>> one problem that is related to this ... IntelliJ keeps on complaining
>>>> about no storagePass property being configured. This property is
>>>> mandatory for creating signed Air application, and therefore is a
>>>> required property, but for normal Flex application it is optional.
>>>> Splitting up everything into separate mojos would make a lot of stuff
>>> easier.
>>>>
>>>> The next thing is that I would like to completely overwork the
>>>> Test-support. Currently Flexmojos opens a set of sockets and compiles
>>>> a dedicated testrunner SWF to connect to these sockets. There have
>>>> been quite some problems with this. I would therefore like to change
>>>> this that the swf is served by a mini-webserver (20 LOC) and simply
>>>> communicates with a rudimentary webservice on the same port.
>>>>
>>>> In the TestSupport I am also thinking about using the Flex
>>>> Log-Framework to support several concurrent streams of log-data and
>>>> provide the means to save the log output together with the
>>>> test-results. Currently debugging tests is pretty nasty.
>>>>
>>>> Last not Least I think with a new plugin we could optimize tool
>>>> support much better by including the Tool vendors in the process (I'm
>>>> just thinking about the copy-resources problems with IntelliJ).
>>>>
>>>> What do you think?
>>>>
>>>> Chris
>>>>
>>>
>>>
>>>
>>> --
>>> regards,
>>> Roland
>>>
>>> --
>>> Roland Zwaga
>>> Senior Consultant | Stack & Heap BVBA
>>>
>>> +32 (0)486 16 12 62 | roland@stackandheap.com |
>>> +http://www.stackandheap.com
>>>
>>> http://zwaga.blogspot.com
>>> http://www.springactionscript.org
>>> http://www.as3commons.org
>>>
>>
>>
>>
>> --
>> regards,
>> Roland
>>
>> --
>> Roland Zwaga
>> Senior Consultant | Stack & Heap BVBA
>>
>> +32 (0)486 16 12 62 | roland@stackandheap.com |
>> http://www.stackandheap.com
>>
>> http://zwaga.blogspot.com
>> http://www.springactionscript.org
>> http://www.as3commons.org
>>
Re: Donation of Flexmojos
Posted by John Cunliffe <ma...@gmail.com>.
+1 for solid maven support in flex
On Thu, Jan 24, 2013 at 1:21 PM, Roland Zwaga <ro...@stackandheap.com>wrote:
> from what I know of the process:
> -Velo needs to sign an ICLA
> -Code can be donated as a JIRA issue, but it can also just be sent to one
> of the committers who puts it in SVN
> -When the source is actually released by Apache Flex I believe the headers
> and packages need to be in order, bot for
> the inital donation this isn't required (please correct me if I'm wrong
> anyone)
>
> Oh, and I'm not sure if the current open source license if compatible with
> the Apache license, so how that would
> work exactly I don't know either. Please, people who are in the know,
> comment on this :)
>
> cheers,
>
> Roland
>
> On 24 January 2013 13:12, christofer.dutz@c-ware.de <
> christofer.dutz@c-ware.de> wrote:
>
> > Yeah ... the problem is ... could someone please write down what would be
> > needed?
> > - Which agreements have to be signed?
> > - How is the code actually donated? (Jira Issue with 60MB attachment?)
> > - What steps have to be done before the code is allowed to be added to
> the
> > Apache code repo (Headers, Package Names, Artifact IDs? And does his have
> > to happen also for "scratchpad code"?)
> >
> > Chris
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Roland Zwaga [mailto:roland@stackandheap.com]
> > Gesendet: Donnerstag, 24. Januar 2013 12:57
> > An: dev@flex.apache.org
> > Betreff: Re: Donation of Flexmojos
> >
> > I think you you make a very clear and sensible case.
> > +1 to accepting Velo's donation.
> >
> > On 24 January 2013 12:22, christofer.dutz@c-ware.de <
> > christofer.dutz@c-ware.de> wrote:
> >
> > > Hi,
> > >
> > > after me telling the other Flexmojos users on the FM Mailinglist that
> > > we are working on a brand-new flex plugin for maven. Velo said that he
> > > would be willing to donate Flexmojos to Apache. We just should tell
> > > him where to sign and what to do (Even if the "doing" would be
> > > something that would have to be done by me)
> > >
> > > I think it would be a good idea to take this offer. But I wouldn't
> > > recommend directly using this code as a directly as the official Flex
> > > Plugin. More I would like to add it as some sort of scratchpad project
> > > and use the existing parts to build a new plugin and to do things
> > > differently where things aren't solved ideally.
> > >
> > > The reason for this is that Flexmojos has become a beast to maintain,
> > > as it supports Adobe Flex 2 up to 4.6 and with my changes in the
> > > Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
> > > Currently you need about 8 complete FDKs to have the Testsuite working
> > > and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has
> > made everything even worse.
> > >
> > > The testsuite is full of tests which made sense once, but today it
> > > seems impossible to find out what they were initially meant to test.
> > > Usually when adding support for a new FDK the testsuite had errors and
> > > I simply made them pass again. I would like to setup a clean testsuite
> > > that has a more clean structure AND has documented Tests to avoid
> > > problems like this in the future.
> > >
> > > Flexmojos has grown more and more over the years making it one
> > > monolithic plugin. Everybody using IntelliJ will probably have noticed
> > > one problem that is related to this ... IntelliJ keeps on complaining
> > > about no storagePass property being configured. This property is
> > > mandatory for creating signed Air application, and therefore is a
> > > required property, but for normal Flex application it is optional.
> > > Splitting up everything into separate mojos would make a lot of stuff
> > easier.
> > >
> > > The next thing is that I would like to completely overwork the
> > > Test-support. Currently Flexmojos opens a set of sockets and compiles
> > > a dedicated testrunner SWF to connect to these sockets. There have
> > > been quite some problems with this. I would therefore like to change
> > > this that the swf is served by a mini-webserver (20 LOC) and simply
> > > communicates with a rudimentary webservice on the same port.
> > >
> > > In the TestSupport I am also thinking about using the Flex
> > > Log-Framework to support several concurrent streams of log-data and
> > > provide the means to save the log output together with the
> > > test-results. Currently debugging tests is pretty nasty.
> > >
> > > Last not Least I think with a new plugin we could optimize tool
> > > support much better by including the Tool vendors in the process (I'm
> > > just thinking about the copy-resources problems with IntelliJ).
> > >
> > > What do you think?
> > >
> > > Chris
> > >
> >
> >
> >
> > --
> > regards,
> > Roland
> >
> > --
> > Roland Zwaga
> > Senior Consultant | Stack & Heap BVBA
> >
> > +32 (0)486 16 12 62 | roland@stackandheap.com |
> > +http://www.stackandheap.com
> >
> > http://zwaga.blogspot.com
> > http://www.springactionscript.org
> > http://www.as3commons.org
> >
>
>
>
> --
> regards,
> Roland
>
> --
> Roland Zwaga
> Senior Consultant | Stack & Heap BVBA
>
> +32 (0)486 16 12 62 | roland@stackandheap.com |
> http://www.stackandheap.com
>
> http://zwaga.blogspot.com
> http://www.springactionscript.org
> http://www.as3commons.org
>
Re: Donation of Flexmojos
Posted by Roland Zwaga <ro...@stackandheap.com>.
from what I know of the process:
-Velo needs to sign an ICLA
-Code can be donated as a JIRA issue, but it can also just be sent to one
of the committers who puts it in SVN
-When the source is actually released by Apache Flex I believe the headers
and packages need to be in order, bot for
the inital donation this isn't required (please correct me if I'm wrong
anyone)
Oh, and I'm not sure if the current open source license if compatible with
the Apache license, so how that would
work exactly I don't know either. Please, people who are in the know,
comment on this :)
cheers,
Roland
On 24 January 2013 13:12, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> Yeah ... the problem is ... could someone please write down what would be
> needed?
> - Which agreements have to be signed?
> - How is the code actually donated? (Jira Issue with 60MB attachment?)
> - What steps have to be done before the code is allowed to be added to the
> Apache code repo (Headers, Package Names, Artifact IDs? And does his have
> to happen also for "scratchpad code"?)
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Roland Zwaga [mailto:roland@stackandheap.com]
> Gesendet: Donnerstag, 24. Januar 2013 12:57
> An: dev@flex.apache.org
> Betreff: Re: Donation of Flexmojos
>
> I think you you make a very clear and sensible case.
> +1 to accepting Velo's donation.
>
> On 24 January 2013 12:22, christofer.dutz@c-ware.de <
> christofer.dutz@c-ware.de> wrote:
>
> > Hi,
> >
> > after me telling the other Flexmojos users on the FM Mailinglist that
> > we are working on a brand-new flex plugin for maven. Velo said that he
> > would be willing to donate Flexmojos to Apache. We just should tell
> > him where to sign and what to do (Even if the "doing" would be
> > something that would have to be done by me)
> >
> > I think it would be a good idea to take this offer. But I wouldn't
> > recommend directly using this code as a directly as the official Flex
> > Plugin. More I would like to add it as some sort of scratchpad project
> > and use the existing parts to build a new plugin and to do things
> > differently where things aren't solved ideally.
> >
> > The reason for this is that Flexmojos has become a beast to maintain,
> > as it supports Adobe Flex 2 up to 4.6 and with my changes in the
> > Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
> > Currently you need about 8 complete FDKs to have the Testsuite working
> > and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has
> made everything even worse.
> >
> > The testsuite is full of tests which made sense once, but today it
> > seems impossible to find out what they were initially meant to test.
> > Usually when adding support for a new FDK the testsuite had errors and
> > I simply made them pass again. I would like to setup a clean testsuite
> > that has a more clean structure AND has documented Tests to avoid
> > problems like this in the future.
> >
> > Flexmojos has grown more and more over the years making it one
> > monolithic plugin. Everybody using IntelliJ will probably have noticed
> > one problem that is related to this ... IntelliJ keeps on complaining
> > about no storagePass property being configured. This property is
> > mandatory for creating signed Air application, and therefore is a
> > required property, but for normal Flex application it is optional.
> > Splitting up everything into separate mojos would make a lot of stuff
> easier.
> >
> > The next thing is that I would like to completely overwork the
> > Test-support. Currently Flexmojos opens a set of sockets and compiles
> > a dedicated testrunner SWF to connect to these sockets. There have
> > been quite some problems with this. I would therefore like to change
> > this that the swf is served by a mini-webserver (20 LOC) and simply
> > communicates with a rudimentary webservice on the same port.
> >
> > In the TestSupport I am also thinking about using the Flex
> > Log-Framework to support several concurrent streams of log-data and
> > provide the means to save the log output together with the
> > test-results. Currently debugging tests is pretty nasty.
> >
> > Last not Least I think with a new plugin we could optimize tool
> > support much better by including the Tool vendors in the process (I'm
> > just thinking about the copy-resources problems with IntelliJ).
> >
> > What do you think?
> >
> > Chris
> >
>
>
>
> --
> regards,
> Roland
>
> --
> Roland Zwaga
> Senior Consultant | Stack & Heap BVBA
>
> +32 (0)486 16 12 62 | roland@stackandheap.com |
> +http://www.stackandheap.com
>
> http://zwaga.blogspot.com
> http://www.springactionscript.org
> http://www.as3commons.org
>
--
regards,
Roland
--
Roland Zwaga
Senior Consultant | Stack & Heap BVBA
+32 (0)486 16 12 62 | roland@stackandheap.com | http://www.stackandheap.com
http://zwaga.blogspot.com
http://www.springactionscript.org
http://www.as3commons.org
AW: AW: AW: Donation of Flexmojos
Posted by Christofer Dutz <ch...@c-ware.de>.
The plugin skeleton is already there ... in flex-utils.
I guess starting on the main mojos "compile" would be best. But I think I would need to start this as it's a pretty tricky thing and I would let a lot of inspiration flow from flexmojos into it. As soon as the compile mojo is done, there are about 10-15 differnt little helpers needed (Test Source Prepare, Test-Runner, Flash Sandbox Registration, ...)
Unfortunately I'm currently working on getting the one plugin we have (Flexmojos) running with falcon ... as soon as that's done I would like to have FlexPMD and BLazeDS out of the door. Perhaps then I could do the Falcon Antlr4 + JBurg2 update ... then I was planning on working on the plugin (After all ... we currently do have a working solution)
Chris
-----Ursprüngliche Nachricht-----
Von: Gautam Pandey [mailto:gkptechi@gmail.com]
Gesendet: Donnerstag, 16. Oktober 2014 04:05
An: dev@flex.apache.org
Betreff: Re: AW: AW: Donation of Flexmojos
Hi Chris,
Let me know if I can help in creating new plugin. I can give minimum 2 hours daily for this.
Thanks
Gautam
Thanks & Regards
Gautam Pandey
On Wed, Oct 15, 2014 at 10:34 PM, Christofer Dutz <christofer.dutz@c-ware.de
> wrote:
> We had discussed possibilities of how this could be achieved.
> Unfortunately Velo never requested users to officially sign an ICLA.
> So they are still in possetion of the rights to that code. In order to
> donate this, they would all have to agree. This is an enormous amount
> of people I would have to ask. So we dropped this idea. We were
> thinking about creating a new plugin here at apache. Unfortunately I
> have so much stuff to do here that I can't find any time to work on that ... the skeleton is there though.
>
> But the GPL of Flexmojos shouldn't have any influence on what you
> build with Flexmojos. As far as I know, it would only be problematic,
> if you bundled Flexmojos itself with your product.
>
> Chris
>
>
> ________________________________________
> Von: Gautam Pandey <gk...@gmail.com>
> Gesendet: Mittwoch, 15. Oktober 2014 14:09
> An: dev@flex.apache.org
> Betreff: Re: AW: AW: Donation of Flexmojos
>
> Is there any progress in donating flexmojos to Apache? I am stuck
> because of GPL and I cannot go forward and use 6.0.1 as my company is
> not allowing to use GPL licensed software.
>
> Thanks & Regards
> Gautam Pandey
>
>
> On Fri, Jan 25, 2013 at 9:36 PM, Alex Harui <ah...@adobe.com> wrote:
>
> >
> >
> >
> > On 1/25/13 7:12 AM, "Greg Reddin" <gr...@gmail.com> wrote:
> >
> > > On Fri, Jan 25, 2013 at 3:35 AM, christofer.dutz@c-ware.de <
> > > christofer.dutz@c-ware.de> wrote:
> > >
> > >> So ... does this have any impact on the plans to donate? Is it
> > >> now
> > harder
> > >> to donate or does it make stuff even easier?
> > >>
> > >
> > > To my knowledge the current licensing strategy of the product has
> > > no bearing on its donation. My assumption is that, by donating it,
> > > Velo asserts that he has intellectual property rights to the
> > > software, and
> > he's
> > > passing those rights on to Apache. Apache can then relicense the
> software
> > > if/when we get ready to release it.
> > But I would say it means that a donation is now required. My idea
> > of having you just borrow code from its current repository is now
> > void because you cannot borrow GPL code.
> >
> > Also, there could be some trickiness in that Velo has to be certain
> > that
> he
> > has the right to re-license the code as Apache license. Whether he
> > does that before or after donation may not matter, but effectively,
> > it is
> being
> > re-licensed. I don't know the GPL terms and what contributor
> > agreement
> he
> > had, but that might dictate whether he has the authority to re-license.
> >
> > Finally, do we really have to have this code? How many of us
> > committers will actually make changes to and release from this code
> > base? If it
> just
> > Chris, then I would argue we don't really have a community around
> > it. I
> am
> > not motivated to work on what has been described as a old monolithic
> beast,
> > but I would be more willing to help out with the new code for the
> > Apache Flex releases.
> >
> > So, the way I see it, Velo has to re-license to Apache one way or
> > another or we have to find a way not to copy significant portions of
> > that code.
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe Systems, Inc.
> > http://blogs.adobe.com/aharui
> >
> >
>
Re: AW: AW: Donation of Flexmojos
Posted by Gautam Pandey <gk...@gmail.com>.
Hi Chris,
Let me know if I can help in creating new plugin. I can give minimum 2
hours daily for this.
Thanks
Gautam
Thanks & Regards
Gautam Pandey
On Wed, Oct 15, 2014 at 10:34 PM, Christofer Dutz <christofer.dutz@c-ware.de
> wrote:
> We had discussed possibilities of how this could be achieved.
> Unfortunately Velo never requested users to officially sign an ICLA. So
> they are still in possetion of the rights to that code. In order to donate
> this, they would all have to agree. This is an enormous amount of people I
> would have to ask. So we dropped this idea. We were thinking about creating
> a new plugin here at apache. Unfortunately I have so much stuff to do here
> that I can't find any time to work on that ... the skeleton is there though.
>
> But the GPL of Flexmojos shouldn't have any influence on what you build
> with Flexmojos. As far as I know, it would only be problematic, if you
> bundled Flexmojos itself with your product.
>
> Chris
>
>
> ________________________________________
> Von: Gautam Pandey <gk...@gmail.com>
> Gesendet: Mittwoch, 15. Oktober 2014 14:09
> An: dev@flex.apache.org
> Betreff: Re: AW: AW: Donation of Flexmojos
>
> Is there any progress in donating flexmojos to Apache? I am stuck because
> of GPL and I cannot go forward and use 6.0.1 as my company is not allowing
> to use GPL licensed software.
>
> Thanks & Regards
> Gautam Pandey
>
>
> On Fri, Jan 25, 2013 at 9:36 PM, Alex Harui <ah...@adobe.com> wrote:
>
> >
> >
> >
> > On 1/25/13 7:12 AM, "Greg Reddin" <gr...@gmail.com> wrote:
> >
> > > On Fri, Jan 25, 2013 at 3:35 AM, christofer.dutz@c-ware.de <
> > > christofer.dutz@c-ware.de> wrote:
> > >
> > >> So ... does this have any impact on the plans to donate? Is it now
> > harder
> > >> to donate or does it make stuff even easier?
> > >>
> > >
> > > To my knowledge the current licensing strategy of the product has no
> > > bearing on its donation. My assumption is that, by donating it, Velo
> > > asserts that he has intellectual property rights to the software, and
> > he's
> > > passing those rights on to Apache. Apache can then relicense the
> software
> > > if/when we get ready to release it.
> > But I would say it means that a donation is now required. My idea of
> > having
> > you just borrow code from its current repository is now void because you
> > cannot borrow GPL code.
> >
> > Also, there could be some trickiness in that Velo has to be certain that
> he
> > has the right to re-license the code as Apache license. Whether he does
> > that before or after donation may not matter, but effectively, it is
> being
> > re-licensed. I don't know the GPL terms and what contributor agreement
> he
> > had, but that might dictate whether he has the authority to re-license.
> >
> > Finally, do we really have to have this code? How many of us committers
> > will actually make changes to and release from this code base? If it
> just
> > Chris, then I would argue we don't really have a community around it. I
> am
> > not motivated to work on what has been described as a old monolithic
> beast,
> > but I would be more willing to help out with the new code for the Apache
> > Flex releases.
> >
> > So, the way I see it, Velo has to re-license to Apache one way or another
> > or
> > we have to find a way not to copy significant portions of that code.
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe Systems, Inc.
> > http://blogs.adobe.com/aharui
> >
> >
>
AW: AW: AW: Donation of Flexmojos
Posted by Christofer Dutz <ch...@c-ware.de>.
We had discussed possibilities of how this could be achieved. Unfortunately Velo never requested users to officially sign an ICLA. So they are still in possetion of the rights to that code. In order to donate this, they would all have to agree. This is an enormous amount of people I would have to ask. So we dropped this idea. We were thinking about creating a new plugin here at apache. Unfortunately I have so much stuff to do here that I can't find any time to work on that ... the skeleton is there though.
But the GPL of Flexmojos shouldn't have any influence on what you build with Flexmojos. As far as I know, it would only be problematic, if you bundled Flexmojos itself with your product.
Chris
________________________________________
Von: Gautam Pandey <gk...@gmail.com>
Gesendet: Mittwoch, 15. Oktober 2014 14:09
An: dev@flex.apache.org
Betreff: Re: AW: AW: Donation of Flexmojos
Is there any progress in donating flexmojos to Apache? I am stuck because
of GPL and I cannot go forward and use 6.0.1 as my company is not allowing
to use GPL licensed software.
Thanks & Regards
Gautam Pandey
On Fri, Jan 25, 2013 at 9:36 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 1/25/13 7:12 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>
> > On Fri, Jan 25, 2013 at 3:35 AM, christofer.dutz@c-ware.de <
> > christofer.dutz@c-ware.de> wrote:
> >
> >> So ... does this have any impact on the plans to donate? Is it now
> harder
> >> to donate or does it make stuff even easier?
> >>
> >
> > To my knowledge the current licensing strategy of the product has no
> > bearing on its donation. My assumption is that, by donating it, Velo
> > asserts that he has intellectual property rights to the software, and
> he's
> > passing those rights on to Apache. Apache can then relicense the software
> > if/when we get ready to release it.
> But I would say it means that a donation is now required. My idea of
> having
> you just borrow code from its current repository is now void because you
> cannot borrow GPL code.
>
> Also, there could be some trickiness in that Velo has to be certain that he
> has the right to re-license the code as Apache license. Whether he does
> that before or after donation may not matter, but effectively, it is being
> re-licensed. I don't know the GPL terms and what contributor agreement he
> had, but that might dictate whether he has the authority to re-license.
>
> Finally, do we really have to have this code? How many of us committers
> will actually make changes to and release from this code base? If it just
> Chris, then I would argue we don't really have a community around it. I am
> not motivated to work on what has been described as a old monolithic beast,
> but I would be more willing to help out with the new code for the Apache
> Flex releases.
>
> So, the way I see it, Velo has to re-license to Apache one way or another
> or
> we have to find a way not to copy significant portions of that code.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: AW: AW: Donation of Flexmojos
Posted by Gautam Pandey <gk...@gmail.com>.
Is there any progress in donating flexmojos to Apache? I am stuck because
of GPL and I cannot go forward and use 6.0.1 as my company is not allowing
to use GPL licensed software.
Thanks & Regards
Gautam Pandey
On Fri, Jan 25, 2013 at 9:36 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 1/25/13 7:12 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>
> > On Fri, Jan 25, 2013 at 3:35 AM, christofer.dutz@c-ware.de <
> > christofer.dutz@c-ware.de> wrote:
> >
> >> So ... does this have any impact on the plans to donate? Is it now
> harder
> >> to donate or does it make stuff even easier?
> >>
> >
> > To my knowledge the current licensing strategy of the product has no
> > bearing on its donation. My assumption is that, by donating it, Velo
> > asserts that he has intellectual property rights to the software, and
> he's
> > passing those rights on to Apache. Apache can then relicense the software
> > if/when we get ready to release it.
> But I would say it means that a donation is now required. My idea of
> having
> you just borrow code from its current repository is now void because you
> cannot borrow GPL code.
>
> Also, there could be some trickiness in that Velo has to be certain that he
> has the right to re-license the code as Apache license. Whether he does
> that before or after donation may not matter, but effectively, it is being
> re-licensed. I don't know the GPL terms and what contributor agreement he
> had, but that might dictate whether he has the authority to re-license.
>
> Finally, do we really have to have this code? How many of us committers
> will actually make changes to and release from this code base? If it just
> Chris, then I would argue we don't really have a community around it. I am
> not motivated to work on what has been described as a old monolithic beast,
> but I would be more willing to help out with the new code for the Apache
> Flex releases.
>
> So, the way I see it, Velo has to re-license to Apache one way or another
> or
> we have to find a way not to copy significant portions of that code.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: AW: AW: Donation of Flexmojos
Posted by Alex Harui <ah...@adobe.com>.
On 1/25/13 7:12 AM, "Greg Reddin" <gr...@gmail.com> wrote:
> On Fri, Jan 25, 2013 at 3:35 AM, christofer.dutz@c-ware.de <
> christofer.dutz@c-ware.de> wrote:
>
>> So ... does this have any impact on the plans to donate? Is it now harder
>> to donate or does it make stuff even easier?
>>
>
> To my knowledge the current licensing strategy of the product has no
> bearing on its donation. My assumption is that, by donating it, Velo
> asserts that he has intellectual property rights to the software, and he's
> passing those rights on to Apache. Apache can then relicense the software
> if/when we get ready to release it.
But I would say it means that a donation is now required. My idea of having
you just borrow code from its current repository is now void because you
cannot borrow GPL code.
Also, there could be some trickiness in that Velo has to be certain that he
has the right to re-license the code as Apache license. Whether he does
that before or after donation may not matter, but effectively, it is being
re-licensed. I don't know the GPL terms and what contributor agreement he
had, but that might dictate whether he has the authority to re-license.
Finally, do we really have to have this code? How many of us committers
will actually make changes to and release from this code base? If it just
Chris, then I would argue we don't really have a community around it. I am
not motivated to work on what has been described as a old monolithic beast,
but I would be more willing to help out with the new code for the Apache
Flex releases.
So, the way I see it, Velo has to re-license to Apache one way or another or
we have to find a way not to copy significant portions of that code.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: Donation of Flexmojos
Posted by Greg Reddin <gr...@gmail.com>.
On Fri, Jan 25, 2013 at 3:35 AM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> So ... does this have any impact on the plans to donate? Is it now harder
> to donate or does it make stuff even easier?
>
To my knowledge the current licensing strategy of the product has no
bearing on its donation. My assumption is that, by donating it, Velo
asserts that he has intellectual property rights to the software, and he's
passing those rights on to Apache. Apache can then relicense the software
if/when we get ready to release it.
Greg
AW: AW: AW: Donation of Flexmojos
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Ok ... I asked Velo about the licenses ... initially FM was GPL ... he changed it to Apache but changed it back to GPL because " cause at the time changing to ASL wasn't real" (Don't quite know what he meant with this ... guess he simply changed the license to Apache without doing the necessary housekeeping so he changed it back again).
So ... does this have any impact on the plans to donate? Is it now harder to donate or does it make stuff even easier?
Chris
-----Ursprüngliche Nachricht-----
Von: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]
Gesendet: Freitag, 25. Januar 2013 09:19
An: dev@flex.apache.org
Betreff: AW: AW: AW: Donation of Flexmojos
>From looking at a commit from Velo on May 27 2012 he replaced the Apache 2.0 licesne with the GNU license and removed any other licensing header from files in the repo ... so I guess Flexmojos trunk is now under GNU General public license. But ... It seems that we could assume that the Contributions prior to this are ok and the people contributing after this were only a hand full (4 to be exact ... me being one of them) ... it should be easy to ask them for permission.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 24. Januar 2013 23:47
An: dev@flex.apache.org
Betreff: Re: AW: AW: Donation of Flexmojos
https://docs.sonatype.org/display/FLEXMOJOS/License
On 1/24/13 2:36 PM, "Om" <bi...@gmail.com> wrote:
> On Thu, Jan 24, 2013 at 9:59 AM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>> It appears that FlexMojos is already under Apache license. Was it
>> always under Apache? This may mean that any contributors should know
>> they are granting certain rights to their code.
>>
>>
> Where did you see that? The project website [1][2] says that it is
> under a GNU GPL v2 license.
>
> And from what I see it is not compatible with the Apache license [3]
>
> Thanks,
> Om
>
> [1] http://code.google.com/p/flex-mojos/
> [2] http://flexmojos.sonatype.org/
> [3] http://www.apache.org/licenses/GPL-compatibility.html
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: Donation of Flexmojos
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
>From looking at a commit from Velo on May 27 2012 he replaced the Apache 2.0 licesne with the GNU license and removed any other licensing header from files in the repo ... so I guess Flexmojos trunk is now under GNU General public license. But ... It seems that we could assume that the Contributions prior to this are ok and the people contributing after this were only a hand full (4 to be exact ... me being one of them) ... it should be easy to ask them for permission.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 24. Januar 2013 23:47
An: dev@flex.apache.org
Betreff: Re: AW: AW: Donation of Flexmojos
https://docs.sonatype.org/display/FLEXMOJOS/License
On 1/24/13 2:36 PM, "Om" <bi...@gmail.com> wrote:
> On Thu, Jan 24, 2013 at 9:59 AM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>> It appears that FlexMojos is already under Apache license. Was it
>> always under Apache? This may mean that any contributors should know
>> they are granting certain rights to their code.
>>
>>
> Where did you see that? The project website [1][2] says that it is
> under a GNU GPL v2 license.
>
> And from what I see it is not compatible with the Apache license [3]
>
> Thanks,
> Om
>
> [1] http://code.google.com/p/flex-mojos/
> [2] http://flexmojos.sonatype.org/
> [3] http://www.apache.org/licenses/GPL-compatibility.html
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: Donation of Flexmojos
Posted by Alex Harui <ah...@adobe.com>.
https://docs.sonatype.org/display/FLEXMOJOS/License
On 1/24/13 2:36 PM, "Om" <bi...@gmail.com> wrote:
> On Thu, Jan 24, 2013 at 9:59 AM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>> It appears that FlexMojos is already under Apache license. Was it always
>> under Apache? This may mean that any contributors should know they are
>> granting certain rights to their code.
>>
>>
> Where did you see that? The project website [1][2] says that it is under
> a GNU GPL v2 license.
>
> And from what I see it is not compatible with the Apache license [3]
>
> Thanks,
> Om
>
> [1] http://code.google.com/p/flex-mojos/
> [2] http://flexmojos.sonatype.org/
> [3] http://www.apache.org/licenses/GPL-compatibility.html
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: Donation of Flexmojos
Posted by Om <bi...@gmail.com>.
On Thu, Jan 24, 2013 at 9:59 AM, Alex Harui <ah...@adobe.com> wrote:
>
> It appears that FlexMojos is already under Apache license. Was it always
> under Apache? This may mean that any contributors should know they are
> granting certain rights to their code.
>
>
Where did you see that? The project website [1][2] says that it is under
a GNU GPL v2 license.
And from what I see it is not compatible with the Apache license [3]
Thanks,
Om
[1] http://code.google.com/p/flex-mojos/
[2] http://flexmojos.sonatype.org/
[3] http://www.apache.org/licenses/GPL-compatibility.html
Re: AW: Donation of Flexmojos
Posted by Greg Reddin <gr...@gmail.com>.
On Thu, Jan 24, 2013 at 11:39 AM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> Well I think there never was a real formal process at Flexmojos ... at
> first you sent Velo patches and he applied them and after going to Githup
> all was handled by Pull requests from other users Repos.
>
Obviously IANAL, but my gut feeling is that people knew they were
contributing to Velo's project, essentially giving him the code to do what
he wants with it. I think an ideal situation would be to track down the
contributors and get agreement from them, but that's not practical. Let's
give it a day or so and see if someone else chimes in. If not, I'd suggest
that Velo has the rights to contribute the code and let's go through the IP
Clearance process if he's willing to do that.
Greg
Re: AW: AW: Donation of Flexmojos
Posted by Alex Harui <ah...@adobe.com>.
On 1/24/13 9:39 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> Well I think there never was a real formal process at Flexmojos ... at first
> you sent Velo patches and he applied them and after going to Githup all was
> handled by Pull requests from other users Repos.
IANAL, but it might be tricky to get it donated without going back and
asking the author of every change for permission.
It appears that FlexMojos is already under Apache license. Was it always
under Apache? This may mean that any contributors should know they are
granting certain rights to their code.
However, if your goal is not to actually work on it, but borrow parts of it
for your new Apache Flex Maven code, it might be already allowed by the
Apache license. I think you may have to do it by copying from where it
lives now and not copy entire files into our SVN. But we should make sure
of that before you start doing that.
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 24. Januar 2013 18:28
> An: dev@flex.apache.org
> Betreff: Re: AW: Donation of Flexmojos
>
>
>
>
> On 1/24/13 9:17 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
> wrote:
>
>> Well I talked to Velo ... the problem is that he thinks that there are
>> about
>> 100 people who have contributed stuff during time (Mabe this number is
>> a little high, but surely a lot of people have contributed stuff).
>>
>> Will Velo be able to donate the code if not all of the contributors agree?
> It depends on what agreement he had with the contributors. At Adobe, when you
> contributed a patch to Flex, you first had to sign an agreement giving Adobe
> all rights to your code (interestingly, Apache is not so formal about patches
> coming in via JIRA anymore). That's how we were able to donate the Flex SDK
> without hunting down all the patch contributors.
>>
>> Chris
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Greg Reddin [mailto:gredbug@gmail.com]
>> Gesendet: Donnerstag, 24. Januar 2013 17:57
>> An: dev@flex.apache.org
>> Betreff: Re: Donation of Flexmojos
>>
>> On Thu, Jan 24, 2013 at 6:12 AM, christofer.dutz@c-ware.de <
>> christofer.dutz@c-ware.de> wrote:
>>
>>> Yeah ... the problem is ... could someone please write down what
>>> would be needed?
>>>
>>
>> Hi Chris,
>>
>> After researching this, I believe we need to go through the IP
>> Clearance process. I'm willing to be convinced otherwise if someone
>> thinks it's not necessary. Here's a page describing the process:
>>
>> http://incubator.apache.org/ip-clearance/index.html
>>
>> and here's more details on the process and the forms that need to be
>> filled
>> out:
>>
>> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>>
>> The main question for Velo is whether he has sufficient rights to
>> donate the whole thing or if other parties need to be involved. If
>> other parties are involved #2 below gets more complicated. If not, I
>> think we can follow this
>> process:
>>
>> 1. Flex PMC should vote to accept the donation.
>>
>> 2. Velo sends ICLA and SGA documents:
>>
>> ICLA: http://www.apache.org/licenses/icla.txt
>> SGA: http://www.apache.org/licenses/software-grant.txt
>>
>> 3. Go through the process described at
>> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>>
>> The software tarball will be checked into the incubator. After the IP
>> Clearance process completes we can check it into the Flex repo.
>>
>> Does that clear things up enough to get started?
>>
>> Thanks,
>> Greg
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: Donation of Flexmojos
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Well I think there never was a real formal process at Flexmojos ... at first you sent Velo patches and he applied them and after going to Githup all was handled by Pull requests from other users Repos.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 24. Januar 2013 18:28
An: dev@flex.apache.org
Betreff: Re: AW: Donation of Flexmojos
On 1/24/13 9:17 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> Well I talked to Velo ... the problem is that he thinks that there are
> about
> 100 people who have contributed stuff during time (Mabe this number is
> a little high, but surely a lot of people have contributed stuff).
>
> Will Velo be able to donate the code if not all of the contributors agree?
It depends on what agreement he had with the contributors. At Adobe, when you contributed a patch to Flex, you first had to sign an agreement giving Adobe all rights to your code (interestingly, Apache is not so formal about patches coming in via JIRA anymore). That's how we were able to donate the Flex SDK without hunting down all the patch contributors.
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Greg Reddin [mailto:gredbug@gmail.com]
> Gesendet: Donnerstag, 24. Januar 2013 17:57
> An: dev@flex.apache.org
> Betreff: Re: Donation of Flexmojos
>
> On Thu, Jan 24, 2013 at 6:12 AM, christofer.dutz@c-ware.de <
> christofer.dutz@c-ware.de> wrote:
>
>> Yeah ... the problem is ... could someone please write down what
>> would be needed?
>>
>
> Hi Chris,
>
> After researching this, I believe we need to go through the IP
> Clearance process. I'm willing to be convinced otherwise if someone
> thinks it's not necessary. Here's a page describing the process:
>
> http://incubator.apache.org/ip-clearance/index.html
>
> and here's more details on the process and the forms that need to be
> filled
> out:
>
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The main question for Velo is whether he has sufficient rights to
> donate the whole thing or if other parties need to be involved. If
> other parties are involved #2 below gets more complicated. If not, I
> think we can follow this
> process:
>
> 1. Flex PMC should vote to accept the donation.
>
> 2. Velo sends ICLA and SGA documents:
>
> ICLA: http://www.apache.org/licenses/icla.txt
> SGA: http://www.apache.org/licenses/software-grant.txt
>
> 3. Go through the process described at
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The software tarball will be checked into the incubator. After the IP
> Clearance process completes we can check it into the Flex repo.
>
> Does that clear things up enough to get started?
>
> Thanks,
> Greg
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: Donation of Flexmojos
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Well I too have the rights to publish stuff there, so I could do the releasing. I Guess this would not be problematic.
Chris
-----Ursprüngliche Nachricht-----
Von: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Donnerstag, 24. Januar 2013 18:54
An: dev@flex.apache.org
Betreff: RE: Donation of Flexmojos
Hi Chris,
Will FM continue to be pushed to the same maven repo ? in this case the Velo's rights have to be transmitted as well ?
-Fred
-----Original Message-----
From: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]
Sent: Thursday, January 24, 2013 6:18 PM
To: dev@flex.apache.org
Subject: AW: Donation of Flexmojos
Well I talked to Velo ... the problem is that he thinks that there are about
100 people who have contributed stuff during time (Mabe this number is a little high, but surely a lot of people have contributed stuff).
Will Velo be able to donate the code if not all of the contributors agree?
Chris
-----Ursprüngliche Nachricht-----
Von: Greg Reddin [mailto:gredbug@gmail.com]
Gesendet: Donnerstag, 24. Januar 2013 17:57
An: dev@flex.apache.org
Betreff: Re: Donation of Flexmojos
On Thu, Jan 24, 2013 at 6:12 AM, christofer.dutz@c-ware.de < christofer.dutz@c-ware.de> wrote:
> Yeah ... the problem is ... could someone please write down what would
> be needed?
>
Hi Chris,
After researching this, I believe we need to go through the IP Clearance process. I'm willing to be convinced otherwise if someone thinks it's not necessary. Here's a page describing the process:
http://incubator.apache.org/ip-clearance/index.html
and here's more details on the process and the forms that need to be filled
out:
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The main question for Velo is whether he has sufficient rights to donate the whole thing or if other parties need to be involved. If other parties are involved #2 below gets more complicated. If not, I think we can follow this
process:
1. Flex PMC should vote to accept the donation.
2. Velo sends ICLA and SGA documents:
ICLA: http://www.apache.org/licenses/icla.txt
SGA: http://www.apache.org/licenses/software-grant.txt
3. Go through the process described at
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The software tarball will be checked into the incubator. After the IP Clearance process completes we can check it into the Flex repo.
Does that clear things up enough to get started?
Thanks,
Greg
RE: Donation of Flexmojos
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Chris,
Will FM continue to be pushed to the same maven repo ? in this case the
Velo's rights have to be transmitted as well ?
-Fred
-----Original Message-----
From: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]
Sent: Thursday, January 24, 2013 6:18 PM
To: dev@flex.apache.org
Subject: AW: Donation of Flexmojos
Well I talked to Velo ... the problem is that he thinks that there are about
100 people who have contributed stuff during time (Mabe this number is a
little high, but surely a lot of people have contributed stuff).
Will Velo be able to donate the code if not all of the contributors agree?
Chris
-----Ursprüngliche Nachricht-----
Von: Greg Reddin [mailto:gredbug@gmail.com]
Gesendet: Donnerstag, 24. Januar 2013 17:57
An: dev@flex.apache.org
Betreff: Re: Donation of Flexmojos
On Thu, Jan 24, 2013 at 6:12 AM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> Yeah ... the problem is ... could someone please write down what would
> be needed?
>
Hi Chris,
After researching this, I believe we need to go through the IP Clearance
process. I'm willing to be convinced otherwise if someone thinks it's not
necessary. Here's a page describing the process:
http://incubator.apache.org/ip-clearance/index.html
and here's more details on the process and the forms that need to be filled
out:
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The main question for Velo is whether he has sufficient rights to donate the
whole thing or if other parties need to be involved. If other parties are
involved #2 below gets more complicated. If not, I think we can follow this
process:
1. Flex PMC should vote to accept the donation.
2. Velo sends ICLA and SGA documents:
ICLA: http://www.apache.org/licenses/icla.txt
SGA: http://www.apache.org/licenses/software-grant.txt
3. Go through the process described at
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The software tarball will be checked into the incubator. After the IP
Clearance process completes we can check it into the Flex repo.
Does that clear things up enough to get started?
Thanks,
Greg
Re: AW: Donation of Flexmojos
Posted by Alex Harui <ah...@adobe.com>.
On 1/24/13 9:17 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> Well I talked to Velo ... the problem is that he thinks that there are about
> 100 people who have contributed stuff during time (Mabe this number is a
> little high, but surely a lot of people have contributed stuff).
>
> Will Velo be able to donate the code if not all of the contributors agree?
It depends on what agreement he had with the contributors. At Adobe, when
you contributed a patch to Flex, you first had to sign an agreement giving
Adobe all rights to your code (interestingly, Apache is not so formal about
patches coming in via JIRA anymore). That's how we were able to donate the
Flex SDK without hunting down all the patch contributors.
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Greg Reddin [mailto:gredbug@gmail.com]
> Gesendet: Donnerstag, 24. Januar 2013 17:57
> An: dev@flex.apache.org
> Betreff: Re: Donation of Flexmojos
>
> On Thu, Jan 24, 2013 at 6:12 AM, christofer.dutz@c-ware.de <
> christofer.dutz@c-ware.de> wrote:
>
>> Yeah ... the problem is ... could someone please write down what would
>> be needed?
>>
>
> Hi Chris,
>
> After researching this, I believe we need to go through the IP Clearance
> process. I'm willing to be convinced otherwise if someone thinks it's not
> necessary. Here's a page describing the process:
>
> http://incubator.apache.org/ip-clearance/index.html
>
> and here's more details on the process and the forms that need to be filled
> out:
>
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The main question for Velo is whether he has sufficient rights to donate the
> whole thing or if other parties need to be involved. If other parties are
> involved #2 below gets more complicated. If not, I think we can follow this
> process:
>
> 1. Flex PMC should vote to accept the donation.
>
> 2. Velo sends ICLA and SGA documents:
>
> ICLA: http://www.apache.org/licenses/icla.txt
> SGA: http://www.apache.org/licenses/software-grant.txt
>
> 3. Go through the process described at
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The software tarball will be checked into the incubator. After the IP
> Clearance process completes we can check it into the Flex repo.
>
> Does that clear things up enough to get started?
>
> Thanks,
> Greg
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: Donation of Flexmojos
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Well I talked to Velo ... the problem is that he thinks that there are about 100 people who have contributed stuff during time (Mabe this number is a little high, but surely a lot of people have contributed stuff).
Will Velo be able to donate the code if not all of the contributors agree?
Chris
-----Ursprüngliche Nachricht-----
Von: Greg Reddin [mailto:gredbug@gmail.com]
Gesendet: Donnerstag, 24. Januar 2013 17:57
An: dev@flex.apache.org
Betreff: Re: Donation of Flexmojos
On Thu, Jan 24, 2013 at 6:12 AM, christofer.dutz@c-ware.de < christofer.dutz@c-ware.de> wrote:
> Yeah ... the problem is ... could someone please write down what would
> be needed?
>
Hi Chris,
After researching this, I believe we need to go through the IP Clearance process. I'm willing to be convinced otherwise if someone thinks it's not necessary. Here's a page describing the process:
http://incubator.apache.org/ip-clearance/index.html
and here's more details on the process and the forms that need to be filled
out:
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The main question for Velo is whether he has sufficient rights to donate the whole thing or if other parties need to be involved. If other parties are involved #2 below gets more complicated. If not, I think we can follow this process:
1. Flex PMC should vote to accept the donation.
2. Velo sends ICLA and SGA documents:
ICLA: http://www.apache.org/licenses/icla.txt
SGA: http://www.apache.org/licenses/software-grant.txt
3. Go through the process described at
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The software tarball will be checked into the incubator. After the IP Clearance process completes we can check it into the Flex repo.
Does that clear things up enough to get started?
Thanks,
Greg
Re: Donation of Flexmojos
Posted by Greg Reddin <gr...@gmail.com>.
On Thu, Jan 24, 2013 at 6:12 AM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> Yeah ... the problem is ... could someone please write down what would be
> needed?
>
Hi Chris,
After researching this, I believe we need to go through the IP Clearance
process. I'm willing to be convinced otherwise if someone thinks it's not
necessary. Here's a page describing the process:
http://incubator.apache.org/ip-clearance/index.html
and here's more details on the process and the forms that need to be filled
out:
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The main question for Velo is whether he has sufficient rights to donate
the whole thing or if other parties need to be involved. If other parties
are involved #2 below gets more complicated. If not, I think we can follow
this process:
1. Flex PMC should vote to accept the donation.
2. Velo sends ICLA and SGA documents:
ICLA: http://www.apache.org/licenses/icla.txt
SGA: http://www.apache.org/licenses/software-grant.txt
3. Go through the process described at
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The software tarball will be checked into the incubator. After the IP
Clearance process completes we can check it into the Flex repo.
Does that clear things up enough to get started?
Thanks,
Greg
AW: Donation of Flexmojos
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Yeah ... the problem is ... could someone please write down what would be needed?
- Which agreements have to be signed?
- How is the code actually donated? (Jira Issue with 60MB attachment?)
- What steps have to be done before the code is allowed to be added to the Apache code repo (Headers, Package Names, Artifact IDs? And does his have to happen also for "scratchpad code"?)
Chris
-----Ursprüngliche Nachricht-----
Von: Roland Zwaga [mailto:roland@stackandheap.com]
Gesendet: Donnerstag, 24. Januar 2013 12:57
An: dev@flex.apache.org
Betreff: Re: Donation of Flexmojos
I think you you make a very clear and sensible case.
+1 to accepting Velo's donation.
On 24 January 2013 12:22, christofer.dutz@c-ware.de < christofer.dutz@c-ware.de> wrote:
> Hi,
>
> after me telling the other Flexmojos users on the FM Mailinglist that
> we are working on a brand-new flex plugin for maven. Velo said that he
> would be willing to donate Flexmojos to Apache. We just should tell
> him where to sign and what to do (Even if the "doing" would be
> something that would have to be done by me)
>
> I think it would be a good idea to take this offer. But I wouldn't
> recommend directly using this code as a directly as the official Flex
> Plugin. More I would like to add it as some sort of scratchpad project
> and use the existing parts to build a new plugin and to do things
> differently where things aren't solved ideally.
>
> The reason for this is that Flexmojos has become a beast to maintain,
> as it supports Adobe Flex 2 up to 4.6 and with my changes in the
> Flexmojos 6.x branch it even supports Apache Flex 4.8 and 4.9.
> Currently you need about 8 complete FDKs to have the Testsuite working
> and the mixing of group-Ids (com.adobe.flex and org.apache.flex) has made everything even worse.
>
> The testsuite is full of tests which made sense once, but today it
> seems impossible to find out what they were initially meant to test.
> Usually when adding support for a new FDK the testsuite had errors and
> I simply made them pass again. I would like to setup a clean testsuite
> that has a more clean structure AND has documented Tests to avoid
> problems like this in the future.
>
> Flexmojos has grown more and more over the years making it one
> monolithic plugin. Everybody using IntelliJ will probably have noticed
> one problem that is related to this ... IntelliJ keeps on complaining
> about no storagePass property being configured. This property is
> mandatory for creating signed Air application, and therefore is a
> required property, but for normal Flex application it is optional.
> Splitting up everything into separate mojos would make a lot of stuff easier.
>
> The next thing is that I would like to completely overwork the
> Test-support. Currently Flexmojos opens a set of sockets and compiles
> a dedicated testrunner SWF to connect to these sockets. There have
> been quite some problems with this. I would therefore like to change
> this that the swf is served by a mini-webserver (20 LOC) and simply
> communicates with a rudimentary webservice on the same port.
>
> In the TestSupport I am also thinking about using the Flex
> Log-Framework to support several concurrent streams of log-data and
> provide the means to save the log output together with the
> test-results. Currently debugging tests is pretty nasty.
>
> Last not Least I think with a new plugin we could optimize tool
> support much better by including the Tool vendors in the process (I'm
> just thinking about the copy-resources problems with IntelliJ).
>
> What do you think?
>
> Chris
>
--
regards,
Roland
--
Roland Zwaga
Senior Consultant | Stack & Heap BVBA
+32 (0)486 16 12 62 | roland@stackandheap.com |
+http://www.stackandheap.com
http://zwaga.blogspot.com
http://www.springactionscript.org
http://www.as3commons.org
Re: Donation of Flexmojos
Posted by Roland Zwaga <ro...@stackandheap.com>.
I think you you make a very clear and sensible case.
+1 to accepting Velo's donation.
On 24 January 2013 12:22, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> Hi,
>
> after me telling the other Flexmojos users on the FM Mailinglist that we
> are working on a brand-new flex plugin for maven. Velo said that he would
> be willing to donate Flexmojos to Apache. We just should tell him where to
> sign and what to do (Even if the "doing" would be something that would have
> to be done by me)
>
> I think it would be a good idea to take this offer. But I wouldn't
> recommend directly using this code as a directly as the official Flex
> Plugin. More I would like to add it as some sort of scratchpad project and
> use the existing parts to build a new plugin and to do things differently
> where things aren't solved ideally.
>
> The reason for this is that Flexmojos has become a beast to maintain, as
> it supports Adobe Flex 2 up to 4.6 and with my changes in the Flexmojos 6.x
> branch it even supports Apache Flex 4.8 and 4.9. Currently you need about 8
> complete FDKs to have the Testsuite working and the mixing of group-Ids
> (com.adobe.flex and org.apache.flex) has made everything even worse.
>
> The testsuite is full of tests which made sense once, but today it seems
> impossible to find out what they were initially meant to test. Usually when
> adding support for a new FDK the testsuite had errors and I simply made
> them pass again. I would like to setup a clean testsuite that has a more
> clean structure AND has documented Tests to avoid problems like this in the
> future.
>
> Flexmojos has grown more and more over the years making it one monolithic
> plugin. Everybody using IntelliJ will probably have noticed one problem
> that is related to this ... IntelliJ keeps on complaining about no
> storagePass property being configured. This property is mandatory for
> creating signed Air application, and therefore is a required property, but
> for normal Flex application it is optional. Splitting up everything into
> separate mojos would make a lot of stuff easier.
>
> The next thing is that I would like to completely overwork the
> Test-support. Currently Flexmojos opens a set of sockets and compiles a
> dedicated testrunner SWF to connect to these sockets. There have been quite
> some problems with this. I would therefore like to change this that the swf
> is served by a mini-webserver (20 LOC) and simply communicates with a
> rudimentary webservice on the same port.
>
> In the TestSupport I am also thinking about using the Flex Log-Framework
> to support several concurrent streams of log-data and provide the means to
> save the log output together with the test-results. Currently debugging
> tests is pretty nasty.
>
> Last not Least I think with a new plugin we could optimize tool support
> much better by including the Tool vendors in the process (I'm just thinking
> about the copy-resources problems with IntelliJ).
>
> What do you think?
>
> Chris
>
--
regards,
Roland
--
Roland Zwaga
Senior Consultant | Stack & Heap BVBA
+32 (0)486 16 12 62 | roland@stackandheap.com | http://www.stackandheap.com
http://zwaga.blogspot.com
http://www.springactionscript.org
http://www.as3commons.org