Hi,
Below are three proposals for package renaming, in order of disruption
(first least disruptive, last most disruptive):
- Proposal 1: ensure that each module has unique package names. Thus
packages can be sealed.
Targeted renaming.
- Proposal 2: rename jersey-core and jersey-server.
- Proposal 3: rename jersey-core, jersey-server, jersey-client,
spring, jersey-json.
All of the proposals would rename the impl packages to be consistent
(but these should not be depended upon).
I am leaning towards proposal 1 as i really want to minimize breakage.
But how about a vote? What do you want?
Paul.
Proposal 1:
----------------
jersey-server:
com.sun.jersey.api -> com.sun.jersey.response
jersey-multipart:
com.sun.jersey.api.* -> com.sun.jersey.multipart.*
Proposal 2:
----------------
jersey-core:
com.sun.jersey.api.* -> com.sun.jersey.core.*
com.sun.jersey.spi.* -> com.sun.jersey.core.spi.*
jersey-server:
com.sun.jersey.api.* -> com.sun.jersey.server.*
com.sun.jersey.spi.* -> com.sun.jersey.server.spi.*
Retain but mark as deprecated:
com.sun.jersey.spi.container.servlet.ServletContainer
(extends
com.sun.jersey.server.spi.container.servlet.ServletContainer)
jersey-multipart:
com.sun.jersey.api.* -> com.sun.jersey.multipart.*
Proposal 3:
----------------
As proposal three but include
jersey-client:
com.sun.jersey.api.* -> com.sun.jersey.client.*
spring
com.sun.jersey.api.* -> com.sun.jersey.spring.*
com.sun.jersey.spi.* -> com.sun.jersey.spring.spi.*
jersey-json
com.sun.jersey.api.* -> com.sun.jersey.json.*