fstyle.de

set variableName=path
echo %variableName%

It is so easy to install Java on Ubuntu now. On Ubuntu 7.04 (Feisty Fawn), follow these steps:

1) Make sure you have the right repositories on your sources.list file.

Edit your sources.list file the following way:

sudo gedit /etc/apt/sources.list

or if you are not using gnome (e.g. you are logged in through ssh):

sudo nano /etc/apt/sources.list

If the following lines are not already there, add them:

deb http://us.archive.ubuntu.com/ubuntu feisty main restricted
deb http://us.archive.ubuntu.com/ubuntu feisty universe multiverse

Save the file (in nano use Control-O to save and then Control-X to exit).
Now you need to tell the package manager to update it’s database:

sudo apt-get update

2) Install Java using apt-get

I currently have both Java 5 and Java 6 installed on my machine and
it’s very easy to switch between the two. Java 6 has some nice goodies such as
JSR-223 and better jconsole that I like to use.

For Java 5:

sudo apt-get install sun-java5-jre sun-java5-jdk sun-java5-plugin

For Java 6:

sudo apt-get install sun-java6-jre sun-java6-jdk sun-java6-plugin

There are other packages that you might be interested in:

sun-java6-demo
sun-java6-doc
* sun-java6-source

3) Verify installation

Verify that you have the correct version of java running:

java -version

For example, on my machine (yes, I call it tiwouj):

Ubuntu Java Version

To see a list of the java versions that you have installed, you can use the following command
(it’s a letter L at the end of the command):

update-java-alternatives -l

Ubuntu Java List

This should show you a list of all the java alternatives you have installed. java-gcj is the free version of Java
from the GNU project and comes installed by default with Ubuntu so you should see it.
To switch to a different version, use the following command:

sudo update-java-alternatives -s

e.g:

sudo update-java-alternatives -s java-1.5.0-sun

Make sure it worked:

java -version

That’s it! How easy was that? You have to love apt-get.

Classpath entry will not be exported or published. Runtime ClassNotFoundExceptions may result.

Hi,
I have an Eclipse project that I have converted over to be a dynamic web project.
Now I have 100s of warnings that were not there before (we have a "no warnings" policy).

The warning is of the form:


Classpath entry /XXX/xxx.jar will not be exported or published.
Runtime ClassNotFoundException may result.


I have googled for parts of that warning without finding any hits.
The problem seem to occur when I have a project that has a JAR file included in the project.

1. How can I get the included JAR files exported correctly
(without having to explode the JARs within their respective projects).

and

2. Is there any way to override these warnings and change them to "ignore"
as you can do with the Java or Javadoc compiler settings?
Does anyone have any suggestions?
Best wishes, Ivan

hi Ivan,

WTP 2.0 M6 includes a new feature that allows you to add "J2EE module"
dependencies to classpath entries (cp containers and libraries) so that the
resolved contributions from these entries will be included in
published/exported structure of the module (will be added to the root of the
EAR or the WEB-INF/lib directory of web modules, depending on the type of
dependency).

Management of these dependencies can all be handled through the standard
"J2EE Module Dependencies" UI (there is also a programmatic API).

Part of this support is a validator that adds errors for various conditions
as well as the warning you have encountered. The motivation behind that
warning is that you may have a potential runtime problem if there is
something on the project classpath which is not included in the published
structure of the module and is not part of the standard WTP cp containers
that expose classes available on the server (these "standard" cp containers
are not selectable within the "J2EE Module Dependencies" UI and do not
trigger the warning).

The answer to #1 is to select these cp entries as J2EE module dependencies
(this will also cause the warning to disappear).

I have recently made the following change in this area:

-An extension point has been added (will be in the next I-build) that allows
adopters to register additional cp containers that should not be considered
as potential dependencies (associated cp container entries will therefore
not be available for selection in the J2EE Module Dependencies UI and the
warning will not be generated).

-Rob

org.apache.jasper.JasperException: java.lang.NullPointerException
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:522)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:356)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)


root cause

java.lang.NullPointerException
org.apache.jsp.chooseSemester_jsp._jspInit(chooseSemester_jsp.java:35)
org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:52)
org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:159)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)