akka/akka-http

Split packages in akka.http.core and akka.http

Open

#2,903 opened on 2020年1月21日

GitHub で見る
 (1 comment) (0 reactions) (0 assignees)Scala (1,311 stars) (598 forks)batch import
1 - triagedbinary-incompatiblehelp wantednice-to-have (low-prio)

説明

Akka HTTP Version 10.1.11:

The following packages currently occur in akka.http.core and akka.http with disjunct classes:

  • akka.http.impl.settings
  • akka.http.javadsl.settings
  • akka.http.scaladsl.settings

We have various options here:

  • Move all classes to the same package into the same artifact
  • Rename one of the packages to avoid the split-package issue, preferably choosing a package name which shares the artifact name as it's prefix
  • With a very good reason (is that even possible?) I think we can keep the split package, but it is the most painful and dirty solution

Related to https://github.com/woq-blended/akka-osgi/issues/2. Comments of https://github.com/akka/akka-http/issues/2902 apply.

コントリビューターガイド

技術スタック
scala
領域
backend
Issue 種別
refactor
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
ScalaAkka HTTPOSGisbt
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
25
調査方針
The issue proposes three options to resolve split packages between akka.http.core and akka.http artifacts. The preferred approach is to move classes to the same package into the same artifact or rename one package to avoid split packages. Examine the existing package layout in the source code (e.g., akka http core/src/main/scala/akka/http/impl/settings) and determine which option is least disruptive. Also review comments in referenced issue #2902 and the OSGi issue linked for further context.
Split packages in akka.http.core and akka.http · akka/akka-http#2903 | Good First Issue