Why is there already a target to compare the date to and what's in there? We should definitely fix the dates in the tar as well.
On Wed, Oct 22, 2025 at 7:37 PM PJ Fanning <[email protected]> wrote: > > So I think I know the cause. > > sbt-source-dist was changed to make the builds more reproducible and > basically, the tarball has all the file dates as if they were created > in 1970. > > This confuses sbt-boilerplate. > > [debug] Found 7 template files in > /Users/pj.fanning/code/tmp/apache-pekko-http-1.3.0-src-20251021/http/src/main/boilerplate. > [debug] Default repositories: > [debug] Using inline dependencies specified in Scala. > [debug] Template 'FormFieldDirectivesInstances.scala.template' older > than target. Ignoring. > [debug] not up to date. inChanged = true, force = false > [debug] Template 'ParameterDirectivesInstances.scala.template' older > than target. Ignoring. > [debug] Template 'ApplyConverterInstances.scala.template' older than > target. Ignoring. > [debug] Template 'ConstructFromTupleInstances.scala.template' older > than target. Ignoring. > [debug] Updating parsing... > [debug] Template 'TupleFoldInstances.scala.template' older than > target. Ignoring. > [debug] Template 'TupleAppendOneInstances.scala.template' older than > target. Ignoring. > [debug] Template 'JavaPathMatchers.scala.template' older than target. > Ignoring. > > This command can be used to update the timestamps on all the .template > files and this will help in persuading sbt-boilerplate to work again. > > find . -name "*.template" -exec touch {} \; > > Is this an ok workaround for the time being? Going forward, we need to > work out if we > * look to get a change into sbt-boilerplate > * or change the way we produce the source tarballs so that the file > dates don't confuse sbt-boilerplate > > On Wed, 22 Oct 2025 at 18:08, PJ Fanning <[email protected]> wrote: > > > > So this issue doesn't happen with the 1.2.0 source release. > > > > The code is generated with sbt-boilerplate. > > https://github.com/sbt/sbt-boilerplate > > > > I'm still at a loss for why this is no longer kicking in and > > especially why only the source release RC is affected while builds run > > from git checkouts still work fine. > > > > On Wed, 22 Oct 2025 at 17:53, PJ Fanning <[email protected]> wrote: > > > > > > I see an issue with compiling the http module but I suspect that it is > > > not new. I doubt whether too many people build from the tgz files. > > > > > > This step only appears to happen when you build from a git checkout. > > > > > > [info] Generating 'FormFieldDirectivesInstances.scala' > > > [info] Generating 'ParameterDirectivesInstances.scala' > > > [info] Generating 'ApplyConverterInstances.scala' > > > [info] Generating 'ConstructFromTupleInstances.scala' > > > [info] Generating 'TupleFoldInstances.scala' > > > [info] Generating 'TupleAppendOneInstances.scala' > > > [info] Generating 'JavaPathMatchers.scala' > > > > > > When this code generation does not happen, the http module fails to > > > compile because it needs these scala files and the classes that are > > > built from them. > > > > > > I guess the next step is to look into why this code gen relies on git. > > > > > > On Wed, 22 Oct 2025 at 15:49, kerr <[email protected]> wrote: > > > > > > > > 何品 > > > > I compiling it , but it fails > > > > > > > > [info] > > > > /Users/hepin/Downloads/apache-pekko-http-1.3.0-src-20251021/http-core/src/test/java/org/apache/pekko/http/javadsl/settings/ParserSettingsTest.java: > > > > ParserSettingsTest.java uses or overrides a deprecated API. > > > > > > > > [info] > > > > /Users/hepin/Downloads/apache-pekko-http-1.3.0-src-20251021/http-core/src/test/java/org/apache/pekko/http/javadsl/settings/ParserSettingsTest.java: > > > > Recompile with -Xlint:deprecation for details. > > > > > > > > [error] (http / Compile / compileIncremental) Compilation failed > > > > > > > > [error] Total time: 60 s, completed Oct 22, 2025 10:48:26 PM > > > > > > > > PJ Fanning <[email protected]> 于2025年10月22日周三 05:35写道： > > > > > > > > > Hello Pekko Community, > > > > > > > > > > This is a call for a vote to release Apache Pekko HTTP version > > > > > 1.3.0-RC1. > > > > > > > > > > The discussion thread: > > > > > > > > > > https://lists.apache.org/thread/wpvcd29x7s2wyly2lz2j03083cdpm1yn > > > > > > > > > > The release candidate: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/pekko/HTTP-1.3.0-RC1/ > > > > > > > > > > This release has been signed with a PGP key available here: > > > > > > > > > > https://downloads.apache.org/pekko/KEYS > > > > > > > > > > Release Notes: > > > > > > > > > > > > > > > https://github.com/apache/pekko-http/pull/852/files#diff-b77608f9884c5f0b45c2d1fd1ef389c7abb249fcc4cc785d31268edcefebe118 > > > > > > > > > > Git branch for the release: > > > > > > > > > > https://github.com/apache/pekko-http/tree/v1.3.0-RC1 > > > > > Git commit ID: 6b8a38973e79d511289390c230e15a0afc451eed > > > > > > > > > > Please download, verify, and test. > > > > > > > > > > We have also staged jars in the Apache Nexus Repository. These were > > > > > built > > > > > with the same code > > > > > as appears in this Source Release Candidate. We would appreciate if > > > > > users > > > > > could test with these too. > > > > > If anyone finds any serious problems with these jars, please also > > > > > notify us > > > > > on this thread. > > > > > > > > > > https://repository.apache.org/content/groups/staging/org/apache/pekko/ > > > > > > > > > > For sbt 1.9.4 or greater you can add this resolver > > > > > > > > > > resolvers += Resolver.ApacheMavenStagingRepo > > > > > > > > > > Otherwise for older versions of sbt > > > > > > > > > > resolvers += "Apache Pekko Staging" at " > > > > > https://repository.apache.org/content/groups/staging"; > > > > > > > > > > > > > > > The VOTE will pass if we have more positive votes than negative votes > > > > > and there must be a minimum of 3 approvals from Pekko PMC members. > > > > > Anyone voting in favour of the release, could you please provide a > > > > > list of > > > > > the checks you have done? > > > > > The vote will be left open until <insert date/time here>. > > > > > > > > > > [ ] +1 approve > > > > > [ ] +0 no opinion > > > > > [ ] -1 disapprove with the reason > > > > > > > > > > To learn more about Apache Pekko, please see https://pekko.apache.org/ > > > > > > > > > > Checklist for reference: > > > > > > > > > > [ ] Download links are valid. > > > > > [ ] Checksums and signatures. > > > > > [ ] LICENSE/NOTICE files exist > > > > > [ ] No unexpected binary files > > > > > [ ] Source files have ASF headers > > > > > [ ] Can compile from source > > > > > [ ] Can verify the binary build > > > > > > > > > > To compile from the source, please refer to: > > > > > > > > > > > > > > > https://github.com/apache/pekko-http/blob/main/README.md#building-from-source > > > > > > > > > > To verify the binary build, please refer to: > > > > > > > > > > > > > > > https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build > > > > > > > > > > Some notes about verifying downloads can be found at: > > > > > > > > > > https://pekko.apache.org/download.html#verifying-downloads > > > > > > > > > > > > > > > Here is my +1 (binding). > > > > > > > > > > Thanks, > > > > > PJ Fanning (Apache Pekko PMC member) > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
