shibboleth-dev - Re: javac -target
Subject: Shibboleth Developers
List archive
- From: Tom Scavo <>
- To: Howard Gilbert <>
- Cc: Shibboleth Development <>
- Subject: Re: javac -target
- Date: Wed, 4 May 2005 08:25:50 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Jbnc0jJ9jIWS4E5F+NRJ6UjaZitPzbeuc1RFo1Roh2PqyL/ftnCRr2V0/cHUYcFE6h2gQO+mBumcS1wyMqZoeyI+Jt0BbXD0CEAvPcPHI7B3Rrfe/DAQxHFf1HB3IbAp+UN8llmJ+Leq609NRaVFSEHrUhAUNCnwmQokaxKP0wc=
If you search the Sun site for "javac target source" you'll find some
interesting discussion regarding this topic. The documentation
suggests that the -target option be accompanied by other options,
namely, -bootclasspath and -extdirs. This could be contributing to
the problems I'm seeing.
Thanks,
Tom
On 5/4/05, Howard Gilbert
<>
wrote:
> The target="1.4" is specified correctly and is necessary. If not specified,
> then if the source is compiled with a JDK 1.5 compiler it will produce class
> files that do not run on a 1.4 system. If a compiler is generating incorrect
> output, or a runtime is not running the files, then this is an error in the
> compiler or runtime. Although you are certainly free to remove this option
> for your own compiles, because locally you can ensure consistent levels of
> Java, it would be a source of errors if they were removed from the official
> build process. We would just end up with a long string of "unsupported
> major.minor version 49.0" error complaints.
- javac -target, Tom Scavo, 05/03/2005
- RE: javac -target, Howard Gilbert, 05/04/2005
- Re: javac -target, Tom Scavo, 05/04/2005
- RE: javac -target, Howard Gilbert, 05/04/2005
- RE: javac -target, Scott Cantor, 05/04/2005
- Re: javac -target, Tom Scavo, 05/04/2005
- RE: javac -target, Howard Gilbert, 05/04/2005
Archive powered by MHonArc 2.6.16.