I’ve run Maven successfully. I’m now examining the source-release.zip.
Is there any harm in posting builds to the staging repo? If not, I guess you can do it without waiting. Is there an easy way to have the build.a.o CI server run builds that create md5 checksum files instead of ASC files? Then more folks are likely to look at it. -Alex On 11/12/14, 2:16 PM, "Christofer Dutz" <[email protected]> wrote: >During the actual release this all happens automatically. > >As I said ... you should be able to see the results by simply running the >maven build locally. As soon as I intend on creating an RC all would be >staged in the staging repository and you could have a look there. Do you >want me to prepare one? > >Chris > >________________________________________ >Von: Alex Harui <[email protected]> >Gesendet: Mittwoch, 12. November 2014 23:11 >An: [email protected] >Betreff: Re: AW: [DISCUSS] Release Flex-Tool-API? > >On 11/12/14, 2:05 PM, "Christofer Dutz" <[email protected]> wrote: > >>I just remember what the problem was that as part of a release each file >>of a release is signed and as soon as I turn on the apache-release >>profile it expects credentials for this signing process. > >So is there a way to set an alternative “goal” (is that the right word >that is equivalent to an Ant target?) that will be more like “build” >instead of “install” and doesn’t try the signing. Also, it would be great >to have MD5 files generated for each download. Is that hard to do? > >-Alex >
