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

Move remote ant support to dedicated bundle

Cerrado
#3,018 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@iloveeclipse ya está trabajando en esto.

Desde el 12/10/2026.

  • #170 de @iloveeclipse — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
java
Área
build-system

Línea de trabajo

The issue names org.eclipse.ant.ui, org.eclipse.ant.launching, and the remoteAnt.jar, lib/antdebug.jar, and lib/remote.jar libraries. Read the linked proposal and open draft PR first, then inspect how these libraries are built and used. Done means the remote Ant support is in a dedicated org.eclipse.ant.remote project with Java 17 settings and the Maven build produces the libraries.

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

Descripción

enhancement

Follow up on https://github.com/eclipse-platform/eclipse.platform/issues/3010 and proposal to fix the problem with remoteAnt.jar checked into org.eclipse.ant.ui and compiled against Java 17. Currently we can't even build this jar anymore (easily) locally without breaking ant support on Java 17!

However, in org.eclipse.ant.launching there is yet another (!!!) set of similar ant related jars we checked into git which are also affected by same problem: lib/antdebug.jar and lib/remote.jar, which are also needed for running ant outside Eclipse JVM.

Therefore I propose to move all the "remote ant" support libraries into one dedicated org.eclipse.ant.remote project with proper JLS 17 setting. This would fix most of the current problems we see with two org.eclipse.ant.launching & org.eclipse.ant.ui bundles, we would build everything during maven build.

With the AI help I was able to quickly evaluate the proposal, and it seem it is doable.

Draft PR follows, so far it looks as it should work.

Lenguaje dominante
Java
Estrellas
165
Forks
174
Merge medio
2 d 16 h
PR fusionados (30 d)
42

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 eclipse-platform/eclipse.platform

Todos los issues de eclipse-platform/eclipse.platform

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.