Databases
StackOverflow2013
Postsdbo
POHow to get JBehave to include test dependency jars when running in Maven?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to get JBehave to include test dependency jars when running in Maven?
    primarykey
    data
    text
    <p>I've got a simple-enough project that I'm trying to test with JBehave core, and doing things in a maven-kosher fashion (that is production under src/main, test under src/test, integration testing stuff under an added path of src/it/{java,resources}, and test dependencies scoped with test). Getting this all running together seems rather harder than it should be.</p> <p>My case is a little different because my code is in src/it/java, and resources in src/it/resources. Having configured those in maven, Eclipse runs the stories just fine - the problem is with Maven.</p> <p>Currently my problem is that it doesn't see mockito (or other test dependencies) when running (mvn -X). Even editing a working example and adding a test dependency doesn't include it.</p> <p>I've been able to bodge it into working by sticking my test dependencies within the plugin xml blob, but obviously I don't want to repeat myself like that.</p> <p>The relevant parts of the build file (without the manually specified dependency hack) are:</p> <p></p> <pre><code>&lt;testResources&gt; &lt;testResource&gt; &lt;directory&gt;src/test/resources&lt;/directory&gt; &lt;filtering&gt;false&lt;/filtering&gt; &lt;includes&gt; &lt;include&gt;**/*&lt;/include&gt; &lt;/includes&gt; &lt;/testResource&gt; &lt;testResource&gt; &lt;directory&gt;src/it/resources&lt;/directory&gt; &lt;filtering&gt;false&lt;/filtering&gt; &lt;includes&gt; &lt;include&gt;**/*&lt;/include&gt; &lt;/includes&gt; &lt;/testResource&gt; &lt;/testResources&gt; </code></pre> <p>...</p> <pre><code> &lt;plugin&gt; &lt;groupId&gt;org.jbehave&lt;/groupId&gt; &lt;artifactId&gt;jbehave-maven-plugin&lt;/artifactId&gt; &lt;executions&gt; &lt;execution&gt; &lt;id&gt;embeddable-stories&lt;/id&gt; &lt;phase&gt;integration-test&lt;/phase&gt; &lt;configuration&gt; &lt;includes&gt; &lt;include&gt;**/*Story.java&lt;/include&gt; &lt;/includes&gt; &lt;ignoreFailureInStories&gt;false&lt;/ignoreFailureInStories&gt; &lt;ignoreFailureInView&gt;false&lt;/ignoreFailureInView&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;testSourceDirectory&gt;src/it/java&lt;/testSourceDirectory&gt; &lt;/configuration&gt; &lt;goals&gt; &lt;goal&gt;run-stories-as-embeddables&lt;/goal&gt; &lt;/goals&gt; &lt;/execution&gt; &lt;/executions&gt; &lt;/plugin&gt; </code></pre> <p>Ideas?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDave LeBlanc
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to get JBehave to include test dependency jars when running in Maven?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to get JBehave to include test dependency jars when running in Maven?
      1. USRobert Watkins
      1. VTFavorite
    3. VO
      singulars
      1. POHow to get JBehave to include test dependency jars when running in Maven?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload