[
https://jira.codehaus.org/browse/MNG-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354742#comment-354742
]
dog nose edited comment on MNG-5704 at 10/21/14 6:38 PM:
---------------------------------------------------------
Sidenode: I also noticed that only *building from the command prompt* fails -
eclipse was able to build the project correctly, when directly deploying to the
(Wildfly-8.1)-Server added.
We have been able to reproduce this for 3 different profiles: Command line
fails (*mvn -f [pathToPom] clean install -P [profilename]*), eclipse suceeds.
(I don't know if Eclipse uses a dedicated, internal version of Maven that might
not have been updated along with the local installation.)
was (Author: dognose):
Sidenode: I also noticed that only *building from the command prompt* fails -
eclipse was able to build the project correctly, when directly deploying to the
(Wildfly-8.1)-Server added.
We have been able to reproduce this for 3 different profiles: Command line
fails (*mvn -f [pathToPom] clean install -P [profilename]*), eclipse suceeds.
(I don't know if Eclipse uses an dedicated, internal version of Maven that
might not have been updated along with the local installation.)
> 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.
> Side
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
