maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MCOMPILER-54) Cannot include non ".java" file via <includes> configuration
Date Sat, 27 Aug 2011 11:27:32 GMT

     [ https://jira.codehaus.org/browse/MCOMPILER-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte closed MCOMPILER-54.
-----------------------------------

    Resolution: Not A Bug

Non-java sources should be placed under {{src/main/resources}} or a custom location specified
in de {{pom.xml}} in the {{<project><build><resources>}}-section as described
[here|http://maven.apache.org/pom.html#Resources].
These (re)sources don't need to be compiled, but belong on the classpath. The [maven-resources-plugin|http://maven.apache.org/plugins/maven-resources-plugin/]
is responsible for this action.

> Cannot include non ".java" file via <includes> configuration
> ------------------------------------------------------------
>
>                 Key: MCOMPILER-54
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-54
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0, 2.0.1, 2.0.2
>         Environment: WinXP, Win2003K, JDK 5.11 (Java(TM) 2 Runtime Environment, Standard
Edition (build 1.5.0_11-b03))
>            Reporter: Dave Ousey
>            Priority: Minor
>         Attachments: quicktest.zip
>
>
> Could not get "mvn clean compile" to move a ".properties" file in source directory structure
even though appropriate <includes> configuration is specified in the POM.  Attached
is simple archetype project to demonstrate.  "app.properties" is not moved to target directory.
> Our use of MyEclipse places ".properties" resource bundle files in source directory.
I will pursue moving "properties" files to "resources" directory but expected this to work.
> I dug into the source code and problem manifests in StateSourceScanner - getIncludedSources
method.  The "scanForSources" private method correctly applies the included files but then
the subsequent "for" loop does not catch the "properties" file because the compiler plugin
only every adds a SourceMapping with a ".java" suffix.  Could not find any clear documentation
to configure this differently to get this working. 
> Got similar results with earlier versions of the plugin and with target = 1.5 and not.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message