I'd say manually mavenizing a previously downloaded Flex sdk is a task nobody will be willing to do. Even if such a Mavenized FDK was downloadable ... manually deploying that to a mmaven repository would be insane. I created the Generator in order to automatically do this transformation from a downloaded FDK to a mavenized one. Using the deployer the deployment can be automated too.
Assuming that we would use the FDK Generator, I'd say there are 3 Types of developers: 1. The "consumers": That expect everything to be setup so they can start using something without any effort ... just add a dependency and off you go. These would feel insulted by such a solution 2. The Powerusers: They know how to read a website and manage to download the FDKs, the generator and use that to deploy to their own repo. These would be anoyed by the need to have to do this, but would probably settle with it and be happy. 3. People like me :-) People that would be glad to finally get their hans on a mavenized FDK of their favourite Flex release and be happy to get their fingers dirty a little in order to use it. Chris [ C h r i s t o f e r D u t z ] C-Ware IT-Service Inhaber Dipl. Inf. Christofer Dutz Karlstraße. 104, 64285 Darmstadt IT- und Systemhäuser fon: 0 61 51 / 27315 - 61 fax: 0 61 51 / 27315 - 64 mobil: 0171 / 7 444 2 33 email: christofer.d...@c-ware.de http://www.c-ware.de UStId-Nr. DE195700962 -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Dienstag, 16. Oktober 2012 19:42 An: flex-dev@incubator.apache.org Betreff: Re: AW: AW: Flex Maven FDK Generator RC1 On 10/16/12 9:58 AM, "Greg Reddin" <gred...@gmail.com> wrote: > > With most projects I've been involved in I've had to manually download > non-permissive stuff and host it in a company repo like Artifactory. I > think it's a bit of an unfortunate fact of our existence that Flex, > for a while at least, will be dependent on non-open source libraries > like the Flash runtime. It may mean that somebody can't just declare a > dependency to our code in their POM file and be off and running. We > may have to document that users will need to manually download and > install the Adobe stuff before the Flex code will be of any use to > them. At least that's the worst case scenario. > > Greg Thanks Greg. Do you happen to know if those non-permissive licenses allow for re-distribution within a company? Are those packages you manually download full-fledged Maven artifacts or does someone else Maven-ize them? To others: Is manual download of the Adobe stuff sufficient? Or is this going to be an important barrier for Apache Flex that we need to solve? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
