[
https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276742#comment-276742
]
Bart De Neuter commented on JBEHAVE-584:
----------------------------------------
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.
> Support loading stories from Google Docs
> ----------------------------------------
>
> Key: JBEHAVE-584
> URL: https://jira.codehaus.org/browse/JBEHAVE-584
> Project: JBehave
> Issue Type: New Feature
> Components: Core, ODF Support
> Reporter: Bart De Neuter
> Assignee: Mauro Talevi
> Priority: Minor
> Fix For: 3.5
>
> Attachments: googledocs.patch
>
>
> As a BA I want to be able to write my story in Google Docs.
> This has the advantage that the stories are in the cloud and multiple
> stakeholders (BA, developer, ...) work at the same time on the same document.
> By using the Google docs API, a document can be exported to ODT and be
> delegated to the ODT support in JBehave.
> ATTENTION: the given patch contains also a fix for the class OdfUtils in the
> module jbehave-odf. The class OdfTextExtractor is used to convert ODT
> correctly to text.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
