Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: buildr-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gethemant@gmail.com
 designates 209.85.198.251 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:in-reply-to:references:content-type:date:message-id
         :mime-version:x-mailer:content-transfer-encoding;
        b=CfdPKFrL7MOLkm1Lk82Jvl6I53E0tbe/xlobpOvZwPPZWijrK3DQT/zk6dDgb43VRa
         NqzeK25xV8gro0BQkjRFNwVkMVtue33YqVA5rFJGck5L8vnp3/1+6PB5MIZl2OlpPnxc
         qO23u6rTtKtFL8X51Dd/IK65QTGiY4EjEwMhs=
Subject: Re: Is buildr 1.3.3 broken for scala projects?
From: hemant kumar <gethemant@gmail.com>
To: buildr-user@incubator.apache.org
In-Reply-To: <5582dd3b0811030525v1d3f3facv1955b93c7530f3af@mail.gmail.com>
References: <fb283d5e0811022338l3e7ad769w2038d116ba27f5a@mail.gmail.com>
	 <5582dd3b0811030525v1d3f3facv1955b93c7530f3af@mail.gmail.com>
Content-Type: text/plain
Date: Mon, 03 Nov 2008 20:31:27 +0530
Message-Id: <1225724487.9049.2.camel@shire>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Okay,

I figured that out eventually. In the meanwhile, I want to point to the
problem of scalac crashing, which buildr eats up silently. Or in other
words, god forbid if your code crashes scalac during compilation, buildr
helpfully eats up the backtrace and all you get is "unknown exception".

Shall I file a bug report about this?


On Mon, 2008-11-03 at 05:25 -0800, Alex Boisvert wrote:
> This is a bug in 1.3.3
> 
> See http://www.nabble.com/Buildr-1.3.3-released-td20035358.html
> 
> On Sun, Nov 2, 2008 at 11:38 PM, hemant <gethemant@gmail.com> wrote:
> 
> > Hi,
> >
> > I am not sure, whats causing this with latest gem 1.3.3, but I am
> > unable to build scala projects.
> >
> > I created a fresh scala project with following code layout
> >
> > src/main/scala/com/msf/hello/Hello.scala   <-- contains main object
> > src/test/scala/com/msf/hello <-- currently empty
> >
> > and my buildfile looks like this:
> >
> > require "rubygems"
> >
> > # Generated by Buildr 1.3.3, change to your liking
> > # Version number for this release
> > VERSION_NUMBER = "1.0.0"
> > # Group identifier for your projects
> > GROUP = "hello"
> > COPYRIGHT = "GPL"
> >
> > # Specify Maven 2.0 remote repositories here, like this:
> > repositories.remote << "http://www.ibiblio.org/maven2/"
> >
> > desc "The Hello project"
> > define "hello" do
> >  project.version = VERSION_NUMBER
> >  project.group = GROUP
> >  manifest["Implementation-Vendor"] = COPYRIGHT
> >  package :jar
> > end
> >
> > "buildr compile" doesn't compile the project. Output with "--trace"
> > option looks like this:
> >
> > (in /home/hemant/tmp/hello, development)
> > ** Invoke buildr:initialize (first_time)
> > ** Execute buildr:initialize
> > ** Invoke hello (first_time)
> > ** Execute hello
> > ** Invoke
> > /home/hemant/.m2/repository/org/apache/ant/ant/1.7.1/ant-1.7.1.jar
> > (first_time, not_needed)
> > ** Invoke
> > /home/hemant/.m2/repository/org/apache/ant/ant-launcher/1.7.1/ant-launcher-1.7.1.jar
> > (first_time, not_needed)
> > ** Invoke
> > /home/hemant/.m2/repository/org/apache/ant/ant-trax/1.7.1/ant-trax-1.7.1.jar
> > (first_time, not_needed)
> > ** Invoke /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/java
> > (first_time, not_needed)
> > ** Invoke /opt/java/lib/tools.jar (first_time, not_needed)
> > ** Invoke hello
> > ** Invoke compile (first_time)
> > ** Execute compile
> > Compiling hello
> > ** Invoke hello:compile (first_time, not_needed)
> > ** Invoke hello:resources (first_time)
> > ** Execute hello:resources
> > [Completed] Your build has completed: /home/hemant/tmp/hello
> > buildr compile
> >
> > Am I missing here something?
> >
> >
> > --
> > Let them talk of their oriental summer climes of everlasting
> > conservatories; give me the privilege of making my own summer with my
> > own coals.
> >
> > http://gnufied.org
> >