pjfanning opened a new pull request, #3670:
URL: https://github.com/apache/pekko/pull/3670

   ### Motivation
   #3645, #3646, #3648, #3649 and #3651 ported changes from Akka 2.9.0 sources 
whose notices read `Copyright (C) <start>-2023 Lightbend Inc.`, but the 
modified Pekko files only carry the earlier `<start>-2022` notice. In the 
review of #3647, @He-Pin asked for the source notice of adapted code to be 
retained.
   
   ### Modification
   Add the Akka 2.9.0 source notice alongside the existing Lightbend notice in 
57 files:
   - each file those PRs modified where Akka 2.9.0 carries a 2023 notice;
   - the `serialization-jackson3` copies of the affected 
`serialization-jackson` files.
   
   Existing notices are unchanged, and no code changes.
   
   | PR | Files |
   |---|---|
   | #3651 | `Serialization.scala`, `ProtobufSerializerSpec.scala` |
   | #3649 | Jackson serializer spec, serialization doc spec and doc example 
files, in `serialization-jackson` and `serialization-jackson3` |
   | #3648 | sharding/singleton settings, `Shard.scala`, 
`ClusterSingletonManager.scala`, typed `ClusterSingleton.scala`, 
`LeaseUsageSettings.scala` and the lease specs |
   | #3646 | typed `EventEnvelope.scala` |
   | #3645 | `ClusterShardingSpec.scala` |
   
   Files these PRs added already carry the right notices (#3650's 
`SerializedEvent.scala` has the 2023 notice, and #3641's files are original 
Pekko code).
   
   ### Result
   The source notices of the ported Akka 2.9.0 code are preserved.
   
   ### Tests
   - `sbt headerCheckAll`
   - `git diff --check`
   
   ### References
   #3645, #3646, #3647, #3648, #3649, #3651
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to