jira-importer opened a new issue, #201: URL: https://github.com/apache/maven-war-plugin/issues/201
**[Alberto Mozzone](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alberto.mozzone)** opened **[MWAR-356](https://issues.apache.org/jira/browse/MWAR-356?redirect=false)** and commented As their name implies, "archiveClasses" and "attachClasses" should avoid to put in the resulting jar the files under "src/main/resources" because: 1. they're not classes 2. they should be left in "WEB-INF/classes" 3. they could be environment dependent: via filtering, the resources in the deployed artifact could contain information which simply do not make sense in the repository (or, worse, could contain sensitive information) Of course, to preserve backward compatibility, I just suggest 2 alternatives: 1. a brand new element which joins the behavior of "archiveClasses" and "attachClasses" (e. g. "packageClasses/deployClasses") and a sibling element "packageResources" which puts the resources in a jar file in "WEB-INF/lib", but not in the repo 2. a new option used by the two elements which activates the new behavior. I'm assuming that the properties in subject should behave the same to avoid differences in artifact naming or content; see also [MWAR-215](https://issues.apache.org/jira/browse/MWAR-215). --- **Affects:** 2.6 **Attachments:** - [mwar-356-test.zip](https://issues.apache.org/jira/secure/attachment/12787902/mwar-356-test.zip) (_1.99 kB_) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
