Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Remove dependency on httpcomponents.core5

Cerrado
  • ¿Algo no está bien?
#2,266 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@rzo1 ya está trabajando en esto.

Desde el 25/10/2026.

  • #2270 de @rzo1 — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
java
Área
backend, build-system, documentation

Línea de trabajo

Start with the affected imports listed in the issue, especially BasicURLNormalizer, then inspect core/pom.xml, the root pom.xml, the archetype shade configuration, and the “Migrating to 4.0.0” docs. The issue specifies the constants and query-string behavior to preserve; review the listed main and test files across core, tika, and warc. Done means removing the dependency and exclusion, preserving query output, and documenting the migration; linked pull request #2270 is already open.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

BREAKING CHANGE core

See discussion on https://github.com/apache/stormcrawler/pull/2236/#issuecomment-6250049212

Context

After #2211, core depends only on org.apache.httpcomponents.core5:httpcore5. It uses it for HTTP header and status constants and for query-string parsing in BasicURLNormalizer. A whole library for that is not worth the dependency, and HttpComponents types in our code mean we can't change these classes in a 4.x minor release without breaking user code. 4.0.0 is the time to remove it.

What's affected

1. HttpHeaders constants

  • Main code: FeedParserBolt, JSoupParserBolt, SimpleFetcherBolt, SiteMapParserBolt, FetchOutcomes, AdaptiveScheduler, HttpRobotRulesParser, FileResponse, okhttp HttpProtocol, CharsetIdentification, plus ParserBolt (tika) and WARCRecordFormat (warc).
  • Tests: FeedParserBoltTest, JSoupParserBoltTest, SiteMapParserBoltTest, AdaptiveSchedulerTest, CharsetIdentificationTest, plus the tika and warc tests.
  • Constants used: ACCEPT, ACCEPT_LANGUAGE, AUTHORIZATION, CONTENT_LENGTH, CONTENT_TYPE, ETAG, IF_MODIFIED_SINCE, IF_NONE_MATCH, LAST_MODIFIED, LOCATION, PROXY_AUTHORIZATION, USER_AGENT.

2. HttpStatus constants

  • Used in FileResponse.
  • Constants used: SC_OK, SC_MULTIPLE_CHOICES, SC_BAD_REQUEST, SC_UNAUTHORIZED, SC_FORBIDDEN, SC_NOT_FOUND, SC_METHOD_FAILURE, SC_INTERNAL_SERVER_ERROR.

3. NameValuePair and URLEncodedUtils in BasicURLNormalizer

  • These sort the query parameters and remove the filtered ones.
  • The code calls URLEncodedUtils.parse(query, UTF_8, '&', ';') and URLEncodedUtils.format(pairs, UTF_8). That class is deprecated in httpcore5.
Actions
  1. Add StormCrawler-owned HttpHeaders and HttpStatus classes in core, for example under org.apache.stormcrawler.protocol. Each holds the constants listed above as plain public static final fields, with the same names and values as HttpCore 5. Switching to them is then an import change only.
  2. Update all the imports above in core, tika and warc, main and test code.
  3. Replace URLEncodedUtils and NameValuePair in BasicURLNormalizer with a small in-house parser and formatter. The output must stay exactly the same.
  4. Remove httpcore5 from core/pom.xml, and the httpcore5.version property from the root pom.xml if nothing else uses it.
  5. Remove the leftover <exclude>org/apache/http/**</exclude> from the archetype's shade configuration.
  6. Update the "Migrating to 4.0.0" docs. Core no longer brings in any HttpComponents classes, so users who relied on them transitively must declare the dependency themselves.
Lenguaje dominante
Java
Estrellas
1k
Forks
295
Merge medio
1 d 15 h
PR fusionados (30 d)
71

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/stormcrawler

Todos los issues de apache/stormcrawler

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.