Hi Justin, forget my last sentence ;-) I noticed one project using some flex maven plugin I had never heard of before and thought it was Squiggly but as I couldn't find the module I wanted to post, I sort of forgot to delete that partial sentence.
Well then: Please help with the legal issues required to release BlazeDS :-) I would even recommend to clean up the project and throw out the old stuff surrounding the "modules" directory, which seems to be the only part that's needed. I would like to tag BlazeDS and then move everything in the modules directory to become the new project root. This would eliminate the entire confusion. Chris ________________________________________ Von: Justin Mclean <jus...@classsoftware.com> Gesendet: Freitag, 5. September 2014 14:25 An: dev@flex.apache.org Betreff: Re: Changing our release strategy? Hi, > What I will personally put more effort in, is finally releasing the > Mavenizer. After that's done I could release Flexmojos 7.1 ... in my opinion > BlazeDS should already be in a releasable state. Legally releasable may be the issue here, as I said quite a few times happy to help out get this released. > Releasing BlazeDS would eliminate one more Adobe dependency from the > Installer that is causing some trouble currently. Yep all for that. > In Squiggly I noticed some modules There's no modules and basically zero required external dependancies (other than the Flex SDK), so not sure what you mean there. Thanks, Justin
