[
https://issues.apache.org/jira/browse/MTOMCAT-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375996#comment-14375996
]
Constantino Cronemberger commented on MTOMCAT-246:
--------------------------------------------------
I managed to get it working by adding a resources declaration in a profile I
use only when running with Tomcat7 plugin:
<profile>
<!-- Enable this profile to run the application with "mvn
tomcat7:run -Pdev. -->
<id>dev</id>
<build>
<resources>
<resource><directory>instance-config/dev</directory></resource>
<resource><directory>src/main/resources</directory></resource>
</resources>
</build>
</profile>
> Allow for adding dirs/files to webapp classpath
> -----------------------------------------------
>
> Key: MTOMCAT-246
> URL: https://issues.apache.org/jira/browse/MTOMCAT-246
> Project: Apache Tomcat Maven Plugin
> Issue Type: New Feature
> Components: tomcat7
> Reporter: Ondrej Burkert
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 3.0
>
> Attachments: sample.zip
>
>
> We have projects developed using Spring. Every project has a set of
> configuration files (usually just logback configuration XML and a property
> file). They are placed on the classpath and loaded from there by Spring app
> context.
> I don't see any way to put these on the classpath with current (we try 2.1 at
> the moment) version of the plugin. Adding it using the
> additionalClasspathDirs does not work as that is apparently Tomcat's not
> application's classpath. It fails with FileNotFound exception. We place these
> in the tomcat/lib folder for regular deployments.
> Any workaround or preferably solution for the problem would be highly
> appreciated. There are couple unanswered questions in this direction on
> stackoverflow as well.
> (http://stackoverflow.com/questions/18862237/tomcat7-maven-plugin-couldnt-locate-the-property-file-on-classpath,
>
> http://stackoverflow.com/questions/17962524/extending-classpath-and-tomcat-plugin)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]