Return-Path: 
 <buildr-user-return-243-apmail-incubator-buildr-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-buildr-user-archive@locus.apache.org
Received: (qmail 19802 invoked from network); 5 Mar 2008 18:42:50 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 5 Mar 2008 18:42:50 -0000
Received: (qmail 9776 invoked by uid 500); 5 Mar 2008 18:42:46 -0000
Delivered-To: apmail-incubator-buildr-user-archive@incubator.apache.org
Received: (qmail 9758 invoked by uid 500); 5 Mar 2008 18:42:46 -0000
Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:buildr-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:buildr-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:buildr-user@incubator.apache.org>
List-Id: <buildr-user.incubator.apache.org>
Reply-To: buildr-user@incubator.apache.org
Delivered-To: mailing list buildr-user@incubator.apache.org
Received: (qmail 9749 invoked by uid 99); 5 Mar 2008 18:42:46 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 10:42:46 -0800
X-ASF-Spam-Status: No, hits=2.7 required=10.0
	tests=HTML_MESSAGE,SPF_SOFTFAIL
X-Spam-Check-By: apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 arkin@intalio.com does not designate 72.14.220.156 as permitted sender)
Received: from [72.14.220.156] (HELO fg-out-1718.google.com) (72.14.220.156)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 18:42:11 +0000
Received: by fg-out-1718.google.com with SMTP id 22so1625812fge.26
        for <buildr-user@incubator.apache.org>;
 Wed, 05 Mar 2008 10:42:20 -0800 (PST)
Received: by 10.86.73.17 with SMTP id v17mr3356848fga.37.1204742539803;
        Wed, 05 Mar 2008 10:42:19 -0800 (PST)
Received: by 10.86.100.18 with HTTP; Wed, 5 Mar 2008 10:42:19 -0800 (PST)
Message-ID: <3de5d7d20803051042l37861f9cif21ef79d48d91c59@mail.gmail.com>
Date: Wed, 5 Mar 2008 10:42:19 -0800
From: "Assaf Arkin" <arkin@intalio.com>
To: buildr-user@incubator.apache.org
Subject: Re: javac's -cp flag (a buildr compilation bug?)
In-Reply-To: <ecebefa10803051035q6a149933pb6ce4571e8c0b78b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1640_27982388.1204742539814"
References: <ecebefa10803051035q6a149933pb6ce4571e8c0b78b@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_1640_27982388.1204742539814
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 3/5/08, Caleb Powell <caleb.powell@gmail.com> wrote:
>
> Hi,
>
> I was using buildr (1.2.1) to compile code in an existing Maven project.
> The
> compile task failed because the Java compiler (Sun JDK1.4.2_13 on Windows=
)
> does not accept the
> '-cp' alias. From what I can tell, the '-cp' alias was not introduced
> until
> the 1.5 compiler. Here was the output where JAVA_HOME was set to the Sun
> 1.4.2_13 JDK;
>
> Compiling 403 source files in pharmacy-core:compile
> javac: invalid flag: -cp
> Usage: javac <options> <source files>
> where possible options include:
>   -g                        Generate all debugging info
>   -g:none                   Generate no debugging info
>   -g:{lines,vars,source}    Generate only some debugging info
>   -nowarn                   Generate no warnings
>   -verbose                  Output messages about what the compiler is
> doing
>   -deprecation              Output source locations where deprecated APIs
> are used
>   -classpath <path>         Specify where to find user class files
>   -sourcepath <path>        Specify where to find input source files
>   -bootclasspath <path>     Override location of bootstrap class files
>   -extdirs <dirs>           Override location of installed extensions
>   -d <directory>            Specify where to place generated class files
>   -encoding <encoding>      Specify character encoding used by source
> files
>   -source <release>         Provide source compatibility with specified
> release
>   -target <release>         Generate class files for specific VM version
>   -help                     Print a synopsis of standard options
>
> rake aborted!
>
> Assuming that buildr should be compatible with the 1.4.x JDK's (is this
> assumption wrong), than I think this qualifies as a bug (which could be
> easily addressed by using 'classpath').
>
> In the meantime, is there any workaround to this issue (short of using th=
e
> 1.5 JDK)?
>
> Cheers!


Newer versions of Buildr invoke the Java compiler through RJB, so they're
not affected but this and also run the build substantially faster.

Assaf


--
> Caleb
>
> "I do not know which makes a man more conservative=97to know nothing but =
the
> present, or nothing but the past."
>   - John Maynard Keynes
>

------=_Part_1640_27982388.1204742539814--