No longer possible to place non-Java resources into package structure
---------------------------------------------------------------------
Key: ARCHETYPE-53
URL: http://jira.codehaus.org/browse/ARCHETYPE-53
Project: Maven Archetype
Issue Type: Bug
Reporter: Wendy Smoak
>From a thread on [EMAIL PROTECTED] This used to work, and I could put (for
>example) .properties files into
>src/main/resources/org/example/myapp/Bundle.properties .
On 9/3/06, tm jee <[EMAIL PROTECTED]> wrote:
> Is there a way allow resource generated by maven archetype to change
> dynamically.
...
> The files under the generated resources directory seems to be static. It
> doesn't seems to change accordingly with the -DgroupId argument passed in. Is
> there a way to configured it to change according to the groupId?
Apparently not. In a prior version of Maven Archetype, you could put non-Java
files in the <sources> section, and it would put them in the
proper package structure.
There are some notes in the Shale Blank archetype.xml file [1].
<!-- The next line causes an error with 'mvn archetype:create':
Embedded error: Template 'src/main/resources/Bundle.properties'
not in directory 'src/main/java' -->
<!--source>src/main/resources/Bundle.properties</source-->
...
<!-- See above, but here, Bundle.properties
does not get placed in the package structure -->
<resource>src/main/resources/Bundle.properties</resource>
[1]
http://svn.apache.org/repos/asf/shale/maven/trunk/archetypes/shale-archetype-blank/src/main/resources/META-INF/archetype.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
