Thanks for your interest Alex. Until we go 1.0, things will remain a bit quirky.
Only the compiler is tested in this release, so we only announced it. Additional methods present in the tasks.rb and lib.rb files are taken from Ketan's SWTBot project. We will build a spec for them ASAP. I will also add some methods from the BPMN modeler build scripts as well: http://tinyurl.com/77793f Ketan outlined that we are working on auto-resolving dependencies for plugin artifacts. We will use the Manifest gem <http://manifest.rubyforge.org/> to read the manifest. Hopefully we will have more to share on this soon. Thanks, Antoine On Mon, Jan 5, 2009 at 5:55 AM, Alex Boisvert <[email protected]> wrote: > That's exactly what I'm talking about :) I'm sure there's plenty of > hidden features in there... if they are not documented then who's going to > know? > > alex > > On Sun, Jan 4, 2009 at 8:34 PM, Ketan Padegaonkar < > [email protected]> wrote: > > > Hi Alex, > > > > The compiler that has > > been written is a dropin > > replacement for java. > > > > PDEc will allow for auto > > discovery of class path > > by figuring out the plugin > > dependencies by > > looking at the manifest. > > > > What is also special > > about it is that the > > compiler can look at jars > > and folders inside jars for > > the class path. > > > > -- Ketan > > > > > > > > On 1/5/09, Alex > > Boisvert <boisvert > > @intalio.com> wrote: > > > Hi Antoine, > > > > > > Nice plugin! It would > > be nice to document > > what the plugin does in > > addition > > > to hooking PDEc as a > > compiler. Looking briefly > > at the code I can see it > > > that is sets manifest > > information and such. It > > would be nice to have > > this > > > information readily > > available in the doc. > > > > > > (I looked at the specs > > but they didn't > > distinguish between > > standard java > > > compiler and what the > > plugin adds) > > > > > > alex > > > > > > On Sun, Jan 4, 2009 at > > 3:40 PM, Antoine > > Toulme > > > <anto...@lunar- > > ocean.com>wrote: > > > > > >> Cross-posting from > > the buildr4eclipse google > > group: click > > >> here< > > >> http:// > > groups.google.com/ > > group/buildr4eclipse/ > > browse_thread/thread/ > > d5a271173b66c78f< > http://groups.google.com/group/buildr4eclipse/browse_thread/thread/d5a271173b66c78f > > > > >> >for > > >> the original > > announcement. > > >> > > >> I just released > > Buildr4Eclipse 0.0.1. > > >> > > >> This is our very first > > release. I tested it by > > running the compiler > > >> against > > >> an Eclipse project. I > > was able to verify that > > the JDT compiler was > > used to > > >> compile the project, > > and everything seems to > > be working well. > > >> > > >> I also uploaded a > > basic website here: > > http:// > > buildr4eclipse.rubyforge. > > org > > >> > > >> This is just a start, > > the release is up for > > testing, your comments > > and > > >> your > > >> appreciations are > > welcome! > > >> > > >> Thanks, > > >> > > >> Antoine > > >> > > >> -- > > >> http://www.lunar- > > ocean.com/blog > > >> > > > > > > > > > -- > > Ketan Padegaonkar > > I blog... therefore I am... > > http:// > > ketan.padegaonkar.name > > http://swtbot.org/ - a > > functional testing tool for > > SWT/Eclipse > > > -- http://www.lunar-ocean.com/blog
