Details
-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.4
-
Component/s: Maven Plugin
-
Labels:None
-
Number of attachments :
Description
Because I run JBehave in the test scope of the same project that it is testing I cannot use the compile scope for JBehave dependencies.
However, the maven unpack-view-resources goal requires the resources to be in compile scope. This means that they get included in my final WAR.
When I switch them to test scope the unpack-view-resources goal doesn't find them.
I suppose the best fix would be to allow the unpack-view-resources goal to have its scope configured in the same way as the run-stories goals.
Activity
Mauro Talevi
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Mauro Talevi [ maurotalevi ] | |
Fix Version/s | 3.4 [ 17278 ] | |
Affects Version/s | web-3.3.1 [ 17313 ] |
Mauro Talevi
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
problem dependencies:
<dependency>
{jbehave.site.version}<groupId>org.jbehave.site</groupId>
<artifactId>jbehave-site-resources</artifactId>
<version>$
</version>
{jbehave.version}<type>zip</type>
</dependency>
<dependency>
<groupId>org.jbehave</groupId>
<artifactId>jbehave-core</artifactId>
<version>$
</version>
<classifier>resources</classifier>
<type>zip</type>
</dependency>