I release it on a need base... but since I'm not working with flex right now, flexmojos just drop on my priority list....
Releasing a new flex SDK is a slow and painful process that usually requires hours testing and patching flexmojos, and I simple have other stuff more important for me right now (I still have to pay my bills (: ) The other day one guy suggested me to make access to flex SDK (on maven format) paid, may be that would made me motivated to maintain it, but I don't know, what do you think guys? On Mon, Mar 7, 2011 at 11:34 AM, Michael Krotscheck <[email protected]>wrote: > Well, there's nothing forcing you to- that's why he said "Should". However, > there are a decent number of homebrew patched SDK's out there (I know Active > Networks has one, as does Merrill Lynch). Those SDK's are normally driven > through a combination of a large difficult-to-upgrade corporate software > stack and a need to fix SDK Bugs that have been fixed in later releases. In > short, they *can't* use flex-mojos because they can't put their particular > version of the SDK into their own repository. > > Also, might I add that you'll be spared the constant pestering of "Hey, has > this SDK been released yet?". > > Michael > > > On Mar 7, 2011, at 5:05 AM, Marvin Froeder wrote: > > Why "I should"? You made me curious now.... > > On Mon, Mar 7, 2011 at 9:48 AM, Simon Morvan <[email protected]> wrote: > >> Le 07/03/2011 09:21, bryan hunt a écrit : >> >> On Mar 7, 2:23 am, Marvin Froeder<[email protected]> wrote: >>> >>>> https://docs.sonatype.org/display/FLEXMOJOS/Installing+Flex+SDK+into+. >>>> .. >>>> >>> What does this bit mean, please. >>> "The descriptors used by Flexmojos to publish Flex SDK aren't public >>> available and won't be provided. The goal is to really make this >>> process hard. If possible impossible to reproduce. People tend to >>> abuse on this, leading to ghost bugs and all kind of inconsistencies. >>> This is a very sensitive process, so be aware that even Flex SDK >>> published on Flexmojos repository can be broken." >>> >>> Thanks, >>> >>> Bryan >>> >>> velo, >> >> You really should either relase your deployment descriptor, either release >> 4.5.0.19786 on sonatype's repo. We are unable to compile flex projects >> through Maven & Flexmojos if we haven't an option to use the desired >> framework easily. (I do not mean that it should be easy to create artifacts >> from bundles but we should have an easier ability to do so) >> >> Plus : you could get some feedback and some help on that repackaging >> process. >> >> -- >> Simon >> >> > > -- > You received this message because you are subscribed to the Google > Groups "Flex Mojos" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/ > > > -- > You received this message because you are subscribed to the Google > Groups "Flex Mojos" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/ > -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
