[
https://jira.codehaus.org/browse/JBEHAVE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286673#comment-286673
]
Alexander Lehmann commented on JBEHAVE-376:
---
I have basically no experience with eclipse
Olmo,
try to extend your abstract class from InjectableEmbedder, as we did
with TraderAnnotatedEmbedder example.
cheers
On 22/12/11 07:45, Olmo Rigolo wrote:
Hi all,
unfortunately I'm having problems wirh the
@RunWith(JiraAnnotatedPathRunner.class) and the maven goal.
I have concrete s
[
https://jira.codehaus.org/browse/JBEHAVE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286646#comment-286646
]
Cristiano Gavião commented on JBEHAVE-376:
--
Hi Alexander,
The easy part, now that I alre
Olmo Rigolo created JBEHAVE-683:
---
Summary: Update jBehave maven goals documentation
Key: JBEHAVE-683
URL: https://jira.codehaus.org/browse/JBEHAVE-683
Project: JBehave
Issue Type: Task
Hi all,
unfortunately I'm having problems wirh the
@RunWith(JiraAnnotatedPathRunner.class) and the maven goal.
I have concrete scenario classes that assemble the stories from jira like:
@UsingSteps(instances={StorySteps.class})
@UsingStories(stories={"PRMPLI-1080", "PRMPLI-1081"})
public class
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 6681145918c6ac2a381ff59efc3de76197de7b00 (commit)
from 102af7c1fa1924c2
Hi Mauro, hi Christiano,
so I did the right thing by extending the AnnotatedPathRunner. I took your
idea with the anonymous class for the AnnotationBuilder and deleted my own
implementation.
Till now I was using the @UsingPaths annotation, but I think its nicer to
have a new Annotation like
@
