Re: [jbehave-dev] Building the website

Hey Shane,

I fixed the problem by making the JBehave sitespec.rb file use Cotta.  
This issue contains the attached patch: http://jira.codehaus.org/ 
browse/JBEHAVE-74

To everyone else in the list who might not have a clue what  
sitespec.rb is for: if you've got Ruby and the BuildMaster, RedCloth  
and BlueCloth gems installed, you can run it like:

 > ruby sitespec.rb server

And point your browser to http://localhost:2000 to get your own local  
version of the JBehave website.

I am working on fixing the broken links and adding a bit more  
information about JBehave on the website, so this will be handy ;)

Cheers,

Carlos

On 22 Nov 2006, at 18:25, Shane Duan wrote:

> Hi,
>
> It appears the jBehave works with the older version of BuildMaster
> (0.8.0 perhaps).  BuildMaster 0.9.0 has Cotta (hopefully you are not
> tired of hearing this) implementation for easy file operations (yes,
> easier than Ruby itself).

Re: [jbehave-dev] JIRA

Just did that! Have a look at http://jira.codehaus.org/browse/ 
JBEHAVE-74 :)

Cheers,

Carlos

On 22 Nov 2006, at 18:30, Shane Duan wrote:

> I would like update the sitespec ruby script so that it works with the
> latest BuildMaster.  And I will send out email about building jbehave
> site, which will also checked in.
>
> There is a JIRA ticket already about website face lifting.
>
> Cheers,
> Shane
>
> On 11/22/06, Dan North <dan@...> wrote:
>>
>>  Also, just to remind people to mail the dev list before embarking on
>> anything so we're all in the loop (even those of us who don't look  
>> at jira
>> too often...).
>>
>>  Cheers,
>>  Dan
>>
>>
>>

Re: [jbehave-dev] JIRA

Nice one Shane, thanks!

Shane Duan wrote:
> I would like update the sitespec ruby script so that it works with the
> latest BuildMaster.  And I will send out email about building jbehave
> site, which will also checked in.
>
> There is a JIRA ticket already about website face lifting.
>
> Cheers,
> Shane
>
> On 11/22/06, Dan North <dan@...> wrote:
>>
>>  Also, just to remind people to mail the dev list before embarking on
>> anything so we're all in the loop (even those of us who don't look at 
>> jira
>> too often...).
>>
>>  Cheers,
>>  Dan
>>
>>
>>
>>  Elizabeth Keogh wrote:
>>
>> Hi all,
>>
>>  I spent a little bit of time yesterday cleaning up JIRA.
>>

[jbehave-dev] jBehave lists on gmane.org

jBehavers,

given the volume of email traffic which has been increasing exponentially (good sign of a waking 
project , I asked the nice folks of gmane.org to resurrect the subscription to the lists.

For info visit http://gmane.org - in practice this means you can avoid subscribing directly to the 
lists and use a newsgroup client (eg Thunderbird) to subscribe to groups

gmane.comp.java.jbehave.devel
gmane.comp.java.jbehave.scm
gmane.comp.java.jbehave.user

et voila', les jeux sont faits!

You can also simply search for jbehave when subscribing to a group.
Note that the user group has not been created yet - it will upon the first message.

Cheers

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] Building the website

YOU ROCK MAN...

I saw the check in, rather than doing File.join, you can use cotta to
get your file by something like

cotta.dir('root').dir('content/site/index')

Looks like you are getting it.  To find out about broken links, you
can do site_spec test which will launch the server and use IE (through
watir) to test the links.  I don't know why but IE 7 (the one with
multiple tabs) does not return error when a link is not found so you
will need IE 6 for this to work.

I don't think you need to install BlueCloth, since jbehave only use
textile syntax.  If that is not true, please post the error message
and I can take a look at it.

Cheers
Shane

On 11/22/06, Carlos Villela <carlos.villela@...> wrote:
> Hey Shane,
>
> I fixed the problem by making the JBehave sitespec.rb file use Cotta.
> This issue contains the attached patch: http://jira.codehaus.org/
> browse/JBEHAVE-74
>
> To everyone else in the list who might not have a clue what
> sitespec.rb is for: if you've got Ruby and the BuildMaster, RedCloth
> and BlueCloth gems installed, you can run it like:

[jbehave-dev] Re: [jbehave-scm] [jbehave] [575] trunk: [JBEHAVE-74] website updated to use BuildMaster 0.9 and added instruction on how to update website

weird, I never understood why the scm commit notification shows the
link to JIRA but JIRA does not show the change set.  Oh well.

Since this one is about building the site, the document that I added
in won't be of any use before you learn how to read it. :)  I am
pasting the simplified instruction here:

    * Install Ruby and gems
    * Update Website
    * Build Website

Install Ruby and Gems

If you are on Windows system, the easiest thing to do is to download
Ruby One-Click Installer (http://rubyforge.org/frs/?group_id=167).
Then make sure that ruby.exe is on your path (verify it by typing
command ruby --version).  After that you can use gem to install
BuildMaster and RedCloth:

gem install BuildMaster
gem install RedCloth

Update Site

At the root of jBehave project there is a sitespec.rb file. Change to
that directory and type "sitespec.rb server", it will launch a local
HTTP server that serve the documents at port 2000. The output should
something like the following:

[2006-11-23 00:50:25] INFO  WEBrick 1.3.1

Re: [jbehave-dev] jBehave lists on gmane.org

Sorry for being ignorant here...  Can I still subscribe to it through
my email account?  I use it to label useful threads.

Cheers,
Shane

On 11/22/06, Mauro Talevi <mauro.talevi@...> wrote:
> jBehavers,
>
> given the volume of email traffic which has been increasing exponentially (good sign of a waking
> project , I asked the nice folks of gmane.org to resurrect the subscription to the lists.
>
> For info visit http://gmane.org - in practice this means you can avoid subscribing directly to the
> lists and use a newsgroup client (eg Thunderbird) to subscribe to groups
>
> gmane.comp.java.jbehave.devel
> gmane.comp.java.jbehave.scm
> gmane.comp.java.jbehave.user
>
> et voila', les jeux sont faits!
>
> You can also simply search for jbehave when subscribing to a group.
> Note that the user group has not been created yet - it will upon the first message.
>
> Cheers
>
>
>
>
> ---------------------------------------------------------------------

[jbehave-dev] 1.0 roadmap - setUp / tearDown / verifyMocks?

Re: [jbehave-dev] jBehave lists on gmane.org

Shane Duan wrote:
> Sorry for being ignorant here...  Can I still subscribe to it through
> my email account?  I use it to label useful threads.
> 

Yep - it changes nothing for people subscribed to the list.

gmane.org acts as just another subscriber and keeps an archive of the mail lists,
which can then be searched or in general accessed without filling in your mailbox.

So you may wish to use both mail and newsgroup client for list subscription.
Up to you.

I find it priceless in keeping track of all the list traffic in various projects.

Cheers

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] 1.0 roadmap - setUp / tearDown / verifyMocks?

Elizabeth Keogh wrote:
> 
> Hi all,
> 
> I'm sitting at the TW beach with four developers eager to help. There 
> aren't many unassigned stories any more on our JIRA roadmap. I'd like to 
> try and get some of the more valuable stuff in if we can.
> 
> One of the things I've really missed while using JBehave is having setUp 
> / tearDown in the behaviours, and having my mocks verified 
> automatically. Calling setUp and verifyMocks each time just isn't fun. 
> I'd like to move this up to 1.0, assuming that I can find someone to do it.
> 

Good idea.  One thought:  we should have the option to have setUp/tearDown only at class level,
as opposed to every behaviour method - cf what is done in JUnit 4.0.

Also, we should change the nomenclature to avoid confusion with JUnit.

How about:
- prepareBehaviour/Behaviours -> set up methods per method/per class
- verifyBehaviour/Behaviours -> verify methods per method/per class

Cheers

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email