This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-core".
The branch, master has been updated
via 84266956b7662894667a1e44a742a8c7e5ee9c73 (commit)
from 00f21adc196a4fc
[
http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-339:
-
Fix Version/s: (was: 3.1)
3.0.1
Assignee: Mauro Talevi
> HTML report n
[
http://jira.codehaus.org/browse/JBEHAVE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-347.
--
Resolution: Fixed
> Method useViewGenerator in Configuration does not honour the builder pattern
> -
Method useViewGenerator in Configuration does not honour the builder pattern
Key: JBEHAVE-347
URL: http://jira.codehaus.org/browse/JBEHAVE-347
Project: JBehave
Issu
[
http://jira.codehaus.org/browse/JBEHAVE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-346.
--
Resolution: Fixed
> Add getter/setter for FilePathResolver in SpringStoryReporterBuilder
> -
Done: http://jira.codehaus.org/browse/JBEHAVE-346
On 23/09/2010 20:32, Peter Suggitt wrote:
> Hi
>
> Bit of boring one, but on SpringStoryReporterBuilder the getter/setter
> is missing from the SpringStoryReporterBuilder class for
> pathResolver. I am extending the class at the moment to work a
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-core".
The branch, master has been updated
via 00f21adc196a4fccd4c6a57b339eb0d70d496817 (commit)
from 7be8a82dd69c57b
Add getter/setter for FilePathResolver in SpringStoryReporterBuilder
Key: JBEHAVE-346
URL: http://jira.codehaus.org/browse/JBEHAVE-346
Project: JBehave
Issue Type: Improvem
Hi
Bit of boring one, but on SpringStoryReporterBuilder the getter/setter
is missing from the SpringStoryReporterBuilder class for pathResolver.
I am extending the class at the moment to work around it which I am not
comfortable in the longer term. Can't see anything obvious as to why
they
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-web".
The branch, master has been updated
via c2aecc22fc6a9fd4e571fdff89fd1a76900ba84f (commit)
from dc5f3f0be731c545
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-web".
The branch, master has been updated
via dc5f3f0be731c545c242b07487aa6062704817e7 (commit)
from fe8542f118ad1f9f
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-web".
The branch, master has been updated
via fe8542f118ad1f9f167a53e0fbffee822bb3dfa1 (commit)
from 175e2ec41291f497
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-web".
The branch, master has been updated
via 175e2ec41291f4976b0b89e9d230550e72f1bee1 (commit)
from c7ee07009d1f48ca
13 matches
Mail list logo