+1 for "Build Like You Code". Simple, to the point, and not overdone. Daniel On Dec 8, 2009, at 4:34 PM, "Alex Boisvert" <alex.boisvert@gmail.com> wrote: > :) > > One thing I like about Buildr is that it can turn a normally boring > job into > a creative task, just like programming. So I was thinking along > the lines > of "Build like you Code"... Maybe other people relate to that and > can > think of something better that expresses this feeling. > > alex > > On Tue, Dec 8, 2009 at 2:23 PM, Tal Rotbart <redbeard@gmail.com> > wrote: > >> I'd like to suggest a slight modification to the original "Ready, >> Set, >> Build" -- "Ready, Set, Buildr!" >> >> Or in jest... >> "Buildr, not your Dad's ant" >> >> Cheers, >> Tal >> >> On Wed, Dec 9, 2009 at 9:17 AM, Alex Boisvert <alex.boisvert@gmail.com >> > >> wrote: >>> Thanks to everybody who sent in their taglines. >>> >>> Anyone wants to suggest more taglines, you have another 48 hours >>> to do >> so. >>> >>> After that, we'll start voting. >>> >>> alex >>> >>> >>> On Mon, Nov 9, 2009 at 11:58 AM, Shane Witbeck <shane@digitalsanctum.com >>> wrote: >>> >>>> - Buildr, elegant builds don't have to be hard >>>> - Buildr, for a concise, fast and flexible build >>>> >>>> -Shane >>>> >>>> >>>> >>>> On Fri, Nov 6, 2009 at 2:07 PM, Assaf Arkin <assaf@labnotes.org> >>>> wrote: >>>>> On Fri, Nov 6, 2009 at 1:24 AM, Jean-Philippe Caruana < >>>>> jeanphilippe1.caruana@orange-ftgroup.com> wrote: >>>>> >>>>>> what about : >>>>>> >>>>>> - buildr, et voilà ! >>>>>> - shrink your build >>>>>> - buildr, a fat free build >>>>>> - lean builds >>>>>> >>>>> >>>>> I like lean builds. It stands for "having no superfluous fat" >>>> (dictionary), >>>>> but also fits very well with the idea of lean practices: >>>>> creating more >>>> value >>>>> with less work, or less waste, if you will. >>>>> >>>>> http://en.wikipedia.org/wiki/Lean_manufacturing >>>>> >>>>> Assaf >>>>> >>>>> >>>>>> >>>>>> >>>>>> we keep on brainstorming here... we'll let you know ! >>>>>> >>>>>> -- >>>>>> Jean-Philippe Caruana >>>>>> ******************************** >>>>>> Ce message et toutes les pieces jointes (ci-apres le "message") >>>>>> sont >>>>>> confidentiels et etablis a l'attention exclusive de ses >> destinataires. >>>>>> Toute utilisation ou diffusion non autorisee est interdite. >>>>>> Tout message electronique est susceptible d'alteration. CVF >>>>>> decline >>>>>> toute responsabilite au titre de ce message s'il a ete altere, >> deforme >>>>>> ou falsifie. >>>>>> Si vous n'etes pas destinataire de ce message, merci de le >>>>>> detruire >>>>>> immediatement et d'avertir l'expediteur. >>>>>> ********************************* >>>>>> This message and any attachments (the "message") are >>>>>> confidential and >>>>>> intended solely for the addressees. Any unauthorised use or >>>>>> dissemination is prohibited. >>>>>> Messages are susceptible to alteration. CVF shall not be liable >>>>>> for >> the >>>>>> message if altered, changed or falsified. >>>>>> If you are not the intended addressee of this message, please >>>>>> cancel >> it >>>>>> immediately and inform the sender.. >>>>>> ******************************** >>>>>> >>>>> >>>> >>> >>
1. build.with :buildr 2. buildr - build easy 3. build, don't stress - buildr All but the first sound like slogans from 80s local television commercials, so try to imagine them read with Mr. T's voice... :p Cheers, Tal On Wed, Dec 9, 2009 at 9:34 AM, Alex Boisvert <alex.boisvert@gmail.com> wrote: > :) > > One thing I like about Buildr is that it can turn a normally boring job into > a creative task, just like programming.  So I was thinking along the lines > of "Build like you Code"...  Maybe other people relate to that and can > think of something better that expresses this feeling. > > alex > > On Tue, Dec 8, 2009 at 2:23 PM, Tal Rotbart <redbeard@gmail.com> wrote: > >> I'd like to suggest a slight modification to the original "Ready, Set, >> Build" -- "Ready, Set, Buildr!" >> >> Or in jest... >> "Buildr, not your Dad's ant" >> >> Cheers, >> Tal >> >> On Wed, Dec 9, 2009 at 9:17 AM, Alex Boisvert <alex.boisvert@gmail.com> >> wrote: >> > Thanks to everybody who sent in their taglines. >> > >> > Anyone wants to suggest more taglines, you have another 48 hours to do >> so. >> > >> > After that, we'll start voting. >> > >> > alex >> > >> > >> > On Mon, Nov 9, 2009 at 11:58 AM, Shane Witbeck <shane@digitalsanctum.com >> >wrote: >> > >> >> - Buildr, elegant builds don't have to be hard >> >> - Buildr, for a concise, fast and flexible build >> >> >> >> -Shane >> >> >> >> >> >> >> >> On Fri, Nov 6, 2009 at 2:07 PM, Assaf Arkin <assaf@labnotes.org> wrote: >> >> > On Fri, Nov 6, 2009 at 1:24 AM, Jean-Philippe Caruana < >> >> > jeanphilippe1.caruana@orange-ftgroup.com> wrote: >> >> > >> >> >> what about : >> >> >> >> >> >> - buildr, et voilà ! >> >> >> - shrink your build >> >> >> - buildr, a fat free build >> >> >> - lean builds >> >> >> >> >> > >> >> > I like lean builds. It stands for "having no superfluous fat" >> >> (dictionary), >> >> > but also fits very well with the idea of lean practices: creating more >> >> value >> >> > with less work, or less waste, if you will. >> >> > >> >> > http://en.wikipedia.org/wiki/Lean_manufacturing >> >> > >> >> > Assaf >> >> > >> >> > >> >> >> >> >> >> >> >> >> we keep on brainstorming here... we'll let you know ! >> >> >> >> >> >> -- >> >> >> Jean-Philippe Caruana >> >> >> ******************************** >> >> >> Ce message et toutes les pieces jointes (ci-apres le "message") sont >> >> >> confidentiels et etablis a l'attention exclusive de ses >> destinataires. >> >> >> Toute utilisation ou diffusion non autorisee est interdite. >> >> >> Tout message electronique est susceptible d'alteration. CVF decline >> >> >> toute responsabilite au titre de ce message s'il a ete altere, >> deforme >> >> >> ou falsifie. >> >> >> Si vous n'etes pas destinataire de ce message, merci de le detruire >> >> >> immediatement et d'avertir l'expediteur. >> >> >> ********************************* >> >> >> This message and any attachments (the "message") are confidential and >> >> >> intended solely for the addressees. Any unauthorised use or >> >> >> dissemination is prohibited. >> >> >> Messages are susceptible to alteration. CVF shall not be liable for >> the >> >> >> message if altered, changed or falsified. >> >> >> If you are not the intended addressee of this message, please cancel >> it >> >> >> immediately and inform the sender.. >> >> >> ******************************** >> >> >> >> >> > >> >> >> > >> >
:) One thing I like about Buildr is that it can turn a normally boring job into a creative task, just like programming. So I was thinking along the lines of "Build like you Code"... Maybe other people relate to that and can think of something better that expresses this feeling. alex On Tue, Dec 8, 2009 at 2:23 PM, Tal Rotbart <redbeard@gmail.com> wrote: > I'd like to suggest a slight modification to the original "Ready, Set, > Build" -- "Ready, Set, Buildr!" > > Or in jest... > "Buildr, not your Dad's ant" > > Cheers, > Tal > > On Wed, Dec 9, 2009 at 9:17 AM, Alex Boisvert <alex.boisvert@gmail.com> > wrote: > > Thanks to everybody who sent in their taglines. > > > > Anyone wants to suggest more taglines, you have another 48 hours to do > so. > > > > After that, we'll start voting. > > > > alex > > > > > > On Mon, Nov 9, 2009 at 11:58 AM, Shane Witbeck <shane@digitalsanctum.com > >wrote: > > > >> - Buildr, elegant builds don't have to be hard > >> - Buildr, for a concise, fast and flexible build > >> > >> -Shane > >> > >> > >> > >> On Fri, Nov 6, 2009 at 2:07 PM, Assaf Arkin <assaf@labnotes.org> wrote: > >> > On Fri, Nov 6, 2009 at 1:24 AM, Jean-Philippe Caruana < > >> > jeanphilippe1.caruana@orange-ftgroup.com> wrote: > >> > > >> >> what about : > >> >> > >> >> - buildr, et voilà ! > >> >> - shrink your build > >> >> - buildr, a fat free build > >> >> - lean builds > >> >> > >> > > >> > I like lean builds. It stands for "having no superfluous fat" > >> (dictionary), > >> > but also fits very well with the idea of lean practices: creating more > >> value > >> > with less work, or less waste, if you will. > >> > > >> > http://en.wikipedia.org/wiki/Lean_manufacturing > >> > > >> > Assaf > >> > > >> > > >> >> > >> >> > >> >> we keep on brainstorming here... we'll let you know ! > >> >> > >> >> -- > >> >> Jean-Philippe Caruana > >> >> ******************************** > >> >> Ce message et toutes les pieces jointes (ci-apres le "message") sont > >> >> confidentiels et etablis a l'attention exclusive de ses > destinataires. > >> >> Toute utilisation ou diffusion non autorisee est interdite. > >> >> Tout message electronique est susceptible d'alteration. CVF decline > >> >> toute responsabilite au titre de ce message s'il a ete altere, > deforme > >> >> ou falsifie. > >> >> Si vous n'etes pas destinataire de ce message, merci de le detruire > >> >> immediatement et d'avertir l'expediteur. > >> >> ********************************* > >> >> This message and any attachments (the "message") are confidential and > >> >> intended solely for the addressees. Any unauthorised use or > >> >> dissemination is prohibited. > >> >> Messages are susceptible to alteration. CVF shall not be liable for > the > >> >> message if altered, changed or falsified. > >> >> If you are not the intended addressee of this message, please cancel > it > >> >> immediately and inform the sender.. > >> >> ******************************** > >> >> > >> > > >> > > >
I'd like to suggest a slight modification to the original "Ready, Set, Build" -- "Ready, Set, Buildr!" Or in jest... "Buildr, not your Dad's ant" Cheers, Tal On Wed, Dec 9, 2009 at 9:17 AM, Alex Boisvert <alex.boisvert@gmail.com> wrote: > Thanks to everybody who sent in their taglines. > > Anyone wants to suggest more taglines, you have another 48 hours to do so. > > After that, we'll start voting. > > alex > > > On Mon, Nov 9, 2009 at 11:58 AM, Shane Witbeck <shane@digitalsanctum.com>wrote: > >> - Buildr, elegant builds don't have to be hard >> - Buildr, for a concise, fast and flexible build >> >> -Shane >> >> >> >> On Fri, Nov 6, 2009 at 2:07 PM, Assaf Arkin <assaf@labnotes.org> wrote: >> > On Fri, Nov 6, 2009 at 1:24 AM, Jean-Philippe Caruana < >> > jeanphilippe1.caruana@orange-ftgroup.com> wrote: >> > >> >> what about : >> >> >> >> - buildr, et voilà ! >> >> - shrink your build >> >> - buildr, a fat free build >> >> - lean builds >> >> >> > >> > I like lean builds. It stands for "having no superfluous fat" >> (dictionary), >> > but also fits very well with the idea of lean practices: creating more >> value >> > with less work, or less waste, if you will. >> > >> > http://en.wikipedia.org/wiki/Lean_manufacturing >> > >> > Assaf >> > >> > >> >> >> >> >> >> we keep on brainstorming here... we'll let you know ! >> >> >> >> -- >> >> Jean-Philippe Caruana >> >> ******************************** >> >> Ce message et toutes les pieces jointes (ci-apres le "message") sont >> >> confidentiels et etablis a l'attention exclusive de ses destinataires. >> >> Toute utilisation ou diffusion non autorisee est interdite. >> >> Tout message electronique est susceptible d'alteration. CVF decline >> >> toute responsabilite au titre de ce message s'il a ete altere, deforme >> >> ou falsifie. >> >> Si vous n'etes pas destinataire de ce message, merci de le detruire >> >> immediatement et d'avertir l'expediteur. >> >> ********************************* >> >> This message and any attachments (the "message") are confidential and >> >> intended solely for the addressees. Any unauthorised use or >> >> dissemination is prohibited. >> >> Messages are susceptible to alteration. CVF shall not be liable for the >> >> message if altered, changed or falsified. >> >> If you are not the intended addressee of this message, please cancel it >> >> immediately and inform the sender.. >> >> ******************************** >> >> >> > >> >
Thanks to everybody who sent in their taglines. Anyone wants to suggest more taglines, you have another 48 hours to do so. After that, we'll start voting. alex On Mon, Nov 9, 2009 at 11:58 AM, Shane Witbeck <shane@digitalsanctum.com>wrote: > - Buildr, elegant builds don't have to be hard > - Buildr, for a concise, fast and flexible build > > -Shane > > > > On Fri, Nov 6, 2009 at 2:07 PM, Assaf Arkin <assaf@labnotes.org> wrote: > > On Fri, Nov 6, 2009 at 1:24 AM, Jean-Philippe Caruana < > > jeanphilippe1.caruana@orange-ftgroup.com> wrote: > > > >> what about : > >> > >> - buildr, et voilà ! > >> - shrink your build > >> - buildr, a fat free build > >> - lean builds > >> > > > > I like lean builds. It stands for "having no superfluous fat" > (dictionary), > > but also fits very well with the idea of lean practices: creating more > value > > with less work, or less waste, if you will. > > > > http://en.wikipedia.org/wiki/Lean_manufacturing > > > > Assaf > > > > > >> > >> > >> we keep on brainstorming here... we'll let you know ! > >> > >> -- > >> Jean-Philippe Caruana > >> ******************************** > >> Ce message et toutes les pieces jointes (ci-apres le "message") sont > >> confidentiels et etablis a l'attention exclusive de ses destinataires. > >> Toute utilisation ou diffusion non autorisee est interdite. > >> Tout message electronique est susceptible d'alteration. CVF decline > >> toute responsabilite au titre de ce message s'il a ete altere, deforme > >> ou falsifie. > >> Si vous n'etes pas destinataire de ce message, merci de le detruire > >> immediatement et d'avertir l'expediteur. > >> ********************************* > >> This message and any attachments (the "message") are confidential and > >> intended solely for the addressees. Any unauthorised use or > >> dissemination is prohibited. > >> Messages are susceptible to alteration. CVF shall not be liable for the > >> message if altered, changed or falsified. > >> If you are not the intended addressee of this message, please cancel it > >> immediately and inform the sender.. > >> ******************************** > >> > > >
Can somebody explain the rationale behind this specification?
describe Buildr::TestTask do
...
it 'should not use the test compile dependencies' do
define('foo') { test.compile.using(:javac).with 'group:id:jar:1.0' }
project('foo').test.dependencies.should_not
include(artifact('group:id:jar:1.0'))
end
...
end
One of my recent
commits<http://github.com/apache/buildr/commit/44a12c63cf1ce390e89db9921fe5ea9e960ce054>breaks
it. I think it's wrong but maybe I'm missing something.
alex
On Sun, Nov 22, 2009 at 4:03 PM, Assaf Arkin <assaf@labnotes.org> wrote: > On Sun, Nov 22, 2009 at 8:30 AM, Alex Boisvert <alex.boisvert@gmail.com > >wrote: > > > Does anybody want to update our release scripts to update the gemcutter > > index? I'm not too familiar with gemcutter yet. It is only a matter of > > adding "gem push" ? > > > > Yep. Simpler and faster. Only problem is transferring ownership from > rubyforge to gemcutter. When I run gem migrate it hangs, does it work for > you? > Doesn't work either but for a different reason. boisvert@smudge:~$ gem migrate buildr Starting migration of buildr from RubyForge... A migration token has been created. Uploading the migration token to buildr.rubyforge.org. Successfully uploaded your token. Asking Gemcutter to verify the upload... Gemcutter is still looking for your migration token. boisvert@smudge:~$ > > Also, this just in: https://www.javagems.org/ > > "Created because we'd rather not use Maven. JavaGems provides gem hosting > and gem creation for the JVM-based-language community. Instantly > publish your gems and install them. Use the API to interact and find out > more information about available gems." > Revolutions never go backwards ;) alex
On Sun, Nov 22, 2009 at 8:30 AM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > Does anybody want to update our release scripts to update the gemcutter > index? I'm not too familiar with gemcutter yet. It is only a matter of > adding "gem push" ? > Yep. Simpler and faster. Only problem is transferring ownership from rubyforge to gemcutter. When I run gem migrate it hangs, does it work for you? Also, this just in: https://www.javagems.org/ "Created because we'd rather not use Maven. JavaGems provides gem hosting and gem creation for the JVM-based-language community. Instantly publish your gems and install them. Use the API to interact and find out more information about available gems." Assaf > alex > > ---------- Forwarded message ---------- > From: <noreply@rubyforge.org> > Date: Sat, Nov 21, 2009 at 7:17 PM > Subject: [RubyForge] Gem index has been shut down > To: alex.boisvert@gmail.com > > > Hello - > > You're receiving this email because you're a RubyForge project admin and a > recent change probably affects you. A few days ago we repointed > gems.rubyforge.org to the gemcutter.org box. This means that Nick > Quaranto's excellent gemcutter app is now indexing and serving all the gems > - so rather than having two gem indexes, we now have one. As a consequence > of this, when you release files to RubyForge you will probably also want to > do a "gem push" to get them onto gemcutter and into the main gem index. > > Note that you can continue to release gems (and other files) at RubyForge; > it's just that gems won't automatically make it into the main gem index. > > Yours, > > The RubyForge support team > http://rubyforge.org/projects/support/ >
Does anybody want to update our release scripts to update the gemcutter index? I'm not too familiar with gemcutter yet. It is only a matter of adding "gem push" ? alex ---------- Forwarded message ---------- From: <noreply@rubyforge.org> Date: Sat, Nov 21, 2009 at 7:17 PM Subject: [RubyForge] Gem index has been shut down To: alex.boisvert@gmail.com Hello - You're receiving this email because you're a RubyForge project admin and a recent change probably affects you. A few days ago we repointed gems.rubyforge.org to the gemcutter.org box. This means that Nick Quaranto's excellent gemcutter app is now indexing and serving all the gems - so rather than having two gem indexes, we now have one. As a consequence of this, when you release files to RubyForge you will probably also want to do a "gem push" to get them onto gemcutter and into the main gem index. Note that you can continue to release gems (and other files) at RubyForge; it's just that gems won't automatically make it into the main gem index. Yours, The RubyForge support team http://rubyforge.org/projects/support/
On Mon, Nov 16, 2009 at 7:21 AM, Daniel Spiewak <djspiewak@gmail.com> wrote: > I forgot about that. Our JRuby code does require jruby-ffi. Is it > possible > to bundle the appropriate native libs within a JRuby distribution? > Actually, the libs are already there. boisvert@boog:/opt/boisvert/buildr-1.3.5-jruby-1.4.0/lib/native$ find . | grep ffi ./x86_64-FreeBSD/libjffi-0.6.so ./i386-SunOS/libjffi-0.6.so ./i386-Windows/jffi-0.6.dll ./i386-Linux/libjffi-0.6.so ./s390x-Linux/libjffi-0.6.so ./darwin/libjffi-0.6.jnilib ./x86_64-SunOS/libjffi-0.6.so ./x86_64-Linux/libjffi-0.6.so ./i386-FreeBSD/libjffi-0.6.so ./sparc-SunOS/libjffi-0.6.so ./sparcv9-SunOS/libjffi-0.6.so I can't make sense of the error message "Can't load AMD 64-bit .so on a AMD 64-bit platform", though. Another thing to consider is that JRuby does have a jar-complete > distribution which is a little easier to manage. We would have to write a > separate buildr script just for that distribution, but it might be an > overall win in terms of manageability. > Yes, I think that's a logical second step. I'd like to get things polished with the current distro first. alex
I forgot about that. Our JRuby code does require jruby-ffi. Is it possible to bundle the appropriate native libs within a JRuby distribution? Another thing to consider is that JRuby does have a jar-complete distribution which is a little easier to manage. We would have to write a separate buildr script just for that distribution, but it might be an overall win in terms of manageability. Daniel On Mon, Nov 16, 2009 at 9:19 AM, Greg Lucas <greg.lucas@gmail.com> wrote: > Thanks for putting this together Alex. > > I've been trying it out with our continuous integration system in order to > build on multiple Linux machines. I'm getting: > > /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > `require': Could not load FFI Provider: FFI not available: > /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform > (LoadError) > > Has anyone seen this? > > -- > Greg Lucas >
Thanks for putting this together Alex. I've been trying it out with our continuous integration system in order to build on multiple Linux machines. I'm getting: /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require': Could not load FFI Provider: FFI not available: /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform (LoadError) Has anyone seen this? -- Greg Lucas
On Windows, it worked out of the box. On Mac I had to make the ./bin/buildr file executable. Thanks Alex! On Tue, Nov 10, 2009 at 4:16 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > Ok, updated the distro at > http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> > > Tested on both Linux and Windows. > > Let me know if you have any luck using it. > > alex > > On Tue, Nov 10, 2009 at 2:59 PM, Alex Boisvert <alex.boisvert@gmail.com > >wrote: > > > Thanks, yes, I think I have solutions for both platforms now. Just need > > to start VirtualBox to test the Windows part (which I should have done > the > > first time around). > > > > And I've now removed all other scripts (jirb, jrubyc, ...) so they don't > > conflict with other JRuby installs. > > > > alex > > > > > > > > On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <nicksieger@gmail.com> > wrote: > > > >> Alex, > >> > >> For Windows, you can piggy back off our new native launcher in JRuby 1.4 > >> by copying jruby.exe to buildr.exe. This effectively does the same as > "jruby > >> -S buildr" would do. The PATH issue is trickier admittedly. You really > need > >> the shebang in the "buildr" script to point to the copy of JRuby that > was > >> bundled, instead of "#!/usr/bin/env jruby". > >> > >> /Nick > >> > >> > >> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote: > >> > >> Hmmmm.... for a start there's two big issues with this distro. First, > if > >>> you already have jruby in your PATH, things get confused and basically > >>> nothing works. Second, there's no buildr.bat so it's pretty useless > for > >>> Windows users. (Unless they are willing to run "jruby -S buildr") > >>> > >>> I'll do another take later. Thanks for listening ;) > >>> > >>> alex > >>> > >>> > >>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert < > alex.boisvert@gmail.com > >>> >wrote: > >>> > >>> Hi, > >>>> > >>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby > >>>> 1.4.0 > >>>> and made it available at: > >>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> > <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> > >>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> > >>>> > >>>> > >>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of > >>>> everything I could that didn't affect functionality, such as > >>>> documentation > >>>> and Ruby 1.9 support. > >>>> > >>>> To use it, simply > >>>> 1) unzip in a directory, > >>>> 2) set your PATH to point to the "bin" directory, and > >>>> 3) run "buildr" as usual. > >>>> > >>>> Looking for feedback on how it works as a quick way to get > >>>> yourself/other > >>>> people started. If there's enough interest, it could become part of > our > >>>> supported distros. > >>>> > >>>> thanks, > >>>> alex > >>>> > >>>> > >>>> > >> > > >
Ok, updated the distro at http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip Tested on both Linux and Windows. Let me know if you have any luck using it. alex On Tue, Nov 10, 2009 at 2:59 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > Thanks, yes, I think I have solutions for both platforms now. Just need > to start VirtualBox to test the Windows part (which I should have done the > first time around). > > And I've now removed all other scripts (jirb, jrubyc, ...) so they don't > conflict with other JRuby installs. > > alex > > > > On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <nicksieger@gmail.com> wrote: > >> Alex, >> >> For Windows, you can piggy back off our new native launcher in JRuby 1.4 >> by copying jruby.exe to buildr.exe. This effectively does the same as "jruby >> -S buildr" would do. The PATH issue is trickier admittedly. You really need >> the shebang in the "buildr" script to point to the copy of JRuby that was >> bundled, instead of "#!/usr/bin/env jruby". >> >> /Nick >> >> >> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote: >> >> Hmmmm.... for a start there's two big issues with this distro. First, if >>> you already have jruby in your PATH, things get confused and basically >>> nothing works. Second, there's no buildr.bat so it's pretty useless for >>> Windows users. (Unless they are willing to run "jruby -S buildr") >>> >>> I'll do another take later. Thanks for listening ;) >>> >>> alex >>> >>> >>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com >>> >wrote: >>> >>> Hi, >>>> >>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby >>>> 1.4.0 >>>> and made it available at: >>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> >>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> >>>> >>>> >>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of >>>> everything I could that didn't affect functionality, such as >>>> documentation >>>> and Ruby 1.9 support. >>>> >>>> To use it, simply >>>> 1) unzip in a directory, >>>> 2) set your PATH to point to the "bin" directory, and >>>> 3) run "buildr" as usual. >>>> >>>> Looking for feedback on how it works as a quick way to get >>>> yourself/other >>>> people started. If there's enough interest, it could become part of our >>>> supported distros. >>>> >>>> thanks, >>>> alex >>>> >>>> >>>> >> >
Thanks, yes, I think I have solutions for both platforms now. Just need to start VirtualBox to test the Windows part (which I should have done the first time around). And I've now removed all other scripts (jirb, jrubyc, ...) so they don't conflict with other JRuby installs. alex On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <nicksieger@gmail.com> wrote: > Alex, > > For Windows, you can piggy back off our new native launcher in JRuby 1.4 by > copying jruby.exe to buildr.exe. This effectively does the same as "jruby -S > buildr" would do. The PATH issue is trickier admittedly. You really need the > shebang in the "buildr" script to point to the copy of JRuby that was > bundled, instead of "#!/usr/bin/env jruby". > > /Nick > > > On Nov 10, 2009, at 16:42 , Alex Boisvert wrote: > > Hmmmm.... for a start there's two big issues with this distro. First, if >> you already have jruby in your PATH, things get confused and basically >> nothing works. Second, there's no buildr.bat so it's pretty useless for >> Windows users. (Unless they are willing to run "jruby -S buildr") >> >> I'll do another take later. Thanks for listening ;) >> >> alex >> >> >> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com >> >wrote: >> >> Hi, >>> >>> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0 >>> and made it available at: >>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> >>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> >>> >>> >>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of >>> everything I could that didn't affect functionality, such as >>> documentation >>> and Ruby 1.9 support. >>> >>> To use it, simply >>> 1) unzip in a directory, >>> 2) set your PATH to point to the "bin" directory, and >>> 3) run "buildr" as usual. >>> >>> Looking for feedback on how it works as a quick way to get yourself/other >>> people started. If there's enough interest, it could become part of our >>> supported distros. >>> >>> thanks, >>> alex >>> >>> >>> >
Alex, For Windows, you can piggy back off our new native launcher in JRuby 1.4 by copying jruby.exe to buildr.exe. This effectively does the same as "jruby -S buildr" would do. The PATH issue is trickier admittedly. You really need the shebang in the "buildr" script to point to the copy of JRuby that was bundled, instead of "#!/usr/bin/env jruby". /Nick On Nov 10, 2009, at 16:42 , Alex Boisvert wrote: > Hmmmm.... for a start there's two big issues with this distro. > First, if > you already have jruby in your PATH, things get confused and basically > nothing works. Second, there's no buildr.bat so it's pretty useless > for > Windows users. (Unless they are willing to run "jruby -S buildr") > > I'll do another take later. Thanks for listening ;) > > alex > > > On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com > >wrote: > >> Hi, >> >> I've created an experimental distribution of Buildr 1.3.5 and JRuby >> 1.4.0 >> and made it available at: >> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip >> > >> >> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of >> everything I could that didn't affect functionality, such as >> documentation >> and Ruby 1.9 support. >> >> To use it, simply >> 1) unzip in a directory, >> 2) set your PATH to point to the "bin" directory, and >> 3) run "buildr" as usual. >> >> Looking for feedback on how it works as a quick way to get yourself/ >> other >> people started. If there's enough interest, it could become part >> of our >> supported distros. >> >> thanks, >> alex >> >>
Hmmmm.... for a start there's two big issues with this distro. First, if you already have jruby in your PATH, things get confused and basically nothing works. Second, there's no buildr.bat so it's pretty useless for Windows users. (Unless they are willing to run "jruby -S buildr") I'll do another take later. Thanks for listening ;) alex On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > Hi, > > I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0 > and made it available at: > http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip> > > The distro is 15M -- not too bad. I've trimmed the packaged JRuby of > everything I could that didn't affect functionality, such as documentation > and Ruby 1.9 support. > > To use it, simply > 1) unzip in a directory, > 2) set your PATH to point to the "bin" directory, and > 3) run "buildr" as usual. > > Looking for feedback on how it works as a quick way to get yourself/other > people started. If there's enough interest, it could become part of our > supported distros. > > thanks, > alex > >
Hi, I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0 and made it available at: http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip The distro is 15M -- not too bad. I've trimmed the packaged JRuby of everything I could that didn't affect functionality, such as documentation and Ruby 1.9 support. To use it, simply 1) unzip in a directory, 2) set your PATH to point to the "bin" directory, and 3) run "buildr" as usual. Looking for feedback on how it works as a quick way to get yourself/other people started. If there's enough interest, it could become part of our supported distros. thanks, alex
- Buildr, elegant builds don't have to be hard - Buildr, for a concise, fast and flexible build -Shane On Fri, Nov 6, 2009 at 2:07 PM, Assaf Arkin <assaf@labnotes.org> wrote: > On Fri, Nov 6, 2009 at 1:24 AM, Jean-Philippe Caruana < > jeanphilippe1.caruana@orange-ftgroup.com> wrote: > >> what about : >> >> - buildr, et voilà ! >> - shrink your build >> - buildr, a fat free build >> - lean builds >> > > I like lean builds. It stands for "having no superfluous fat" (dictionary), > but also fits very well with the idea of lean practices: creating more value > with less work, or less waste, if you will. > > http://en.wikipedia.org/wiki/Lean_manufacturing > > Assaf > > >> >> >> we keep on brainstorming here... we'll let you know ! >> >> -- >> Jean-Philippe Caruana >> ******************************** >> Ce message et toutes les pieces jointes (ci-apres le "message") sont >> confidentiels et etablis a l'attention exclusive de ses destinataires. >> Toute utilisation ou diffusion non autorisee est interdite. >> Tout message electronique est susceptible d'alteration. CVF decline >> toute responsabilite au titre de ce message s'il a ete altere, deforme >> ou falsifie. >> Si vous n'etes pas destinataire de ce message, merci de le detruire >> immediatement et d'avertir l'expediteur. >> ********************************* >> This message and any attachments (the "message") are confidential and >> intended solely for the addressees. Any unauthorised use or >> dissemination is prohibited. >> Messages are susceptible to alteration. CVF shall not be liable for the >> message if altered, changed or falsified. >> If you are not the intended addressee of this message, please cancel it >> immediately and inform the sender.. >> ******************************** >> >
Awesome. Assaf On Sun, Nov 8, 2009 at 8:09 AM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > Thanks :) Yes, it gives external extensions practically the same > opportunies as our core modules. > > alex > > On Sun, Nov 8, 2009 at 3:01 AM, lacton <lacton@users.sourceforge.net> > wrote: > > > Very impressive work, Alex. I feel the buildr extension mechanism, > > which was already very nice, has reached a new level. > > > > Lacton > > > > On Sun, Nov 8, 2009 at 2:34 AM, <boisvert@apache.org> wrote: > > > Author: boisvert > > > Date: Sun Nov 8 01:34:11 2009 > > > New Revision: 833791 > > > > > > URL: http://svn.apache.org/viewvc?rev=833791&view=rev > > > Log: > > > Project extensions (before/after_define) now support dependency > ordering > > similar to Rake > > > (e.g. before_define(:my_setup => :compile) > > >
Thanks :) Yes, it gives external extensions practically the same opportunies as our core modules. alex On Sun, Nov 8, 2009 at 3:01 AM, lacton <lacton@users.sourceforge.net> wrote: > Very impressive work, Alex. I feel the buildr extension mechanism, > which was already very nice, has reached a new level. > > Lacton > > On Sun, Nov 8, 2009 at 2:34 AM, <boisvert@apache.org> wrote: > > Author: boisvert > > Date: Sun Nov 8 01:34:11 2009 > > New Revision: 833791 > > > > URL: http://svn.apache.org/viewvc?rev=833791&view=rev > > Log: > > Project extensions (before/after_define) now support dependency ordering > similar to Rake > > (e.g. before_define(:my_setup => :compile) >
Very impressive work, Alex. I feel the buildr extension mechanism, which was already very nice, has reached a new level. Lacton On Sun, Nov 8, 2009 at 2:34 AM, <boisvert@apache.org> wrote: > Author: boisvert > Date: Sun Nov 8 01:34:11 2009 > New Revision: 833791 > > URL: http://svn.apache.org/viewvc?rev=833791&view=rev > Log: > Project extensions (before/after_define) now support dependency ordering similar to Rake > (e.g. before_define(:my_setup => :compile)
According to Bill Venners, ScalaTest will be updated soon.
(I was going to report the issue earlier today but somebody else beat me to
it)
Until we find a combination that works for all frameworks, my vote would be
to revert to Specs 1.6.
And one request: please run the specs when upgrading versions. The specs
were all broken before I picked them up today. It's worrying to work on
different area (unrelated code) without knowing if I inadvertently broke
other things.
thanks,
alex
On Sat, Nov 7, 2009 at 10:05 PM, Daniel Spiewak <djspiewak@gmail.com> wrote:
> We need to make a decision here. ScalaCheck 1.5 is incompatible with Specs
> 1.6.1. We could stick with Specs 1.6, but there are a lot of very useful
> fixes and improvements in 1.6.1, including several which I require for my
> projects.
>
> I guess ideally ScalaTest would update to support ScalaCheck 1.6, but I
> don't know when that is going to happen.
>
> Daniel
>
> On Nov 7, 2009, at 11:55 PM, "boisvert@apache.org" <boisvert@apache.org>
> wrote:
>
> Author: boisvert
>> Date: Sun Nov 8 05:54:50 2009
>> New Revision: 833834
>>
>> URL: http://svn.apache.org/viewvc?rev=833834&view=rev
>> Log:
>> Fix Scalatest specs (1.0 API compatibility); revert to Scalacheck 1.5
>> since 1.6 is incompatible with Scalatest 1.0
>>
>> Modified:
>> buildr/trunk/lib/buildr/scala/tests.rb
>> buildr/trunk/spec/scala/tests_spec.rb
>>
>> Modified: buildr/trunk/lib/buildr/scala/tests.rb
>> URL:
>> http://svn.apache.org/viewvc/buildr/trunk/lib/buildr/scala/tests.rb?rev=833834&r1=833833&r2=833834&view=diff
>>
>> ==============================================================================
>> --- buildr/trunk/lib/buildr/scala/tests.rb (original)
>> +++ buildr/trunk/lib/buildr/scala/tests.rb Sun Nov 8 05:54:50 2009
>> @@ -23,7 +23,7 @@
>> module Buildr::Scala
>> # Scala::Check is available when using Scala::Test or Scala::Specs
>> module Check
>> - VERSION = '1.6'
>> + VERSION = '1.5'
>>
>> class << self
>> def version
>> @@ -112,7 +112,7 @@
>> # TODO: This should be name=>value pairs!
>> #ant.includes group_includes.join(" ") if group_includes
>> #ant.excludes group_excludes.join(" ") if group_excludes
>> - (options[:properties] || []).each { |name, value|
>> ant.property :name=>name, :value=>value }
>> + (options[:properties] || []).each { |name, value| ant.config
>> :name=>name, :value=>value }
>> end
>> end
>>
>> @@ -127,7 +127,7 @@
>> File.open(reportFile, "r") do |input|
>> while (line = input.gets) do
>> failed = (line =~ /(TESTS? FAILED -)|(RUN STOPPED)|(RUN
>> ABORTED)/) unless failed
>> - completed |= (line =~ /Run completed\./)
>> + completed |= (line =~ /Run completed/)
>> break if (failed)
>> end
>> end
>>
>> Modified: buildr/trunk/spec/scala/tests_spec.rb
>> URL:
>> http://svn.apache.org/viewvc/buildr/trunk/spec/scala/tests_spec.rb?rev=833834&r1=833833&r2=833834&view=diff
>>
>> ==============================================================================
>> --- buildr/trunk/spec/scala/tests_spec.rb (original)
>> +++ buildr/trunk/spec/scala/tests_spec.rb Sun Nov 8 05:54:50 2009
>> @@ -113,7 +113,7 @@
>> val sum = 1 + 1
>> assert(sum === 2)
>> }
>> -
>> +
>> class InnerSuite extends FunSuite {
>> test("addition") {
>> val sum = 1 + 1
>> @@ -180,15 +180,16 @@
>> write 'src/test/scala/PropertyTestSuite.scala', <<-SCALA
>> import org.scalatest._
>> class PropertyTestSuite extends FunSuite {
>> - var properties = Map[String, Any]()
>> + var configMap = Map[String, Any]()
>> test("testProperty") {
>> - assert(properties("name") === "value")
>> + assert(configMap("name") === "value")
>> }
>> -
>> +
>> protected override def runTests(testName: Option[String], reporter:
>> Reporter, stopper: Stopper,
>> - includes: Set[String], excludes:
>> Set[String], properties: Map[String, Any]) {
>> - this.properties = properties;
>> - super.runTests(testName, reporter, stopper, includes, excludes,
>> properties)
>> + filter: Filter, configMap:
>> Map[String, Any],
>> + distributor: Option[Distributor],
>> tracker: Tracker) {
>> + this.configMap = configMap
>> + super.runTests(testName, reporter, stopper, filter, configMap,
>> distributor, tracker)
>> }
>> }
>> SCALA
>> @@ -198,54 +199,55 @@
>>
>> it 'should run with ScalaCheck automatic test case generation' do
>> write 'src/test/scala/MySuite.scala', <<-SCALA
>> - import org.scalatest.prop.PropSuite
>> + import org.scalatest.FunSuite
>> + import org.scalatest.prop.Checkers
>> import org.scalacheck.Arbitrary._
>> import org.scalacheck.Prop._
>> -
>> - class MySuite extends PropSuite {
>> -
>> +
>> + class MySuite extends FunSuite with Checkers {
>> +
>> test("list concatenation") {
>> val x = List(1, 2, 3)
>> val y = List(4, 5, 6)
>> assert(x ::: y === List(1, 2, 3, 4, 5, 6))
>> check((a: List[Int], b: List[Int]) => a.size + b.size == (a :::
>> b).size)
>> }
>> -
>> - test(
>> - "list concatenation using a test method",
>> - (a: List[Int], b: List[Int]) => a.size + b.size == (a :::
>> b).size
>> - )
>> +
>> + test("list concatenation using a test method") {
>> + check((a: List[Int], b: List[Int]) => a.size + b.size == (a :::
>> b).size)
>> + }
>> }
>> SCALA
>> define('foo')
>> project('foo').test.invoke
>> project('foo').test.passed_tests.should include('MySuite')
>> end
>> -
>> +
>> it 'should fail if ScalaCheck test case fails' do
>> write 'src/test/scala/StringSuite.scala', <<-SCALA
>> - import org.scalatest.prop.PropSuite
>> + import org.scalatest.FunSuite
>> + import org.scalatest.prop.Checkers
>> import org.scalacheck.Arbitrary._
>> import org.scalacheck.Prop._
>>
>> - class StringSuite extends PropSuite {
>> + class StringSuite extends FunSuite with Checkers {
>> test("startsWith") {
>> check( (a: String, b: String) => (a+b).startsWith(a) )
>> }
>> -
>> +
>> test("endsWith") {
>> check( (a: String, b: String) => (a+b).endsWith(b) )
>> }
>> -
>> +
>> // Is this really always true?
>> test("concat") {
>> check( (a: String, b: String) => (a+b).length > a.length &&
>> (a+b).length > b.length )
>> }
>> -
>> +
>> test("substring2") {
>> check( (a: String, b: String) => (a+b).substring(a.length) == b )
>> }
>> -
>> +
>> test("substring3") {
>> check( (a: String, b: String, c: String) =>
>> (a+b+c).substring(a.length, a.length+b.length) == b )
>>
>>
>>
We need to make a decision here. ScalaCheck 1.5 is incompatible with
Specs 1.6.1. We could stick with Specs 1.6, but there are a lot of
very useful fixes and improvements in 1.6.1, including several which I
require for my projects.
I guess ideally ScalaTest would update to support ScalaCheck 1.6, but
I don't know when that is going to happen.
Daniel
On Nov 7, 2009, at 11:55 PM, "boisvert@apache.org"
<boisvert@apache.org> wrote:
> Author: boisvert
> Date: Sun Nov 8 05:54:50 2009
> New Revision: 833834
>
> URL: http://svn.apache.org/viewvc?rev=833834&view=rev
> Log:
> Fix Scalatest specs (1.0 API compatibility); revert to Scalacheck
> 1.5 since 1.6 is incompatible with Scalatest 1.0
>
> Modified:
> buildr/trunk/lib/buildr/scala/tests.rb
> buildr/trunk/spec/scala/tests_spec.rb
>
> Modified: buildr/trunk/lib/buildr/scala/tests.rb
> URL: http://svn.apache.org/viewvc/buildr/trunk/lib/buildr/scala/tests.rb?rev=833834&r1=833833&r2=833834&view=diff
> ===
> ===
> ===
> =====================================================================
> --- buildr/trunk/lib/buildr/scala/tests.rb (original)
> +++ buildr/trunk/lib/buildr/scala/tests.rb Sun Nov 8 05:54:50 2009
> @@ -23,7 +23,7 @@
> module Buildr::Scala
> # Scala::Check is available when using Scala::Test or Scala::Specs
> module Check
> - VERSION = '1.6'
> + VERSION = '1.5'
>
> class << self
> def version
> @@ -112,7 +112,7 @@
> # TODO: This should be name=>value pairs!
> #ant.includes group_includes.join(" ") if group_includes
> #ant.excludes group_excludes.join(" ") if group_excludes
> - (options[:properties] || []).each { |name, value|
> ant.property :name=>name, :value=>value }
> + (options[:properties] || []).each { |name, value|
> ant.config :name=>name, :value=>value }
> end
> end
>
> @@ -127,7 +127,7 @@
> File.open(reportFile, "r") do |input|
> while (line = input.gets) do
> failed = (line =~ /(TESTS? FAILED -)|(RUN STOPPED)|
> (RUN ABORTED)/) unless failed
> - completed |= (line =~ /Run completed\./)
> + completed |= (line =~ /Run completed/)
> break if (failed)
> end
> end
>
> Modified: buildr/trunk/spec/scala/tests_spec.rb
> URL: http://svn.apache.org/viewvc/buildr/trunk/spec/scala/tests_spec.rb?rev=833834&r1=833833&r2=833834&view=diff
> ===
> ===
> ===
> =====================================================================
> --- buildr/trunk/spec/scala/tests_spec.rb (original)
> +++ buildr/trunk/spec/scala/tests_spec.rb Sun Nov 8 05:54:50 2009
> @@ -113,7 +113,7 @@
> val sum = 1 + 1
> assert(sum === 2)
> }
> -
> +
> class InnerSuite extends FunSuite {
> test("addition") {
> val sum = 1 + 1
> @@ -180,15 +180,16 @@
> write 'src/test/scala/PropertyTestSuite.scala', <<-SCALA
> import org.scalatest._
> class PropertyTestSuite extends FunSuite {
> - var properties = Map[String, Any]()
> + var configMap = Map[String, Any]()
> test("testProperty") {
> - assert(properties("name") === "value")
> + assert(configMap("name") === "value")
> }
> -
> +
> protected override def runTests(testName: Option[String],
> reporter: Reporter, stopper: Stopper,
> - includes: Set[String],
> excludes: Set[String], properties: Map[String, Any]) {
> - this.properties = properties;
> - super.runTests(testName, reporter, stopper, includes,
> excludes, properties)
> + filter: Filter, configMap:
> Map[String, Any],
> + distributor: Option
> [Distributor], tracker: Tracker) {
> + this.configMap = configMap
> + super.runTests(testName, reporter, stopper, filter,
> configMap, distributor, tracker)
> }
> }
> SCALA
> @@ -198,54 +199,55 @@
>
> it 'should run with ScalaCheck automatic test case generation' do
> write 'src/test/scala/MySuite.scala', <<-SCALA
> - import org.scalatest.prop.PropSuite
> + import org.scalatest.FunSuite
> + import org.scalatest.prop.Checkers
> import org.scalacheck.Arbitrary._
> import org.scalacheck.Prop._
> -
> - class MySuite extends PropSuite {
> -
> +
> + class MySuite extends FunSuite with Checkers {
> +
> test("list concatenation") {
> val x = List(1, 2, 3)
> val y = List(4, 5, 6)
> assert(x ::: y === List(1, 2, 3, 4, 5, 6))
> check((a: List[Int], b: List[Int]) => a.size + b.size ==
> (a ::: b).size)
> }
> -
> - test(
> - "list concatenation using a test method",
> - (a: List[Int], b: List[Int]) => a.size + b.size == (a :::
> b).size
> - )
> +
> + test("list concatenation using a test method") {
> + check((a: List[Int], b: List[Int]) => a.size + b.size ==
> (a ::: b).size)
> + }
> }
> SCALA
> define('foo')
> project('foo').test.invoke
> project('foo').test.passed_tests.should include('MySuite')
> end
> -
> +
> it 'should fail if ScalaCheck test case fails' do
> write 'src/test/scala/StringSuite.scala', <<-SCALA
> - import org.scalatest.prop.PropSuite
> + import org.scalatest.FunSuite
> + import org.scalatest.prop.Checkers
> import org.scalacheck.Arbitrary._
> import org.scalacheck.Prop._
>
> - class StringSuite extends PropSuite {
> + class StringSuite extends FunSuite with Checkers {
> test("startsWith") {
> check( (a: String, b: String) => (a+b).startsWith(a) )
> }
> -
> +
> test("endsWith") {
> check( (a: String, b: String) => (a+b).endsWith(b) )
> }
> -
> +
> // Is this really always true?
> test("concat") {
> check( (a: String, b: String) => (a+b).length > a.length
> && (a+b).length > b.length )
> }
> -
> +
> test("substring2") {
> check( (a: String, b: String) => (a+b).substring(a.length)
> == b )
> }
> -
> +
> test("substring3") {
> check( (a: String, b: String, c: String) =>
> (a+b+c).substring(a.length, a.length+b.length) ==
> b )
>
>
Ok, I've gone ahead and implemented dependency/ordering between extensions (before_define / after_define)* à la Rake*. https://svn.apache.org/viewvc?view=revision&revision=833791 alex On Thu, Nov 5, 2009 at 7:44 AM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > (Moving to dev@) > > This issue is due to how extensions are handled. > > The Test module (which is an extension) adds test.compile.target to the > classpath: > > # lib/buildr/core/test.rb > after_define do |project| > ... > test.dependencies.concat [test.compile.target, > test.resources.target].compact > ... > end > > but Peter's custom extension is run only after so the change to > test.compile.from (which affects the value of test.compile.target) isn't > taken into account: > > after_define do |project| > project.test.compile.from project._(:src, 'test-functional', :java) > end > > and thus when JUnit runs the classpath is incorrect and it's too late to > fix anything since the classpath must be defined early for RJB to accept it. > > I've come across the same kind of issue with Eclipse extensions as well... > and I think we need a way to define dependencies/ordering between extensions > so we can properly compose them. Maybe we could borrow the same notation > from task dependencies? e.g., > > after_define(:test => :my_extension) > > after_define(:my_extension) do |project| > ... > end > > Thoughts? Any better ideas? > > alex > > On Mon, Nov 2, 2009 at 6:02 AM, Peter Schröder <ps@blau.de> wrote: > >> Hi, >> >> I am experiencing a strange behavior of buildr when having an empty >> test-folder. >> >> See the example in the attachment, and look into the readme.txt for >> the problem. >> >> Kind regards >> Peter >> >> >
On Fri, Nov 6, 2009 at 1:24 AM, Jean-Philippe Caruana < jeanphilippe1.caruana@orange-ftgroup.com> wrote: > what about : > > - buildr, et voilà ! > - shrink your build > - buildr, a fat free build > - lean builds > I like lean builds. It stands for "having no superfluous fat" (dictionary), but also fits very well with the idea of lean practices: creating more value with less work, or less waste, if you will. http://en.wikipedia.org/wiki/Lean_manufacturing Assaf > > > we keep on brainstorming here... we'll let you know ! > > -- > Jean-Philippe Caruana > ******************************** > Ce message et toutes les pieces jointes (ci-apres le "message") sont > confidentiels et etablis a l'attention exclusive de ses destinataires. > Toute utilisation ou diffusion non autorisee est interdite. > Tout message electronique est susceptible d'alteration. CVF decline > toute responsabilite au titre de ce message s'il a ete altere, deforme > ou falsifie. > Si vous n'etes pas destinataire de ce message, merci de le detruire > immediatement et d'avertir l'expediteur. > ********************************* > This message and any attachments (the "message") are confidential and > intended solely for the addressees. Any unauthorised use or > dissemination is prohibited. > Messages are susceptible to alteration. CVF shall not be liable for the > message if altered, changed or falsified. > If you are not the intended addressee of this message, please cancel it > immediately and inform the sender.. > ******************************** >
On Thu, Nov 5, 2009 at 9:41 PM, Assaf Arkin <assaf@labnotes.org> wrote: > On Thu, Nov 5, 2009 at 11:25 AM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > >> I wrote a draft of our November board report at: >> >> http://cwiki.apache.org/confluence/display/BUILDR/November+2009+Board+Report >> >> As always, feel free to edit or comment... I'll be sending it to the board >> on Sunday Nov. 8th. >> > > +1 > > assaf +1 lacton
what about : - buildr, et voilà ! - shrink your build - buildr, a fat free build - lean builds we keep on brainstorming here... we'll let you know ! -- Jean-Philippe Caruana ******************************** Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'attention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. CVF decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. ********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. CVF shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender.. ********************************
How about "A build system for the agile world"? Alex Boisvert wrote: > I attended the media training at ApacheCon earlier this week and as part of > the day's discussions, I submitted our current project tagline "The build > system that doesn't suck" to our group for feedback. The group was mostly > composed of technical folks and one non-technical person (Sally, our > trainer). As you might expect, the response to the tagline was not very > enthusiastic. Most thought is was an okay tagline for a small project > that's starting out but that it probably needs refinement for a project with > bigger aspirations. > > Among some comment, one was along the line of... "Let's say a developer > discovers Buildr and really likes it. Before using it, she needs to have it > checked out by her manager. The manager goes to the website, reads the > tagline ... and ... well, doesn't get a great first impression." Don't be > alarmed, though, the group thought the current tagline could still be used > on t-shirts and other such promotional pieces but that the official tagline > should probably be a little more positive sounding. > > I tend to agree with the feedback and in any case I've been meaning to > brainstorm this on the mailing list... Here are some starting points I've > been thinking about for the tagline: > > "Ready, Set, Build!" (emphasize speed / productivity) > > "Beautiful Builds" (elegance / beautiful code meme) > > "Any Code, Any Size, Any Task" (polyglot programming, scalability and > customizability) > > Any of these strike your fancy? You think you can do better? > > I'd like to collect ideas during the next 2 weeks (time enough to brainstorm > without pressure) and then proceed with a couple rounds of voting for the > best tagline. Winner gets karma points, self-satisfaction, bragging rights > and the next release (1.4.0) dedicated to her/him. > > alex > > -- -- Tikal <http://www.tikalk.com> Tikal Project <http://tikal.sourceforge.net>
"Ready, Set, Build" gets my +1. "Buildr it and they will come"? ;p On Fri, Nov 6, 2009 at 8:12 AM, Alexis Midon <alexismidon@gmail.com> wrote: > In the spirit of "Ready, Set, Build" and as a tribute to MJ: "Just build it, > build it" > > I'm only half kidding ;) > > On Thu, Nov 5, 2009 at 12:12 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > >> I attended the media training at ApacheCon earlier this week and as part of >> the day's discussions, I submitted our current project tagline "The build >> system that doesn't suck" to our group for feedback. Â The group was mostly >> composed of technical folks and one non-technical person (Sally, our >> trainer). Â As you might expect, the response to the tagline was not very >> enthusiastic. Â Most thought is was an okay tagline for a small project >> that's starting out but that it probably needs refinement for a project >> with >> bigger aspirations. >> >> Among some comment, one was along the line of... "Let's say a developer >> discovers Buildr and really likes it. Â Before using it, she needs to have >> it >> checked out by her manager. Â The manager goes to the website, reads the >> tagline ... and ... well, doesn't get a great first impression." Â Don't be >> alarmed, though, the group thought the current tagline could still be used >> on t-shirts and other such promotional pieces but that the official tagline >> should probably be a little more positive sounding. >> >> I tend to agree with the feedback and in any case I've been meaning to >> brainstorm this on the mailing list... Â Here are some starting points I've >> been thinking about for the tagline: >> >> "Ready, Set, Build!" Â (emphasize speed / productivity) >> >> "Beautiful Builds" Â (elegance / Â beautiful code meme) >> >> "Any Code, Any Size, Any Task" Â (polyglot programming, scalability and >> customizability) >> >> Any of these strike your fancy? Â You think you can do better? >> >> I'd like to collect ideas during the next 2 weeks (time enough to >> brainstorm >> without pressure) and then proceed with a couple rounds of voting for the >> best tagline. Â Winner gets karma points, self-satisfaction, bragging rights >> and the next release (1.4.0) dedicated to her/him. >> >> alex >> >
In the spirit of "Ready, Set, Build" and as a tribute to MJ: "Just build it, build it" I'm only half kidding ;) On Thu, Nov 5, 2009 at 12:12 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > I attended the media training at ApacheCon earlier this week and as part of > the day's discussions, I submitted our current project tagline "The build > system that doesn't suck" to our group for feedback. The group was mostly > composed of technical folks and one non-technical person (Sally, our > trainer). As you might expect, the response to the tagline was not very > enthusiastic. Most thought is was an okay tagline for a small project > that's starting out but that it probably needs refinement for a project > with > bigger aspirations. > > Among some comment, one was along the line of... "Let's say a developer > discovers Buildr and really likes it. Before using it, she needs to have > it > checked out by her manager. The manager goes to the website, reads the > tagline ... and ... well, doesn't get a great first impression." Don't be > alarmed, though, the group thought the current tagline could still be used > on t-shirts and other such promotional pieces but that the official tagline > should probably be a little more positive sounding. > > I tend to agree with the feedback and in any case I've been meaning to > brainstorm this on the mailing list... Here are some starting points I've > been thinking about for the tagline: > > "Ready, Set, Build!" (emphasize speed / productivity) > > "Beautiful Builds" (elegance / beautiful code meme) > > "Any Code, Any Size, Any Task" (polyglot programming, scalability and > customizability) > > Any of these strike your fancy? You think you can do better? > > I'd like to collect ideas during the next 2 weeks (time enough to > brainstorm > without pressure) and then proceed with a couple rounds of voting for the > best tagline. Winner gets karma points, self-satisfaction, bragging rights > and the next release (1.4.0) dedicated to her/him. > > alex >
"Read, Set, Build!" sounds a little bit too much like a Ruby tutorial. :-) I don't have any better ideas at the moment, but I'll give it some thought. Daniel On Thu, Nov 5, 2009 at 2:43 PM, Assaf Arkin <assaf@labnotes.org> wrote: > On Thu, Nov 5, 2009 at 12:12 PM, Alex Boisvert <alex.boisvert@gmail.com > >wrote: > > > I attended the media training at ApacheCon earlier this week and as part > of > > the day's discussions, I submitted our current project tagline "The build > > system that doesn't suck" to our group for feedback. The group was > mostly > > composed of technical folks and one non-technical person (Sally, our > > trainer). As you might expect, the response to the tagline was not very > > enthusiastic. Most thought is was an okay tagline for a small project > > that's starting out but that it probably needs refinement for a project > > with > > bigger aspirations. > > > > Among some comment, one was along the line of... "Let's say a developer > > discovers Buildr and really likes it. Before using it, she needs to have > > it > > checked out by her manager. The manager goes to the website, reads the > > tagline ... and ... well, doesn't get a great first impression." Don't > be > > alarmed, though, the group thought the current tagline could still be > used > > on t-shirts and other such promotional pieces but that the official > tagline > > should probably be a little more positive sounding. > > > > I tend to agree with the feedback and in any case I've been meaning to > > brainstorm this on the mailing list... Here are some starting points > I've > > been thinking about for the tagline: > > > > "Ready, Set, Build!" (emphasize speed / productivity) > > > > "Beautiful Builds" (elegance / beautiful code meme) > > > > "Any Code, Any Size, Any Task" (polyglot programming, scalability and > > customizability) > > > > Any of these strike your fancy? You think you can do better? > > > > > I like Ready, Set, Build! > > Beautiful Builds could be the title of a book or blog post. > > Assaf > > > > > > I'd like to collect ideas during the next 2 weeks (time enough to > > brainstorm > > without pressure) and then proceed with a couple rounds of voting for the > > best tagline. Winner gets karma points, self-satisfaction, bragging > rights > > and the next release (1.4.0) dedicated to her/him. > > > > alex > > >
On Thu, Nov 5, 2009 at 12:12 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > I attended the media training at ApacheCon earlier this week and as part of > the day's discussions, I submitted our current project tagline "The build > system that doesn't suck" to our group for feedback. The group was mostly > composed of technical folks and one non-technical person (Sally, our > trainer). As you might expect, the response to the tagline was not very > enthusiastic. Most thought is was an okay tagline for a small project > that's starting out but that it probably needs refinement for a project > with > bigger aspirations. > > Among some comment, one was along the line of... "Let's say a developer > discovers Buildr and really likes it. Before using it, she needs to have > it > checked out by her manager. The manager goes to the website, reads the > tagline ... and ... well, doesn't get a great first impression." Don't be > alarmed, though, the group thought the current tagline could still be used > on t-shirts and other such promotional pieces but that the official tagline > should probably be a little more positive sounding. > > I tend to agree with the feedback and in any case I've been meaning to > brainstorm this on the mailing list... Here are some starting points I've > been thinking about for the tagline: > > "Ready, Set, Build!" (emphasize speed / productivity) > > "Beautiful Builds" (elegance / beautiful code meme) > > "Any Code, Any Size, Any Task" (polyglot programming, scalability and > customizability) > > Any of these strike your fancy? You think you can do better? > I like Ready, Set, Build! Beautiful Builds could be the title of a book or blog post. Assaf > > I'd like to collect ideas during the next 2 weeks (time enough to > brainstorm > without pressure) and then proceed with a couple rounds of voting for the > best tagline. Winner gets karma points, self-satisfaction, bragging rights > and the next release (1.4.0) dedicated to her/him. > > alex >
On Thu, Nov 5, 2009 at 11:25 AM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > I wrote a draft of our November board report at: > > http://cwiki.apache.org/confluence/display/BUILDR/November+2009+Board+Report > > As always, feel free to edit or comment... I'll be sending it to the board > on Sunday Nov. 8th. > +1 assaf > > alex >
I attended the media training at ApacheCon earlier this week and as part of the day's discussions, I submitted our current project tagline "The build system that doesn't suck" to our group for feedback. The group was mostly composed of technical folks and one non-technical person (Sally, our trainer). As you might expect, the response to the tagline was not very enthusiastic. Most thought is was an okay tagline for a small project that's starting out but that it probably needs refinement for a project with bigger aspirations. Among some comment, one was along the line of... "Let's say a developer discovers Buildr and really likes it. Before using it, she needs to have it checked out by her manager. The manager goes to the website, reads the tagline ... and ... well, doesn't get a great first impression." Don't be alarmed, though, the group thought the current tagline could still be used on t-shirts and other such promotional pieces but that the official tagline should probably be a little more positive sounding. I tend to agree with the feedback and in any case I've been meaning to brainstorm this on the mailing list... Here are some starting points I've been thinking about for the tagline: "Ready, Set, Build!" (emphasize speed / productivity) "Beautiful Builds" (elegance / beautiful code meme) "Any Code, Any Size, Any Task" (polyglot programming, scalability and customizability) Any of these strike your fancy? You think you can do better? I'd like to collect ideas during the next 2 weeks (time enough to brainstorm without pressure) and then proceed with a couple rounds of voting for the best tagline. Winner gets karma points, self-satisfaction, bragging rights and the next release (1.4.0) dedicated to her/him. alex
Looks good! Daniel On Thu, Nov 5, 2009 at 1:25 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote: > I wrote a draft of our November board report at: > > http://cwiki.apache.org/confluence/display/BUILDR/November+2009+Board+Report > > As always, feel free to edit or comment... I'll be sending it to the board > on Sunday Nov. 8th. > > alex >
I wrote a draft of our November board report at: http://cwiki.apache.org/confluence/display/BUILDR/November+2009+Board+Report As always, feel free to edit or comment... I'll be sending it to the board on Sunday Nov. 8th. alex
(Moving to dev@) This issue is due to how extensions are handled. The Test module (which is an extension) adds test.compile.target to the classpath: # lib/buildr/core/test.rb after_define do |project| ... test.dependencies.concat [test.compile.target, test.resources.target].compact ... end but Peter's custom extension is run only after so the change to test.compile.from (which affects the value of test.compile.target) isn't taken into account: after_define do |project| project.test.compile.from project._(:src, 'test-functional', :java) end and thus when JUnit runs the classpath is incorrect and it's too late to fix anything since the classpath must be defined early for RJB to accept it. I've come across the same kind of issue with Eclipse extensions as well... and I think we need a way to define dependencies/ordering between extensions so we can properly compose them. Maybe we could borrow the same notation from task dependencies? e.g., after_define(:test => :my_extension) after_define(:my_extension) do |project| ... end Thoughts? Any better ideas? alex On Mon, Nov 2, 2009 at 6:02 AM, Peter Schröder <ps@blau.de> wrote: > Hi, > > I am experiencing a strange behavior of buildr when having an empty > test-folder. > > See the example in the attachment, and look into the readme.txt for > the problem. > > Kind regards > Peter > >
Thanks! I've applied the patch now.
And while I was at it, I added a way to declare classpath variables so that
the generated .classpath files remain portable even if you have libraries
located outside the project. We already did this for M2_REPO but now you
can define your own variables.
eclipse.classpath_variables { :LIBS => '/path/to/external/libraries' }
cheers,
alex
On Thu, Oct 29, 2009 at 12:14 AM, Stefan Wasilewski <stefanw@gmail.com>wrote:
> Greetings,
>
> I've submitted this issue along with a one line patch to correct it.
> Would
> someone mind reviewing it for me?
>
> Thanks for a fantastically fun build system!
>
> ~ Stefan
>
Greetings, I've submitted this issue along with a one line patch to correct it. Would someone mind reviewing it for me? Thanks for a fantastically fun build system! ~ Stefan