Contents of /licenses/dlj-1.1

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.3 - (show annotations) (download)
Thu Dec 1 00:16:05 2011 UTC (8 years, 4 months ago) by mr_bones_
Branch: MAIN
Changes since 1.2: +0 -0 lines
clean unused license

1 Operating System Distributor License for Java version 1.1
10 1. DEFINITIONS. "Software" means the code identified above in binary
11 form, any other machine readable materials including, but not
12 limited to, libraries, source files, header files, and data files),
13 any updates or error corrections provided by Sun, and any user
14 manuals, programming guides and other documentation provided to you
15 by Sun under this Agreement, and any subsequent versions that Sun
16 makes available to you hereunder. "Operating System" means any
17 version of the Linux or OpenSolaris operating systems that manages
18 the hardware resources of a general purpose desktop or server
19 computer and shares these resources with various software programs
20 that run on top of it. "Programs" means Java technology applets and
21 applications intended to run on the Java Platform Standard Edition
22 (Java SE platform) platform on Java-enabled general purpose desktop
23 computers and servers.
25 2. License Grant. Subject to the terms and conditions of this
26 Agreement, as well as the restrictions and exceptions set forth in
27 the Software README file, Sun grants you a non-exclusive,
28 non-transferable, royalty-free limited license to reproduce and use
29 the Software internally, complete and unmodified, for the sole
30 purposes of running Programs and designing, developing and testing
31 Programs. Sun also grants you a non-exclusive, non-transferable,
32 royalty-free limited license to reproduce and distribute the
33 Software, directly or indirectly through your licensees,
34 distributors, resellers, or OEMs, electronically or in physical
35 form or pre-installed with your Operating System on a general
36 purpose desktop computer or server, provided that: (a) the Software
37 and any proprietary legends or notices are complete and unmodified;
38 (b) the Software is distributed with your Operating System, and
39 such distribution is solely for the purposes of running Programs
40 under the control of your Operating System and designing,
41 developing and testing Programs to be run under the control of your
42 Operating System; (c) you do not combine, configure or distribute
43 the Software to run in conjunction with any additional software
44 that implements the same or similar functionality or APIs as the
45 Software; (d) you do not remove or modify any included license
46 agreement or impede or prevent it from displaying and requiring
47 acceptance; (e) you only distribute the Software subject to this
48 license agreement; and (f) you agree to defend and indemnify Sun
49 and its licensors from and against any damages, costs, liabilities,
50 settlement amounts and/or expenses (including attorneys' fees)
51 incurred in connection with any claim, lawsuit or action by any
52 third party that arises or results from (i) the use or distribution
53 of your Operating System, or any part thereof, in any manner, or
54 (ii) your use or distribution of the Software in violation of the
55 terms of this Agreement or applicable law. You shall not be
56 obligated under Section 2(f)(i) if such claim would not have
57 occurred but for a modification made to your Operating System by
58 someone not under your direction or control, and you were in
59 compliance with all other terms of this Agreement. If the Software
60 README file permits certain files to be replaced or omitted from
61 your distribution, then any such replacement(s) or omission(s)
62 shall not be considered a breach of Section 2(a).
64 3. RESTRICTIONS. Software is copyrighted and title to Software and
65 all associated intellectual property rights is retained by Sun
66 and/or its licensors. Unless enforcement is prohibited by
67 applicable law, you may not modify, decompile, or reverse engineer
68 Software. You may not create, modify, or change the behavior of,
69 or authorize your licensees, distributors, resellers, OEMs, or end
70 users (collectively, "Licensees") to create, modify, or change the
71 behavior of, classes, interfaces, or subpackages that are in any
72 way identified as "java", "javax", "sun" or similar convention as
73 specified by Sun in any naming convention designation. You
74 acknowledge that Licensed Software is not designed or intended for
75 use in the design, construction, operation or maintenance of any
76 nuclear facility. Sun Microsystems, Inc. disclaims any express or
77 implied warranty of fitness for such uses.
79 4. COMPATIBILITY. If you exercise the license in Section 2, and Sun
80 or a licensee of the Software (under section 4(b)) notifies you
81 that there are compatibility issues (as determined by the
82 applicable Technology Compatibility Kit) caused by the interaction
83 of the Software with your Operating System, then within ninety
84 (90) days you must either: (a) modify the Operating System in a
85 way that resolves the compatibility issue (as determined by Sun)
86 and make a patch or replacement version available to your
87 Licensees who have already received the version of your Operating
88 System that was the subject of the compatibility issue ("Your
89 Incompatible Operating System"); or (b) cease distributing the
90 Software and make commercially reasonable attempts to forward the
91 notification to your Licensees who have already received Your
92 Incompatible Operating System.
94 5. Trademarks and Logos. No right, title or interest in or to any
95 trademark, service mark, logo or trade name of Sun or its
96 licensors is granted under this Agreement. You acknowledge and
97 agree that, as between you and Sun, Sun owns the SUN and JAVA
98 trademarks and all SUN and JAVA-related trademarks, service marks,
99 logos and other brand designations ("Sun Marks"), and you agree to
100 comply with the Sun Trademark and Logo Usage Requirements
101 currently located at http://www.sun.com/policies/trademarks. Any
102 use you make of the Sun Marks inures to Sun's benefit.
104 6. LIMITED WARRANTY. If you received the Software directly from Sun
105 or its authorized resellers, Sun warrants to you that for a period
106 of ninety (90) days from delivery to you, the media on which
107 Software is furnished (if any) will be free of defects in
108 materials and workmanship under normal use. Except for the
109 foregoing, Software is provided "AS IS". Your exclusive remedy
110 and Sun's entire liability under this limited warranty will be
111 replacement of the Software media. This limited warranty gives
112 you specific legal rights. You may have others, which vary from
113 state to state.
127 Sun's liability to you, whether in contract, tort (including
128 negligence), or otherwise, exceed the amount paid by you for the
129 Software under this Agreement. The foregoing limitations will
130 apply even if the above stated warranty fails of its essential
131 purpose. Some states do not allow the exclusion of incidental or
132 consequential damages, so some of the terms above may not be
133 applicable to you.
135 9. THIRD PARTY CODE. Additional copyright notices and license terms
136 applicable to portions of the Software are set forth in the
137 THIRDPARTYLICENSEREADME.txt file. In addition to any terms and
138 conditions of any third party opensource/freeware license
139 identified in the THIRDPARTYLICENSEREADME.txt file, the disclaimer
140 of warranty and limitation of liability provisions in paragraphs 7
141 and 8 of this Agreement shall apply to all Software in this
142 distribution.
144 10. Termination. This Agreement is effective until it is
145 terminated. You may terminate this Agreement at any time by
146 ceasing distribution of the Software. This Agreement will
147 terminate immediately without notice from Sun if you fail to
148 comply with any material provision herein. Either party may
149 terminate this Agreement immediately should any Software become,
150 or in either party's opinion be likely to become, the subject of a
151 claim of infringement of any intellectual property right. Upon
152 termination, you must destroy all copies and cease copying and
153 distribution of the Software. All of your obligations and any
154 applicable limitations on your rights and remedies under this
155 Agreement shall survive termination.
157 11. SOURCE CODE. Software may contain source code that, unless
158 expressly licensed for other purposes, is provided solely for
159 reference purposes pursuant to the terms of this Agreement.
160 Source code may not be redistributed unless expressly provided for
161 in this Agreement.
163 12. Export Regulations. All Software and technical data delivered
164 under this Agreement are subject to US export control laws and may
165 be subject to export or import regulations in other countries.
166 You acknowledge that you have the responsibility to obtain such
167 licenses to export, re-export, or import as may be required after
168 delivery to you.
170 13. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is being acquired
171 by or on behalf of the U.S. Government or by a U.S. Government
172 prime contractor or subcontractor (at any tier), then the
173 Government's rights in Software and accompanying documentation
174 will be only as set forth in this Agreement; this is in accordance
175 with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense
176 (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD
177 acquisitions).
179 14. MISCELLANEOUS. Any action related to this Agreement will be
180 governed by California law and controlling U.S. federal law. No
181 choice of law rules of any jurisdiction will apply. If any
182 provision of this Agreement is held to be unenforceable, this
183 Agreement will remain in effect upon the parties' agreement to
184 revised terms that most nearly accomplish the same effect. This
185 Agreement is the entire agreement between you and Sun relating to
186 its subject matter. It supersedes all prior or contemporaneous
187 oral or written communications, proposals, representations and
188 warranties and prevails over any conflicting or additional terms
189 of any quote, order, acknowledgment, or other communication
190 between the parties relating to its subject matter during the term
191 of this Agreement. No modification of this Agreement will be
192 binding, unless in writing and signed by an authorized
193 representative of each party.
195 For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle,
196 Santa Clara, California 95054, U.S.A.
198 DLJ v1.1 27APR2006ANS
200 - - - - - end of DLJ License text - - - - -
202 -------------------------------------------------------------------------------
203 *******************************************************************************
204 -------------------------------------------------------------------------------
206 FAQ for the Operating System Distributor License for Java (DLJ)
208 The purpose of this FAQ is to provide some insight into Sun's thoughts
209 in creating the Operating System Distributor License for Java.
210 Although the FAQ is not a legal document, it is designed to illustrate
211 the license terms through explanation and examples. This is a well
212 accepted way of helping non-lawyers attain some comfort with legal
213 language, which is crafted by attorneys to meet the arcane
214 requirements of statutes and judicial opinions. For example,
215 Creative Commons does a similar thing with its "Deeds,"
216 (e.g. http://creativecommons.org/licenses/by-sa/2.5/ ) which are
217 human-readable summaries of the "Legal Code"
218 (e.g. http://creativecommons.org/licenses/by-sa/2.5/legalcode ) and
219 and are accompanied by a legal disclaimer
220 ( http://creativecommons.org/licenses/disclaimer-popup?lang=en-us ).
222 If you think our FAQ is contradicted by the language in the license,
223 we'd like to hear from you so that we can consider revising the
224 license to clear up any confusion. Otherwise, we encourage you to
225 think of the FAQ as a series of guideposts designed to help you
226 understand and work with the license terms. Of course, if Sun clearly
227 says in an FAQ that it's okay to do something (and we haven't made a
228 blatant typographical error), we're not going to sue you -- even if
229 one could make a clever legal argument that the license doesn't permit
230 it. We believe in simplicity and transparency, and pledge to work
231 diligently with the community to achieve those objectives.
233 Sun expects to periodically update this FAQ to better reflect the
234 concerns and questions of the developer community. You will find a
235 pointer to the latest version of this FAQ at:
236 https://jdk-distros.dev.java.net/developer.html
238 1. What is the Operating System Distribution License for Java
239 (a.k.a. the "Distro License for Java" or DLJ)?
241 The DLJ is a license created specifically for individuals and
242 communities who want to distribute Sun's binary Java Development
243 Kit (JDK) or Java Runtime Environment (JRE) with a Linux or
244 OpenSolaris Operating System (OS) distribution.
246 2. Why is Sun releasing the DLJ?
248 It's been difficult for developers who want to use Java SE
249 technology on a broad choice of Linux or OpenSolaris distributions
250 to easily obtain and use Sun's JDK or JRE. One issue has been the
251 redistribution terms of the Binary Code License (BCL) for Java SE
252 technology, which was never intended to license these bits for
253 general distribution with an Operating System. With this new
254 license, Sun is enabling the developer community to distribute our
255 binary JDK and JRE with distributions of Linux or OpenSolaris
256 operating systems, while still maintaining compatibility with the
257 Java Specifications.
259 3. How do I become a "DLJ Licensee?"
261 The DLJ is distributed by Sun as a "click-through license" in
262 special bundles available on java.net in the jdk-distros project
263 at https://jdk-distros.dev.java.net . These bundles contain the
264 same JDK software found in the standard Linux distribution bundles
265 and the Solaris bundles in the download area on java.sun.com
266 except that the LICENSE and README file are replaced by the DLJ
267 and a modified README file with matching terms. The README file
268 included in these bundles allows you to create JRE distributions
269 from the JDK bundles by following instructions in the file.
271 4. What does the DLJ allow me to do?
273 You can:
274 - Use the JDK on your OS to design, develop, test, and run Java programs.
275 - Repackage the JDK for use with your OS, within the limitations
276 spelled out in the README file.
277 - Distribute the JDK on any media, online, and preinstalled on
278 systems as a package with your OS.
279 - Distribute the JDK directly, or indirectly through your
280 licensees, distributors, resellers, OEMs, or downstream
281 recipients of your OS.
283 5. When I exercise the license and distribute the JDK, does it become
284 part of my Operating System, or do I need to explicitly declare it
285 as part of my OS?
287 No - the license grants you the right to distribute the JDK with
288 your Operating System, but it is still a separate piece of
289 software. You do not need to make the JDK part of what you define
290 as your OS when you exercise the license. All you need to do to
291 exercise the license is distribute the JDK with your OS. For
292 example, you could distribute the JDK bundles on a CD with your
293 OS, or in a package repository for your OS on your mirror
294 distribution sites.
296 6. Can projects such as the JPackage Project exercise the DLJ?
298 Sun recognizes and encourages the contributions of projects such
299 as the JPackage Project ( http://www.jpackage.org ) to the adoption
300 of Java technology on GNU/Linux OSs. Such projects are very
301 similar to the jdk-distros project that Sun has established,
302 providing recommendations for packaging Java technology with OS
303 distributions, but not actually distributing an OS. Anyone can
304 provide recommendations for packaging under the DLJ, but only
305 GNU/Linux and OpenSolaris OS distributors may exercise the DLJ and
306 ship the JDK, as the license requires that you ship the JDK
307 bundles with an OS.
309 7. I distribute my OS online from multiple mirror sites. Does such a
310 multi-site online distribution model fit into the definition of
311 "online" under this license?
313 Yes it does. Each mirror is, in essence, a downstream distributor
314 of the original OS bundles from the master site. Accordingly, the
315 mirror sites may distribute the JDK as part of these bundles,
316 under the terms and conditions of the DLJ.
318 8. What are my obligations under this license?
320 The license is the best reference for this. Some of the important
321 terms to consider are that you are required to:
322 - Keep all copyright and other notices intact.
323 - Distribute the entire JDK - no subsetting. Note - the README
324 file has the specifics of what you must distribute, and what can
325 be omitted.
326 - Use the JDK only to design, develop, test, and run Java programs
327 on your OS - you may not use it or parts of it for other
328 purposes.
329 - Present for acceptance any end user licenses that are part of
330 the JDK, if such licenses are included in the generic install
331 bundle provided to you for repackaging.
332 - Redistribute subject to the DLJ - so that downstream users and
333 distributors of the JDK are also subject to the DLJ's terms.
334 - Indemnify Sun against claims arising from your OS or your
335 violation of the DLJ (or any applicable law) Note that you are
336 not responsible for changes made to your OS distribution by
337 downstream users or distributors when such changes are out of
338 your control.
339 - Ship only a compatible JDK on your OS. If notified of an
340 incompatibility, you must correct it and offer a patch or
341 replacement to downstream recipients within 90 days, or stop
342 shipment and notify downstream recipients.
344 9. What is the README file? Is it part of the license? Why not include
345 it with the rest of the license?
347 The README file is explicitly called out in Section 2. License
348 Grant as a document that provides specific exceptions and
349 restrictions to what you may distribute, and should be considered
350 an adjunct to the license. The reason for keeping these details in
351 a separate file is simple: it allows us to adjust the technical
352 details of what constitutes the "Software" and what parts may be
353 redistributed separately or omitted from a distribution without
354 revising the license itself. This allows us to more quickly react
355 to clarify allowable modifications as additional distributions
356 package the JDK and discover modifications that are required to
357 ensure compatibility and quality.
359 You will find a pointer to the latest version of the README at:
360 https://jdk-distros.dev.java.net/developer.html
362 10. May I redistribute the src.zip file?
364 This is one of the files listed in the README as being optional,
365 but redistributable, so yes.
367 11. If I am working on alternative technology projects, will I be
368 "tainted" by the existence of the src.zip file on my system, or if
369 I open this file and examine its contents?
371 No. The source in src.zip is licensed as a reference for running,
372 designing, developing and testing Java applications, and is an
373 integral and useful component of the JDK. Sun maintains that you
374 aren't tainted simply by having looked at this code, or having it
375 on your hard drive.
377 12. How do I ensure that my package reproduces all the right copyright
378 notices and proprietary legends as required in Section 2(a)?
380 If you make certain that any copyright notices and licenses for
381 the packaging are clearly separate from the notices for the Java
382 platform, you'll be fine. Just make sure you distribute all the
383 notices that are provided as part of the JDK bundles you are
384 repackaging. For example in the 1.5.0 bundles, the notices are in
385 the following files in the top level directory:
391 These files are the copyright notice for the JRE or JDK packages,
392 the license terms (DLJ) for the JRE or JDK packages and the
393 copyright notices and license terms for the THIRD PARTY CODE,
394 respectively.
396 13. Can I use the JDK to develop programs that can be run anywhere,
397 or only for my OS? Section 2(b) seems to say I can't use the JDK
398 for developing arbitrary Java language applications.
400 The license allows you and your users to run Java programs from
401 any source, and develop Java programs for any platform. If you
402 distribute the JDK under this license, you must distribute it with
403 your OS, and for the purpose of running and developing Java
404 programs on your OS. The DLJ does not give you the right to
405 distribute a "naked" version of the JDK without your OS. The
406 purpose of the language in 2(b) is to require that you include
407 your OS, and to use the JDK only for its normal intended purpose
408 of running and developing Java programs.
410 14. Does this license prevent me shipping any alternative technologies
411 in my OS distribution?
413 The DLJ does not restrict you from shipping any other technologies
414 you choose to include in your distribution. However, you can't use
415 pieces of the JDK configured in conjunction with any alternative
416 technologies to create hybrid implementations, or mingle the code
417 from the JDK with non-JDK components of any kind so that they run
418 together. It is of course perfectly OK to ship programs or
419 libraries that use the JDK. Because this question has caused
420 confusion in the past, we want to make this absolutely clear:
421 except for these limitations on combining technologies, there is
422 nothing in the DLJ intended to prevent you from shipping
423 alternative technologies with your OS distribution.
425 15. So, can I ship Eclipse, or other language implementations like
426 Perl or Python?
428 Sun can't give you permission to ship these technologies. Only the
429 lawful owners and licensors of those technologies can do that. The
430 DLJ doesn't prohibit you from shipping them or from running them.
432 16. If some program in my OS specifies the option -Xbootclasspath to
433 the java command, is that considered a breach of Section 2(c)?
435 We realize there is some confusion about this because the
436 documentation for the java command at
437 http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/java.html
438 makes specific mention of the Binary Code License (BCL). The
439 intent of Section 2(c) is not to restrict what end user programs
440 do with command line options but rather to ensure that the Sun
441 Java platform is not used to create hybrid implementations with
442 alternate technologies, or mingle the JDK code with alternate
443 technologies so they run together.
445 17. What do you mean by "Present for acceptance end user licenses"
446 (from #8 above)? Do I have to create a click-through license
447 display when a user first installs or runs the JDK? Must my users
448 accept the license?
450 Your users must agree to the license terms for the JDK before
451 installing it. While you aren't required to show the DLJ on first
452 use or installation, you must inform them that the JDK is licensed
453 software and that they must agree to the license before using
454 it. A click-through mechanism is the preferred way to do this, but
455 at a minimum you must present the license by some appropriate
456 means for acceptance. For example, your OS download procedure
457 could show the user a page that informs him or her that software
458 packages included in the download may contain software licenses to
459 which the user must agree before installation, and allow the user
460 to review them before download.
462 You can leverage your distribution's packaging technology to
463 ensure that the license terms have been accepted. For instance, on
464 Debian and derivative distributions, you could configure the
465 package so that if the debconf key for accepting the DLJ has not
466 been pre-accepted, the installation will be canceled if the
467 license cannot be presented. The point of presenting the license
468 is that an individual, corporation, non-profit or entity which
469 will be an end user of the JRE or JDK has had a chance to review
470 and agree to the DLJ. If the user or administrator pre-accepts
471 the key for DLJ agreement on behalf of herself or her group then
472 it is perfectly acceptable to silently install Sun Java on one or
473 many computers. This is an excellent example of how you can
474 leverage packaging infrastructure to comply with the terms of the
475 DLJ in ways that are convenient and expected for your users.
477 18. How do I redistribute the JDK in my OS, so that downstream
478 recipients are subject to the DLJ? Do I need to do anything
479 special?
481 Nothing special - just be sure to include the license in your JDK
482 bundle, and inform your downstream recipients that the JDK is
483 subject to the license when they download or install it.
485 19. What obligations do I assume when I receive the JDK as part of an
486 OS distribution, and then turn around and redistribute it, even if
487 I don't change a thing?
489 When you redistribute the JDK under the DLJ, you are subject to
490 its terms. This means that you are granted the rights described in
491 the license (provided you remain in compliance with the license
492 terms) and assume its obligations, including compatibility
493 requirements and indemnification. It doesn't matter whether you
494 change the distribution you receive or not. When you redistribute,
495 you do so under the terms of the DLJ.
497 20. Why does Sun ask for indemnification? What indemnification am I
498 providing to Sun? I'm concerned that I will be held responsible
499 for things over which I have no control.
501 Simply put, Sun requires indemnification to limit its exposure for
502 issues that are not Sun's fault. If your conduct or your OS
503 causes a problem that results in a third-party claim, then Sun
504 expects you to take responsibility for it. Note that you are not
505 indemnifying Sun against claims that are a result of something in
506 Sun's code. You also are not indemnifying Sun against claims due
507 to changes that a downstream distributor has made to your OS.
509 Since downstream distributors must redistribute the JDK under the
510 terms of the DLJ, they are the ones providing indemnification to
511 Sun for the changes they've made to your OS - which is now their
512 OS for the purposes of this license.
514 21. What do you mean by "compatible"?
516 "Compatible" has a very specific meaning for Java technology, and
517 in this license. Specifically, a "Compatible" Implementation" is
518 an implementation of the Java SE technology specification that
519 meets the requirements of the Technology Compatibility Kit (TCK).,
520 i.e., the compliance tests, tools and documentation which allows
521 you to establish whether a particular implementation completely
522 and correctly implements the Java SE Specification on a specific
523 host platform.
525 22. Am I required to run the TCK before I distribute the software?
527 No, this license does not require that you run the TCK.
529 23. How do I learn more about the TCK?
531 There is a "read-only" version of the Java SE TCK available at
532 https://jck.dev.java.net which you can look at to better
533 understand the compatibility requirements. The license for this
534 is for evaluation purposes only.
536 24. How do I verify compatibility when I don't have the TCK?
538 The DLJ is a binary redistribution license, for a binary that has
539 been verified on Sun's supported OS platforms (see
540 http://java.sun.com/j2se/1.5.0/system-configurations.html ).
541 However, it is possible that the combination of Sun's JDK with
542 your OS distribution could break compatibility. The jdk-distros
543 project was created as a place for Linux, OpenSolaris, and Java
544 developers to cooperate on creating new packaging for the JDK,
545 solving problems including compatibility issues, and as a
546 clearinghouse for best practices, tips and tricks, examples, and
547 solutions to common issues. This project includes helpful guides
548 to potential problems with compatibility based on Sun's experience
549 in creating JDK bundles for supported OS versions. You can use
550 this guide to help you discover potential problems before you
551 distribute the JDK with your OS.
553 25. I'd like to test my OS distribution's compatibility. How do I
554 obtain the TCK?
556 The TCK is available under a usage license that includes some
557 support, and which may be purchased from Sun.
559 If you are a qualified not-for-profit organization, you may be
560 eligible to obtain the TCK under a scholarship. You can find more
561 information about this program and request a scholarship
562 application at: http://java.sun.com/scholarship/
564 There is a "read-only" version of the Java SE TCK available at
565 http://jck.dev.java.net which you can look at to better understand
566 the compatibility requirements. The license for this is for
567 evaluation purposes only and while it does not allow you to run
568 the TCK, it may be helpful in your understanding of its
569 requirements.
571 26. What happens if my OS does not behave compatibly with the JDK?
573 Sun provides JDK bundles which have been qualified as compatible
574 on several common Linux distributions and on
575 Solaris. Incompatibility problems will typically be the result of
576 variations between your OS and common distributions. Accordingly
577 you should fix any problems you are aware of in your OS before
578 distributing the software. The JDK must behave in a compatible
579 manner when running on your OS.
581 27. If I'm aware of problems, can I document them for my users
582 and ship anyway?
584 No, you must fix the problems before distributing the software. It
585 is worth noting however, that you may document supported and
586 unsupported platform configurations such as specific web browsers,
587 OS versions, or hardware devices.
589 28. What if a problem comes up after I distribute the software?
591 If Sun becomes aware of a compatibility problem with the JDK
592 software on your OS distribution and notifies you about it, then
593 you must fix the problem and offer a patch or new version to your
594 downstream users and distributors, or stop distributing the
595 software within 90 days of being notified. If you stop
596 distributing the software, you must also make reasonable attempts
597 to notify your users, and anyone who might have downloaded your OS
598 distribution. Once your downstream users are notified, they must
599 make the same choice (i.e. fix the problem or stop
600 using/distributing the software)
602 Remember, you are always allowed to discontinue distribution of
603 the JDK and make a reasonable attempt to notify your downstream
604 users and distributors. For example you can stop shipping Sun Java
605 by removing it from the list of currently available software for
606 your OS. Sun will consider a stop-ship action to be a suitable
607 remedy for any compatibility problems. If at some future time you
608 are able to fix the problem, you can resume distribution of the
609 JDK under the terms of the DLJ.
611 29. If I decide to stop-ship, must I remove the JDK from archived and
612 compatible distribution bundles as well?
614 No, archived bundles can contain the JDK as long as there are no
615 compatibility issues. Removing the JDK from your active
616 distribution should be sufficient. For instance, on Debian and
617 derivative operating systems, you could remove the Sun Java
618 packages from the tag database so that users can no longer install
619 them using the conventional method (e.g. apt-get install
620 sun-java5-jre).
622 30. What does Section 12, Export Regulations, mean?
624 As a U.S. company, Sun is obligated to comply with U.S. export
625 regulations --as well as the regulations of other countries where
626 it does business or ships to. One way we comply with this
627 obligation is to bring these laws and regulations to your
628 attention. Ultimately you are responsible for ensuring that your
629 use and distribution of the Software is in accordance with export
630 regulations, as well as any other applicable laws.
632 31. May I use the Java logo to show that I'm including the JDK in my
633 OS distribution? What may I do with Java logos?
635 No, you may not use the logo, as the right to use the logo is
636 based on acquiring a TCK license and passing the TCK. You may
637 state that you include the JDK as part of your description of your
638 distribution. This license does not grant any right to use any Sun
639 mark or logo.
641 32. What notification must I give Sun before distributing the JDK?
643 You are not required to notify Sun, or register. You might find it
644 useful however to post something in the jdk-distros project forums
645 so that others interested in similar OS distributions to yours can
646 share their experiences with you and you can collaborate with them
647 on common issues and solutions.
649 33. Who can I contact if I have additional questions or comments?
651 You can send questions related to the DLJ to DLJfeedback@sun.com
652 and/or post comments on the jdk-distros project forums on
653 java.net, at http://forums.java.net/jive/forum.jspa?forumID=94 .
655 DLJ FAQ v1.2
657 - - - - - end of DLJ FAQ text - - - - -

  ViewVC Help
Powered by ViewVC 1.1.20