Hi ... adding my few cents to the discussion ;-) - I would vote for streamlining the packaging and give it some package / artifact names down the path of "org.apache.flex.commons" ... no real need for the "as3" as I think the apache-flex allready sets the path. - I would make it a seperate sub-project as as3commons reference a huge amount of other libraries which I don't quite know the license status of ... I would expect some to be Apache-Bad-Style licenses and I don't want these issues to block further releases of the SDK - I would make it a seperate sub-project as as3commons is currently build with maven and the SDK is not ... - I would make it a seperate sub-project as there is no need to release all this stuff for each new SDK (Especially as I would doubt that there would be too much contributions to it ... as3commons is allready open-sourced and not much is happening ... and I'm not expecting too much to happen here)
We have lots of sub-projects that have been donated that haven't been finished or released yet ... I don't want to add another huge code base that's not taken care of. But getting an official Apache release of these would enable us to publish versions to Maven-Central, making things a lot easier for Maven people like me ;-) But with this codebase I would volunteer to get it up to shape as this is built with Maven and Flexmojos and I think this is actually the place I need to contribute after dropping the ball on all non-maven things ;-) Chris -----Ursprüngliche Nachricht----- Von: omup...@gmail.com [mailto:omup...@gmail.com] Im Auftrag von OmPrakash Muppirala Gesendet: Samstag, 5. Dezember 2015 09:33 An: dev@flex.apache.org Betreff: Re: [DISCUSS] Adopting AS3Commons Hey, you committer ;-) You have all the power to drag those components and put them in. I like your idea. Thanks, Om On Sat, Dec 5, 2015 at 12:27 AM, jude <flexcapaci...@gmail.com> wrote: > Since Flex was open sourced it's felt like to me it's stagnated. We > had all of these new components donated or proposed to be donated > proposed to be worked on and I haven't seen any of them. I think it's > because it's in some white board somewhere. I hate that. Put them in the main > branch. Put it in. > Then we can see them in code completion. Then we can start getting bug > reports as their being used. > > Put as3commons into our.main.branch.utils. If that's org.apache.utils > then fine. I also figure if someone is upgrading their SDK and we've > renamed the package then there is no conflict. They can remove the > link to as3commons.swc and all the API's will cause errors. Then they > just go in and use the new packages. > > > On Fri, Dec 4, 2015 at 1:36 PM, Michael Schmalle < > teotigraphix...@gmail.com> > wrote: > > > IIRC most of the projects have some pretty thorough unit tests as well. > > > > Mike > > > > On Fri, Dec 4, 2015 at 2:14 PM, jude <flexcapaci...@gmail.com> wrote: > > > > > +1 for renaming it. make it part of the main package. that way we > > > +have > to > > > commit to it. if we put it off to the side there's more "it's a > > > side project. we don't need to maintain it." > > > > > > On Fri, Dec 4, 2015 at 10:26 AM, Kessler CTR Mark J < > > > mark.kessler....@usmc.mil> wrote: > > > > > > > Good point, we should keep it the same then. However if we do > > > > have > to > > > > reorganize it in the future, we can go over options then. > > > > > > > > -Mark > > > > > > > > -----Original Message----- > > > > From: Alex Harui [mailto:aha...@adobe.com] > > > > Sent: Friday, December 04, 2015 10:52 AM > > > > To: dev@flex.apache.org > > > > Subject: Re: [DISCUSS] Adopting AS3Commons > > > > > > > > > > > > I'd either leave it as is: org.as3commons Or add apache: > > > > org.apache.as3commons Or add apache.flex: > > > > org.apache.flex.as3commons Or hint at Apache Commons: > > > > org.apache.commons.as3 > > > > > > > > There is backward compatibility to be considered, so if we > > > > rename the packages folks would have to change their source code > > > > to use it, so > I'd > > > > probably lean towards leaving it as is. > > > > > > > > -Alex > > > > > > > > > > > > > >
