You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't actually tried the plugin with a maven 2/3 style project - if the project has a workspace that is accessible it may work - I'll have to investigate.
I tried the plugin with Jenkins 1.492 using a maven style project with maven 3 for a prototype and it works like a charm. Please note that I have only 2 features yet (one in english and one in german because auf issue #48 , see issue #31 for the work around).
The project is a multi module maven project that has only one module which uses cucumber for acceptance tests. I've set the "Json Reports Path" to the target directory of that module because automatic detection did not work. I think that won't work with multiple modules generating multiple .json files in different target directories.
I'll enhance the protoype during the next months and I'll report back if there are any problems with the maven style project but I don't expect to find some ;-).
Our projects are maven based, and it'd be immensely helpful to take advantage of this project with a Maven 2/3 Style Project.
I haven't looked into the work needed to do this, I just thought I'd log the feature request here, so it won't get forgotten.
The text was updated successfully, but these errors were encountered: