[
http://jira.codehaus.org/browse/JBEHAVE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265581#action_265581
]
Caoilte O'Connor commented on JBEHAVE-507:
------------------------------------------
problem dependencies:
<dependency>
<groupId>org.jbehave.site</groupId>
<artifactId>jbehave-site-resources</artifactId>
<version>${jbehave.site.version}</version>
<type>zip</type>
</dependency>
<dependency>
<groupId>org.jbehave</groupId>
<artifactId>jbehave-core</artifactId>
<version>${jbehave.version}</version>
<classifier>resources</classifier>
<type>zip</type>
</dependency>
> unpack-view-resources goal requires resources to be in compile scope
> --------------------------------------------------------------------
>
> Key: JBEHAVE-507
> URL: http://jira.codehaus.org/browse/JBEHAVE-507
> Project: JBehave
> Issue Type: Improvement
> Components: Maven Plugin
> Affects Versions: web-3.3.1
> Reporter: Caoilte O'Connor
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
