Well, I guess I would need to run [1] for all files or sign them first and deploy all of them [2] in a big jar, not though what is the exact way but sure I couldn't be run for nightly builds even though for snapshots only, it takes too long.
[1] mvn gpg:sign-and-deploy-file -DpomFile= myLib.pom -Dfile=myLib.swc -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging [2] jar -cvf bundle.jar myLib.pom myLib.pom.asc myLib.swc myLib.swc.asc myLib-sources.jar myLib-sources.jar.asc -Fred -----Message d'origine----- De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Envoyé : mardi 29 octobre 2013 22:01 À : dev@flex.apache.org Objet : AW: License Stuff Hi Frederic, well whenever I do a Flexmojos Release, I have to deploy quite a lot of files. That was never really a problem. I guess it should be possible to stage all the fdk files using the deployer after all it's nothing than an ordinary maven deploy. All that's different to an ordinary deply is that you have to deploy to a staging repo which you can test and as soon as all is good, you hit the "Go" button and the stuff is publically available at the Sonatype OSS repo and after some time artifacts are synced to Mavan Central. Chris -----Ursprüngliche Nachricht----- Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Gesendet: Dienstag, 29. Oktober 2013 21:31 An: dev@flex.apache.org Betreff: RE: License Stuff Chris, I just had a look at the deployment process requires by Sonatype, something I did 2 years ago, so, I didn't remembered well, it was heavy and it was only one Flex Lib built by Maven. How do you think we can deploy our not Maven built SDK artifacts in the Sonatype way ? can it accept a compress file as a bundle of all signed artifacts or something else ? -Fred -----Message d'origine----- De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Envoyé : mardi 29 octobre 2013 21:14 À : dev@flex.apache.org Objet : AW: License Stuff But if the deal Velo and Sonatype had with Adobe was enough, I guess this would be all we need and we wouldn't have the hassle of having to implement any sort of manual deployment wrapper as I would really hate having to implement any sort if "interactive" maven build. Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Dienstag, 29. Oktober 2013 21:08 An: dev@flex.apache.org Betreff: Re: License Stuff We did not pursue that approach because Apache supposedly only distributes source code with open licenses. Even if there was such an agreement, the binary packages still could not contain Adobe stuff because a binary package can only contain the compiled results of a source package. I may still set up a simple "business" to distribute the same package as Adobe 4.6 but a license acceptance will still be required which AFAIK still poses a problem for Maven. Maybe we should add some license handling to Maven itself? -Alex On 10/29/13 12:53 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: >Not sure if it has been already asked but can't Apache / Apache Flex >sign a Distribution agreement ? > >-----Message d'origine----- >De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 29 octobre >2013 17:57 À : dev@flex.apache.org Objet : Re: License Stuff > > > >On 10/29/13 7:16 AM, "christofer.d...@c-ware.de" ><christofer.d...@c-ware.de> wrote: > >>Hi Guys, >> >>I am currently talking to Brian Fox from Sonatype. He told me that >>Sonatype signed a Distribution Agreement with Adobe had been signed in >>2008, but this has expired 2009, but it seems they are willing to >>re-sign such an Agreement. >> >>For which parts would we Need an Agreement from Adobe? As far as I >>know this would be the Flach Playerglobal and for Air the Airglobal >>and related SWCs/RSLs is there anything else? Can a Distribution >>Agreement be signed for all of the missing parts? >I believe you need the entire AIR SDK. Well, maybe not the runtimes, >but the packagers if you are going to support mobile output. > >> >>If we manage to sort this out, I guess There should be nothing else >>preventing us from Publishing Flex SDKs without having to implement >>any hacks. I guess this would help a lot of Flex users quite a lot. >In my last conversation with Adobe Legal, they still want folks to >accept the license agreement once per company. The distribution >agreement only gives you the right to distribute, but folks still need >to be aware that not every file is Apache-licensed. > >-Alex >
