dog nose created MNG-5704:
-----------------------------
Summary: Resource Processing: Change to included files?
Key: MNG-5704
URL: https://jira.codehaus.org/browse/MNG-5704
Project: Maven
Issue Type: Bug
Components: Bootstrap & Build
Affects Versions: 3.2.3
Reporter: dog nose
Priority: Minor
Until a few weeks ago, I used our profiles with just directory instructions.
This seems to have stopped working. Today I encountered a post about the very
same Issue on stackoverflow - my answer to explicitly include the files seems
to have resolved the Issue.
For reference:
http://stackoverflow.com/questions/26497522/maven-3-2-3-fails-to-import-resources-correctly
So the question that arises: Is this a bug or a (undocumented) feature / change?
---
When providing a profile like
{code}
<profile>
<id>dev</id>
<build>
<resources>
<resource>
<directory>src/main/config/local</directory>
</resource>
</resources>
</build>
</profile>
{code}
Maven will not correctly process all the elements inside that folder, unless an
explicit *include* instruction has been given.
I encountered this Issue along with *filtering* resources, but the above linked
post shows the same problem (and solution) even without filtering of resources.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
