Just need to signup do get editing access... https://docs.sonatype.org/signup.action
VELO On Wed, Oct 28, 2009 at 1:30 PM, Grant Smith <[email protected]> wrote: > Thanks Logan, > > In the meantime, I think someone should at least put a note on the existing > Wiki page explaining some of this. I'd do it myself, but it looks like I > need to be authorized (given a Confluence login?) to do so. > > I actually have some feedback to give on my setup for creating a > certificate and signing/building an air app in one step which I combined > from information in the Wikis and elsewhere - but couldn't find a way to > register for the Wiki. Velo, if you assist me to post on the Wiki, I will > gladly add some value to the project :) > > -Grant. > > > On Wed, Oct 28, 2009 at 6:31 AM, Logan Allred <[email protected]> wrote: > >> >> On Tue, Oct 27, 2009 at 3:07 PM, Grant Smith <[email protected]> >> wrote: >> > We were also hoping that flex-mojos would be more open, in the spirit of >> open >> > source, but I guess the descriptor xml file falls outside of this scope, >> > perhaps. >> > >> > You really should remove the Wiki page of the descriptor file is >> > proprietary, no ? >> >> The specific files Velo uses to update the Sonatype repos are >> proprietary. Everything else is open. >> >> Installing your own FDK is an advanced topic, and Velo was bit >> severely in the past when those who didn't understand what it was >> doing did it wrong and caused all sorts of support problems. It's very >> hard to troubleshoot Maven and Flexmojos if the FDK is messed up, and >> Velo wasted lots of time in the past trying to help people figure out >> what went wrong. That is why he doesn't want the process to be >> well-known. Not due to proprietary concerns, but support and sanity >> concerns. >> >> I have installed several FDKs myself (using the old way, not the new >> bundle publisher). If you are careful, understand what it is doing, >> and pretty good at Maven debugging on your own, you should be able to >> do it on your own just fine. We will need to install another custom >> FDK in a few months, and I'll learn bundle publisher then and do it >> myself. But you have to have a really really solid understanding of >> how Maven and Flexmojos use the Flex SDK, and how it's structured. The >> bundle-publisher is open source, but poorly documented, but you can >> dig through the source and figure out how to make it work. >> >> If I can figure out a "safe" way to share that, and get Velo to agree, >> then I'll share it on the Wiki. >> >> If you really need custom FDKs and don't have the time or money to do >> it yourself or pay someone to set them up, then the other option is to >> switch to Servebox, which supports a locally installed Flex SDK model, >> or convince Velo to add a similar option to Flexmojos (not likely). Or >> you can try and get Adobe to release the FDK themselves in a Maven >> repo, so we don't have to do it for them. >> >> Logan >> >> >> > > > -- > Grant Smith > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
