-
Bug
-
Resolution: Fixed
-
P2
-
1.4.0
-
None
-
beta
-
generic
-
generic
We need to determine whether src.jar should remain in the SDK, and if so,
we need to clarify what it is needed for and what it should contain.
"The original intent of shipping some amount of source with our
binary developer's release was effectively to treat the source as
supplementary developer's documentation. If they had trouble
understanding what some API should do, they could just look at its
implementation. We didn't want to put out all of our source that way,
just the relatively high-level stuff so people could see what input
checking was done, errors thrown, etc." (Tim's recollection)
This argument is weaker than it used to be, and the more recent arguments
for keeping src.jar in the bundle is that there is a belief that our IDE
vendors need it. If this is the case, then this need should be clarified.
Risks surrounding this need should also be clarified. (There is no
guarantee that OEM licensees will include src.jar when they port the SDK
to their platform.)
Including the src.jar also impacts the download footprint of the SDK and
also involves a maintenance cost.
If the decision is made to keep src.jar around for the original reasons,
then it should just contain user-level APIs.
janet.koenig@Eng 2000-01-27
we need to clarify what it is needed for and what it should contain.
"The original intent of shipping some amount of source with our
binary developer's release was effectively to treat the source as
supplementary developer's documentation. If they had trouble
understanding what some API should do, they could just look at its
implementation. We didn't want to put out all of our source that way,
just the relatively high-level stuff so people could see what input
checking was done, errors thrown, etc." (Tim's recollection)
This argument is weaker than it used to be, and the more recent arguments
for keeping src.jar in the bundle is that there is a belief that our IDE
vendors need it. If this is the case, then this need should be clarified.
Risks surrounding this need should also be clarified. (There is no
guarantee that OEM licensees will include src.jar when they port the SDK
to their platform.)
Including the src.jar also impacts the download footprint of the SDK and
also involves a maintenance cost.
If the decision is made to keep src.jar around for the original reasons,
then it should just contain user-level APIs.
janet.koenig@Eng 2000-01-27
- relates to
-
JDK-4305590 Please remove src/ from files in src.jar to better reveal the package structure
-
- Resolved
-
-
JDK-4283031 Please put back src.jar
-
- Resolved
-