Port UUID with Java UUID libraries
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 38/100
Direção de pesquisa
Read src/main/java/org/perlonjava/runtime/perlmodule/DataUUID.java as the local reference, then compare the UUID 0.39 API and upstream contract described in the issue. Implement the Java-backed API and add project-owned tests for generation, conversions, queries, imports, and stateful options. Done means the upstream suite and UUID-dependent IPC-Manager cases pass on both JVM and interpreter backends without native compilation.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Goal
Port CPAN UUID to PerlOnJava using Java UUID APIs and Java-side support code, so distributions that depend on UUID do not require the native XS implementation. Avoid requiring native code or an external process.
The project already targets Java 24 and has a Java-backed Data::UUID implementation at src/main/java/org/perlonjava/runtime/perlmodule/DataUUID.java that uses java.util.UUID; use it as a local implementation reference where the semantics overlap.
Compatibility scope
Implement the Perl-visible API from UUID 0.39, including the exported functions and import options documented upstream. This includes binary and textual conversion, parsing, formatting, comparison, null/type/version/variant/time queries, and UUID generation (versions 1, 3, 4, 5, 6, and 7, plus the documented aliases). Preserve Perl's 16-byte UUID representation and upstream behavior for namespace names, invalid inputs, and byte ordering. Handle the stateful :mac, :persist, and :defer options according to the upstream contract, or document any intentional compatibility limit with evidence.
Use java.util.UUID and standard Java time, digest, and randomness APIs where they match the required behavior; implement remaining UUID layouts and state in Java. Java's built-in UUID directly covers common parsing/string conversion, v3 name-based generation, v4 random generation, and UUID field access, but the port must also cover the additional upstream versions and stateful behavior.
Evidence
- CPAN distribution:
UUID0.39; discovered as a prerequisite ofIPC-Manager0.000037 in PerlOnJava CPAN tester run20261006-085241-91243. - System Perl 5.42.2: upstream suite passed, 174 files and 1,649 tests.
- PerlOnJava: the tester could not compile UUID's XS/C sources;
makefailed while generating a native header. This prevented the dependency from being installed, and the downstream IPC-Manager run later timed out with UUID load failures. The timeout is not evidence of a separate PerlOnJava hang. - The default
jperlpath was exercised by the tester; interpreter behavior was not independently verified. - Reverse dependency evidence: 14 unique runtime dependants, 8 recent. Examples include
IPC-Manager,DBIx-QuickORM,Net-NATS-Streaming-Client, andTravel-Status-DE-DBRIS.
Acceptance criteria
- Provide a PerlOnJava implementation of the supported UUID 0.39 API without XS/native compilation.
- Add project-owned tests for generation versions, deterministic namespace UUIDs, parse/unparse and binary round trips, comparison and field queries, imports/aliases, and relevant stateful options.
- Validate new tests with system Perl, then pass them on both the JVM and interpreter backends.
- Run the UUID 0.39 upstream test suite through PerlOnJava with the expected native-free implementation selected.
- Run the dependent IPC-Manager tests far enough to confirm UUID loads and its UUID-dependent cases pass; report any unrelated environmental skips separately.
- Linguagem predominante
- Perl
- Estrelas
- 64
- Forks
- 7
- Merge médio
- 4h 56min
- PRs com merge (30d)
- 181
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de fglock/PerlOnJava
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
fglock/PerlOnJava#1651 ·
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
fglock/PerlOnJava#1579 ·
Mantenedores costumam responder em até 1 dia
-
area:cpan-port area:unicode bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
fglock/PerlOnJava#1341 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 4/5 1-2 dias Facilidade para iniciantes 54/100
fglock/PerlOnJava#1671 ·
Mantenedores costumam responder em até 1 dia
-
area:backend bug
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 57/100
fglock/PerlOnJava#1669 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de fglock/PerlOnJava
Issues semelhantes
-
FOODTURE
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
openfoodfacts/openfoodfacts-server#14853 ·
Mantenedores costumam responder em até 1 dia
-
Needs Triage
Dificuldade 2/5 Meio dia Facilidade para iniciantes 66/100
Perl/perl5#24913 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 85/100
gugod/App-perlbrew#879 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
RotherOSS/otobo#6205 · 1 comentário ·
Mantenedores costumam responder em até 1 dia