Well to give my few cents to the discussion: I remember when I started using Flexmojos about 2 Years ago it was a total struggle to get everything up and running. There were lots of different people posting on lots of different blogs how to build flex project using Flexmojos using sdks from lots of different company repositories. I ended up adding lots of remote repositories to my Artifacotry and having a total version mess in it. Currently I really enjoy upgrading my sdk to the latest version because I know it will work. So I sort of agree with Velo to keep it that way as the only perfect solution seems to be impossible (Adobe maintaining and hosting their mavenized SDKs).
Chris 2011/3/8 Simon Morvan <[email protected]> > Le 08/03/2011 17:02, Marvin Froeder a écrit : > > On Tue, Mar 8, 2011 at 12:37 PM, Simon Morvan <[email protected]> wrote: > >> AFAIK, the Sonatype repository isn't publically writable. Releasing the >> tools doesn't force you to accept publishing unofficial (aka, not made by >> you) mavenized SDKs. >> Moreover, the tool can be enhanced by the whole community and the issues >> each new SDK brings can be solved easily. >> This neither doesn't force you to accept modifications on the tools itself >> but you could receive interesting enhancement I think, and maybe discover >> some "responsible" guys in the community that you could trust and could help >> you with the mavenization of adobe builds. >> > > I had lot's of e-mails saying "hey I switched from FM 1.0.1 to 1.0.2 and > broke everything, I try to get back but the same problem happen, I changed > nothing".... > People broke their own local repositories and blame on me, forget, I won't > release my code, it is mine, be happy that flexmojos is free and accept that > the sdk tool is not. > > Plus : the source code for FM itself is available, I can hack it and >> break the buildchain : does this leads to enormous mail traffic on your >> mailbox ? >> > > No one, or very, very, little number of people go anywhere near flexmojos > code. And usually who goes know what they are doing or are acting on a > problem. > Everybody was trying to use the sdk tool w/o even know what the tool was > doing, then they screwed their local repos and spam me. > > If half of the energy the community spend on this topic was spend on this > SDK version it would be already hosted somewhere. > > Guys give up, once more, this tool is mime, I wrote it, I have the right to > not make it public. I won't reply on this matter anymore! > > Ok, so to conclude > > No, you won't share your tool source / descriptors ; > No, you won't release SDK 4.5.0.19786 ; > No, you won't share some of your knowledge on that tedious task to help > somebody out there doing it. > > So, I have to do it myself, and understand the mavenization process for the > scratch without any help. > > Am I right ? > -- 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/
