[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] Best practices for includes resources outside of project base directory
|
Any final word on this? Should this be considered a feature or a bug?
/Collin
On Wed, Sep 12, 2012 at 10:06 PM, Collin Peters
<cpeters@xxxxxxxxxxxxxxxxxxx> wrote:
Bringing new meaning to the words "late reply" :)
Thanks for the link Fred. If I take that that directory [1] and import into Eclipse I get the same warning: "Access "/home/collin/code/m2e-test/mid/web/../../resource" directory outside of project base directory. (org.apache.maven.plugins:maven-war-plugin:2.1.1:war:default-war:package)"
Everything still works, just an annoying warning. Any way of squashing that warning?
--
Collin Peters
cpeters@xxxxxxxxxxxxxxxxxxx
(206) 855-6656 (Direct Line)
On Sun, Oct 16, 2011 at 10:54 PM, Fred Bricon
<fbricon@xxxxxxxxx> wrote:
Can you try using <directory>${basedir}/../../sql</directory>, this scenario is tested in m2e-wtp : https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp.tests/projects/WebResourceFiltering/top/mid/web/pom.xml
Regards,
Fred Bricon
2011/10/17 Collin Peters
<cpeters@xxxxxxxxxxxxxxxxxxx>
I have a Maven war project which includes the following for including some resources
<webResources>
<!-- Include SQL for dbmaintain -->
<webResource>
<directory>../../sql</directory>
<targetPath>WEB-INF/sql</targetPath>
<includes>
<include>**/*.sql</include>
</includes>
</webResource>
<!-- Include compiled reports -->
<webResource>
<directory>../../reports</directory>
<targetPath>WEB-INF/reports</targetPath>
<includes>
<include>**/*.jasper</include>
<!-- Include XSLT for reports -->
<include>**/*.xslt</include>
</includes>
</webResource>
</webResources>
This has always worked fine in Maven (2 & 3) as well as the old m2eclipse. The new m2e complains with "Access "/home/collin/Code/intouch.git/java/intouch-webapp/../../reports" directory outside of project base directory"
I know Maven is convention over configuration but this is just forcing convention. To me, putting all my Jasper reports and application SQL inside <root>/java/webapp/src/main/reports instead of <root>/reports is just silly.
What are the best practices for dealing with resources that should be included in a WAR, but just don't make sense to include inside the actual Java webapp project
Regards,
Collin
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
--
"Have you tried turning it off and on again" - The IT Crowd
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
