/usr/share/doc/java-common/debian-java-policy/c180.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Issues to discuss</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Debian policy for Java"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Main, contrib or non-free"
HREF="x169.html"><LINK
REL="NEXT"
TITLE="Advices to Java packagers"
HREF="c208.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Debian policy for Java</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="x169.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="c208.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
><H1
><A
NAME="to-discuss"
></A
>Chapter 3. Issues to discuss</H1
><P
>&#13;      The following points are discussions about the policy, either
      because they have to be studied more, or are controversial.</P
><P
></P
><UL
><LI
><P
>&#13;	  Name and existence of the repository. It was removed
	  in the latest version.
	</P
></LI
><LI
><P
>&#13;	  The symbolic links in <TT
CLASS="filename"
>/usr/share/java</TT
> be
	  made by a script instead, similar to the c-libraries.
	</P
></LI
><LI
><P
>Core classes (<TT
CLASS="filename"
>java.*</TT
>). More study
	  needed.</P
></LI
><LI
><P
>&#13;	  Sun's Community Source Licence. Can we use it? How?
	  The 2.3 version of the text can be found 
	  <A
HREF="http://wwws.sun.com/software/java2/license.html"
TARGET="_top"
>here</A
>.
	</P
></LI
><LI
><P
>All jars must have a good CLASSPATH documentation, but
	  how should it be documented. The best solution is probably in some
	  computer parsable format to make it even easier for the developer.
	</P
><P
>It should exist some tool to parse this. How should it
	  work?
	</P
><P
>Should the tool also be used to create the necessary symbolic
	  links needed by servlets under tomcat?
	</P
></LI
><LI
><P
>&#13;	  Should there be a default CLASSPATH, similar to a
	  repository? Which jars should be included in that? A standard and
	  one optional part? If there are a default CLASSPATH (in the
	  wrapper) how should it be overridden?
	</P
></LI
><LI
><P
>How to check for a good enough <ACRONYM
CLASS="acronym"
>JVM</ACRONYM
>, and to select a
	  proper one to use. Are <TT
CLASS="filename"
>/etc/alternatives</TT
>
	  not good enough?
	</P
></LI
><LI
><P
>&#13;	  Should the <ACRONYM
CLASS="acronym"
>JVM</ACRONYM
> internal classes be possible to
	  override entirely and how?
	</P
></LI
></UL
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="x169.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="c208.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Main, contrib or non-free</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Advices to Java packagers</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
java-common 0.47 / usr / share / doc / java-common / debian-java-policy / c180.html
