[
https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276664#comment-276664
]
Bart De Neuter commented on JBEHAVE-584:
----------------------------------------
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?
> 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
