Indeed: http://www.eclipse.org/modeling/emft/b3/
I would very much like to script my builds in b3 language instead of mucking around with xml or whatnot. (see an example of b3 script at http://dev.eclipse.org/svnroot/modeling/org.eclipse.emft.b3/trunk/org.eclipse.b3.beelang.tests/src-b3/examples/demoSallad.b3) Unfortunately, beelang is still just a syntax and a model with - as far as I am aware, no concrete build engine implementation behind it... On 24 nov, 16:15, phil swenson <[email protected]> wrote: > +1 on gradle. > > But the real key is to move past the broken notion that builds should > be written in XML. What a terrible idea! > > > > > > > > On Tue, Nov 23, 2010 at 5:08 AM, Paul King <[email protected]> wrote: > > Also consider Gradle. I find it very useful for Java, Groovy or Scala > > projects. It is super smart about compiling just what is needed but from > > what I know takes a different approach to sbt. > > Cheers, Paul. > > > On Tue, Nov 23, 2010 at 8:29 PM, Kevin Wright <[email protected]> > > wrote: > > >> On 23 November 2010 02:34, JamesJ <[email protected]> wrote: > > >>> I would just play with it and see if you like it. It will build Java, > >>> it just requires a bit of Scala as the configuration language (no > >>> worse than property files or XML, given a few examples.) Like I said, > >>> I'm very new to SBT, but it seems that you could get pretty far > >>> without having to learn much with some cut/paste/modify. > > >>> One of the complaints that I have read is that it downloads lots of > >>> stuff initially, including Scala 2.7, but that didn't really bother me > >>> at all. > > >> In its most basic form, you can think of SBT as a Scala DSL wrapper around > >> Ivy (which it uses internally), plus Maven standard directory > >> layout. It's able to resolve dependencies from a Maven repo, as well as > >> your local ~/.ivy and ~/.m2 repositories. > >> So you don't need to learn the entirety of Scala, just the subset used in > >> the DSL (in that regard, its not much different to polyglot Maven with a > >> Groovy POM). > >> On top of that, you also get all the benefits of continuous compilation, > >> continuous testing, and the Scala REPL - which is still very usable against > >> a pure Java codebase. > > >> -- > >> Kevin Wright > > >> mail / gtalk / msn : [email protected] > >> pulse / skype: kev.lee.wright > >> twitter: @thecoda > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "The Java Posse" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group at > >>http://groups.google.com/group/javaposse?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "The Java Posse" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
