Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: buildr-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of antoine.toulme@gmail.com
 designates 209.85.217.26 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:sender:to:subject:in-reply-to
         :mime-version:content-type:references:x-google-sender-auth;
        b=Kg4udfeR7sh7cmb+8+FdVUmvr0C5aZ2m8C4VZCxBRp/OqjNWE1WICtsfrsGa8VOmOh
         vUdIPbVHZE1HK8WA9EI+BoOW0W7hdlsrcY6s4EJ/GQnCL4c+a+jpRXKZxPQb5JseSwZd
         26q4UhnUJIwPq/az+r9ubCCkBN2LLyVbqWoM4=
Message-ID: <f97124910812110821m50b9dd3ak1207dc0f2af55a27@mail.gmail.com>
Date: Thu, 11 Dec 2008 17:21:26 +0100
From: "Antoine Toulme" <antoine@lunar-ocean.com>
Reply-To: antoine@lunar-ocean.com
Sender: antoine.toulme@gmail.com
To: buildr-user@incubator.apache.org
Subject: Re: Announcement : Creation of buildr4eclipse
In-Reply-To: <4941381D.1000601@tikalk.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10282_19826918.1229012486708"
References: <f97124910812110308w2710ceabl2fc63c3af1224270@mail.gmail.com>
	 <4941381D.1000601@tikalk.com>

------=_Part_10282_19826918.1229012486708
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Right now I compile my plugins with Maven. I also compile with a ruby
wrapper that calls a buckminster build that triggers an ant task that runs
the JDT compiler for another project.
Compiling java code works, but traditional compilers don't apply rules
derived from the manifest of the OSGi bundle you build.OGSi bundles, for
example, need to specify the packages they export. They also can reexport a
dependency. They can make a dependency optional.
OSGi bundles have their own versioning scheme for dependencies, which if at
first may look like Maven, is not matching perfectly with it at times.

Our goal is really minimal, we want to replace the default javac compiler by
the JDT compiler.
Later on, we hope to be able to use the dependencies defined in the manifest
to make it easier for plugin devs. I'm for taking baby steps on this.

We established a goals page on google code if you want more info:
http://code.google.com/p/buildr4eclipse/wiki/Goals

Thanks,

Antoine

On Thu, Dec 11, 2008 at 4:56 PM, Ittay Dror <ittayd@tikalk.com> wrote:

> i'm compiling osgi bundles that are created as eclipse plugins (that is,
> eclipse manages the manifest file).
>
>
> actually, i didn't find it that difficult to do, what are the main
> difficulties you see?
>
>
> ittay
>
>
> Antoine Toulme wrote:
>
>  Hi all,
>> Ketan <http://ketan.padegaonkar.name/> opened the way a month ago. I
>> contacted him again today, and we decided to join forces to build an
>> extension for buildr to compile Eclipse plugins.
>>
>> We are opening a new project
>> Buildr4eclipse<http://code.google.com/p/buildr4eclipse/> ,
>> that will take place on Google
>> Code<http://code.google.com/p/buildr4eclipse/>and
>> Github <http://github.com/ketan/buildr4eclipse/tree>.
>>
>> We will try to use the extension mechanism Buildr provides as much as
>> possible. We will probably have questions, we thank you in advance for
>> bearing with us on this.
>>
>> We welcome any help, if you have some time and would like to contribute,
>> we
>> appreciate an extra hand for sure.
>>
>> Thanks for reading,
>>
>> Antoine
>>
>> for the full announcement, look up
>> http://www.lunar-ocean.com/building-eclipse-plugins-with-buildr.
>>
>>
>>
>
> --
> Ittay Dror <ittayd@tikalk.com>
> Tikal <http://www.tikalk.com>
> Tikal Project <http://tikal.sourceforge.net>
>
>


-- 
http://www.lunar-ocean.com/blog

------=_Part_10282_19826918.1229012486708--