Skip to content

Rename com.sun.enterprise.backup.util to org.glassfish.main#26102

Open
renatsaf wants to merge 1 commit into
eclipse-ee4j:mainfrom
renatsaf:analyze-issue-23627-refactor-com-sun-packages
Open

Rename com.sun.enterprise.backup.util to org.glassfish.main#26102
renatsaf wants to merge 1 commit into
eclipse-ee4j:mainfrom
renatsaf:analyze-issue-23627-refactor-com-sun-packages

Conversation

@renatsaf

Copy link
Copy Markdown
Contributor

First incremental step toward refactoring GlassFish-owned com.sun.* packages to org.glassfish.main, as discussed in #23627.

What

Renames com.sun.enterprise.backup.util.BackupUtils to org.glassfish.main.enterprise.backup.util.BackupUtils and updates the two in-module references (BackupManager, RestoreManager).

Why this class first

Per @dmatej's request in the issue, the migration should be iterative and keep every test green at each step. BackupUtils is the lowest-risk possible starting point:

  • Single class, contained entirely within the appserver/admin/backup module.
  • Referenced from only two other Java files, both in the same module.
  • No string/FQCN references in domain.xml, *.conf, *.policy, *.properties, META-INF/services, or Class.forName — so no reflection/config exposure.
  • No external-project (EclipseLink/TCK) contract on it.

The intent is to validate the per-package workflow (rename → fix imports → sweep config/string references → compile) on a trivial case before tackling larger, reflection-heavy packages.

Verification

  • mvn -pl appserver/admin/backup -am compile succeeds.
  • Repo-wide search confirms no remaining references to the old package name.

Refs #23627

First incremental step toward refactoring GlassFish-owned com.sun.*
packages to org.glassfish.main (refs eclipse-ee4j#23627).

BackupUtils has no XML/config/reflection exposure and is referenced
only within the appserver/admin/backup module, making it a low-risk
starter for the iterative package migration.

Refs eclipse-ee4j#23627

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant