http://sablevm.org/bugs/show_bug.cgi?id=88
Summary: SableVM should provide JAVA_HOME like env.
Product: SableVM
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: default
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
SableVM should provide a kind of JAVA_HOME environment, as much similar to
the Sun's SDK as possible. Even if this interface is hardly documented, it
is still quite convinient to use in many situations and as there's no
alternative, widely spreat interface - it is de facto standard.
I think .../lib/sablevm/sdk or similar would be a desirable place.
- bin - should contain java, javac, javah and other executables
- lib - core *.jar files that are path of default (boot)classpath
- jre/lib - native libs (symlinks to) libsablevm, classpath libraries, etc.
- jre/lib/ext - extension directory - other *.jars used by default
- jre/plugin - browser plugins
- include - jni.h, jvmdi.h and other .h files (symlinked from /usr/include)
My personal opinion is that this structure is not quite as natural as one
would wish. I think we'll dump some things into single dirs, or move
dirs around (ie why jre/lib/ext, not just ext?), and then provide symlinks
for compatibility with Sun's messy JAVA_HOME env.
We could start with simple things, ie. adding support for ext directory
or symlinking java-sablevm wrapper to bin, same for include files, etc.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.