Support loading stories from Google Docs

Hi Bart,

added your contributed Google docs loader, but kept in the jbehave-odf module rather than a separate one.

I've tested against a private document, but clearly this cannot be used for generic testing (hence the tests are marked as @Ignore). What we'd need is to create a public group account that we can use for testing.

Do you know if that is possible?

Hi Mauro,

I added it to a separate module because it has nothing to do with odf. Google docs can export to different formats and I have used odt in order to delegate it to the odf-module for converting it to text. But from the user perspective it is an implementation detail. If you place it in the odf-module then this module also needs the dependencies to the google api's.

I'm not sure how to test it without putting a password in the test class. Maybe you can make a google account for JBehave and put the password in the settings.xml from the maven build on the different environments?

For the moment, we are exporting to use odf formats, so it makes sense for it be in the jbehave-odf module.

Once we start using other formats, we can move it to a separate module. But is there an alternative format to use?

And we should create a jbehave user for google docs.

Actually, for jbehave we convert the document from google docs to a String. How we do it, is an implementation detail and not important for the user. Instead of first exporting to ODT, we could export directly to txt. But then we loose the correct formatting of the table.
But for me it's fine if you put it in the jbehave-odf module.

Do you want me to create a jbehave user? I still don't know how I have to handle the password question. If you put the password in settings.xml or as an environment variable, then you could run the tests on your CI server. But the downloaded code can not be build out of the box.

Presumably, we should be able to maintain the format in txt too, like in a wiki.

Let's decide what formats we are going to or can support and then we can decide whether it warrants a separate module or not. Not against it, just would like to understand the usecase first.

For the google access, ideally we'd want to create a group access and have a read-only user. It'd be great if you could investigate the issue with the Google Docs folks and present the options we have. I'd be surprised if they did not offer some sort of test access (but perhaps it's not available for general public).

Use the DocumentQuery API for safer construction of the request URI

Thanks, applied patch, although had to applied changes manually. Somehow this patch did not get applied as the other. Did you change method of patch generation?

Mauro,
My apologies, it is the first time I use git and I'm still learning how to use it. Although both are created with eclipse, it is possible that I created the second patch with other options then the first patch.

No problem I find that using command-line "git diff > ~/some.patch" is easier and safer.

Mauro,

I tried to figure out if there is something like a public group account. But it seems not. You can find the discussion here: http://code.google.com/apis/documents/forum.html?place=topic%2Fgoogle-documents-list-api%2FIh0R7qza8D4%2Fdiscussion

Hi Bart,

added jbehave-google-example which can be executed by users providing their own credentials as env variables.

The unit test will be refactored to mock the response from the Google docs API.

Hi Bart,

as you originally suggested, a separate jbehave-google module has now been created, which can be used to expand support for Google Docs, even when not based on ODF.