-
Bug
-
Resolution: Fixed
-
P2
-
1.3.1
-
None
-
rc1
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2042133 | 1.4.0 | Dale Mcduffie | P2 | Resolved | Fixed | beta |
Name: dm26566 Date: 04/03/2001
Ladybird build 21 generates incorrect bundle names when the MILESTONE=fcs
build is performed.
In particular, the Install Shield bundles have the following names:
j2re-1.3.1-internal-win-i.exe
j2re-1.3.1-internal-win.exe
j2sdk-1.3.1-internal-win.exe
jinstall-1_3_1-internal-win.cab
instead of
j2re-1.3.1-fcs-win-i.exe
j2re-1.3.1-fcs-win.exe
j2sdk-1.3.1-fcs-win.exe
jinstall-1_3_1-fcs-win.cab
This is symtomatic of a potentially bigger issue: the MILESTONE value
of 'internal' was used by the Install Shield makefile to generate the
bundles. The MILESTONE value is used to to generate the RELEASE, and
RELEASE is incorporated into VERSION in the ISheild Makefiles. VERSION
is used to set PLUGIN_VERSION and WEB_VERSION.
Although the bundles appear to install just fine, there may be some
lurking issues. It is best to just fix this.
======================================================================
dale.mcduffie@Eng 2001-04-04
- backported by
-
JDK-2042133 win32 FCS Install Shield bundles named with wrong MILESTONE value
-
- Resolved
-
- relates to
-
JDK-4427056 cannot generate fcs version linux bundles
-
- Resolved
-