Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin doesn't find steps in a dependent jar #11

Open
skurlow opened this issue Apr 1, 2014 · 7 comments
Open

Plugin doesn't find steps in a dependent jar #11

skurlow opened this issue Apr 1, 2014 · 7 comments

Comments

@skurlow
Copy link

skurlow commented Apr 1, 2014

We are trying to split some of our step classes into a separate maven module that is in a separate maven project. For those step classes that we have moved into the new module their steps are showing up in our story files with a red underline meaning the plugin thinks the steps are not defined.

But that is not true. ;-) When we run our story using a jbehave runner we can see jbehave is able to find the steps. So the issue is with the jbehave support plugin v1.3.

Now this new module (jar) is added as a maven dependency and when looking at IntelliJ's module dependencies tab I can see our new jar (containing our steps) is listed. According to the plugin's wiki page it says the jbehave support plugin should scan the module classpath but it doesn't seem to be or I don't really understand what that statement on the wiki means???

Alternatively can you point me to the code where I can change the jbehave support plugin to widen its scan?

Otherwise this is a fantastic plugin and would be lost without it. Thanks so much. :)

@longtimeago
Copy link

+1
moved common steps implementation to separate module and discovered these issue ...

@harley84
Copy link
Collaborator

Can you please give an example of relevant dependency tree?
For example if:
A - maven module with JBehave unit tests
B - maven module with stories
C - maven module with steps
Are some of the above modules overlap?
What are the dependencies in your case?

Thanks

@longtimeago
Copy link

Ups ... looks like it was dependency issue. Sorry for boring you :(

@Shnitzelil
Copy link

Hey,

In our project we're using steps from different dependencies (from other projects) and sadly this great plugin is unable to "see" those steps... (cannot use auto-complete and also mark them as "No definition...."

Can you point me to the code?

Thanks

@simpleTester
Copy link

Hi,

I am facing the same issue.
My project is using dependent jars, which contain the step defs.
JBehave plugin does not find the step def, i.e. when I ctrl+click the step it does not take me to the dependent codebase.

Longtimeago, if you have solved the issue could you please help.

Thanks

@harley84
Copy link
Collaborator

Sorry everyone, I do not have time recently to address the issues.
@Shnitzelil , @simpleTester - can you please address my previous comment regarding the dependency tree, or even better, upload a small project that reproduces it?

Thanks in advance

@stahloss
Copy link

Same issue here. Seems that when the steps project is not opened in the same project as a module, it works. When it is opened as a module, however, the steps cannot be found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants