On Sun, Nov 5, 2017 at 5:31 PM, Daniel Dekany <[email protected]> wrote: > Sunday, November 5, 2017, 10:39:06 PM, Woonsan Ko wrote: > >> On Fri, Nov 3, 2017 at 8:20 PM, Daniel Dekany <[email protected]> wrote: >>> Thank you Woonsan! >> >> Thanks again for your guidance and helps! >> >>> >>> Anything to improve on the release process itself, and on its >>> documentation? (I did some updates in the how-to, on the places where >>> you had questions, so apart from those.) >> >> I've fixed a typo in the KEYS url: >> - >> https://git1-us-west.apache.org/repos/asf?p=incubator-freemarker-site.git;a=commitdiff;h=a5f926f6;hp=f37ae1ab30c83b024ab256588b616c5529979630 > > Thanks! > >> Didn't update the site yet. >> >> In my case, adding the following [1] was helpful. Otherwise, it was in >> stuck in the signing process: >> >> GPG_TTY=$(tty) >> export GPG_TTY > > It would much be better to automate this in the build.xml, rather than > documenting it. (Is it normal that the installation of GPG doesn't add > this environment variable, or just a local glitch?)
Searching on the internet, it doesn't look like a local glitch, but possibly on every Mac and/or *nix env. A similar example (in git commit signing case): - https://mitchellcash.com/2017/01/31/you-need-a-passphrase-fixing-an-issue-when-signing-git-commits-on-a-mac.html Anyway, the problem seemed to occur only when invoking 'packageAndSignDist' macro (in build.xml), but it seemed okay in signing jar artifact using maven-gpg-plugin (also in build.xml). maven-gpg-plugin seems to pass the passphrase defined in the 'gpg' profile with --batch and --passphrase-fd args: - http://svn.apache.org/viewvc/maven/plugins/tags/maven-gpg-plugin-1.6/src/main/java/org/apache/maven/plugin/gpg/AbstractGpgMojo.java?view=markup#l58 - http://svn.apache.org/viewvc/maven/plugins/tags/maven-gpg-plugin-1.6/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java?view=markup#l93 But, the gpg command in the ant macro doesn't have that (<exec executable="${gpgCommand}" failonerror="true">...</exec>), so I guess the builder is supposed to type the passphrase interactively, which might work fine on W32 env for instance, I assume. Someone tried to mimic how the maven-gpg-plugin does below, but it has some limitations: - https://stackoverflow.com/questions/5199571/pgp-decrypt-using-ant Therefore, I'm inclined to add a tip in the documentation, instead of trying to solve this in ant build.xml. ;-) Also, the committer-howto page doesn't seem to describe the dependency on 'gpg' maven profile in builder's settings.xml. > >> Perhaps shall we add this info as a tip for non-W32 devs in the steps? >> >> Another thing is, where to update the manual docs in the releasing >> process. 2.3 or 2.3-gae? I updated 2.3 branch, but now I assume I >> should have updated 2.3-gae and merge it into 2.3 where I generate the >> manual docs. If this is right, shall I try to commit some changes for >> clarification? > > It doesn't mater now. But changes should be always done in 2.3-gae > first, and then merged into 2.3. This is stated in the release how-to > as well (maybe I have added that after you were after that part). Also > on http://freemarker.apache.org/sourcecode.html, so I guess we are > covered. I see. Thanks! Regards, Woonsan > >> Thanks, >> >> Woonsan >> >> [1] >> https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPG_002dAGENT.html >> >> >> >>> >>> >>> Friday, November 3, 2017, 2:34:34 PM, Woonsan Ko wrote: >>> >>>> The Apache FreeMarker (incubating) community is pleased to announce >>>> the release of Apache FreeMarker 2.3.27 (incubating). >>>> >>>> Change log: >>>> http://freemarker.org/docs/versions_2_3_27.html >>>> >>>> You can get binary and source packages from here: >>>> http://freemarker.org/freemarkerdownload.html >>>> >>>> Or with Maven: >>>> >>>> <dependency> >>>> <groupId>org.freemarker</groupId> >>>> <artifactId>freemarker</artifactId> >>>> <version>2.3.27-incubating</version> >>>> </dependency> >>>> >>>> Disclaimer: Apache FreeMarker is an effort undergoing incubation at >>>> The Apache Software Foundation (ASF), sponsored by the Apache >>>> Incubator <https://incubator.apache.org/>. Incubation is required of >>>> all newly accepted projects until a further review indicates that the >>>> infrastructure, communications, and decision making process have >>>> stabilized in a manner consistent with other successful ASF projects. >>>> While incubation status is not necessarily a reflection of the >>>> completeness or stability of the code, it does indicate that the >>>> project has yet to be fully endorsed by the ASF. >>>> >>>> >>>> Woonsan Ko >>>> on behalf of Apache FreeMarker Podling Project Management Committee >>>> >>> >>> -- >>> Thanks, >>> Daniel Dekany >>> >> > > -- > Thanks, > Daniel Dekany >
