Maven Archetype

Restore the ability to "package" non-Java resources

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-alpha-4
  • Fix Version/s: 2.0-alpha-1
  • Component/s: Creator
  • Labels:
    None
  • Number of attachments :
    1

Description

Some time ago, the Archetype plugin lost the ability to "package" non-Java resources. The change was committed in April '06, so it would have first appeared in 1.0-alpha-4.

http://mail-archives.apache.org/mod_mbox/maven-commits/200604.mbox/%3C20060403072414.51468.qmail@minotaur.apache.org%3E

Prior to this change, you could put non-Java files in the <sources> element, for example
<source>src/main/resources/App.properties</source>
and
mvn archetype:create ... -DgroupId=com.example
would result in
src/main/resources/com/example/App.properties

Now, you get an error saying: "Template 'App.properties' is not in directory src/main/java."

One way to fix this is to roll back the changes from lines 682-705 in r390971:
http://svn.apache.org/viewvc/maven/archetype/trunk/maven-archetype/maven-archetype-core/src/main/java/org/apache/maven/archetype/DefaultArchetype.java?r1=390965&r2=390971&diff_format=h

However if I'm reading the changes right, that will break the ability to have "sub packages".

Maybe we need to leave <sources> alone, and have both <resources> and <packagedResources> ?

There is an example project (based on the quickstart archetype) in the sandbox. It includes App.properties as described above.

http://svn.apache.org/repos/asf/maven/sandbox/trunk/archetype/maven-archetype-quickstart/

Issue Links

This issue is duplicated by:
ARCHETYPE-54 Dynamic archetype resource Major Closed
This issue relates to:
ARCHETYPE-203 resources file don't copy to the proper location Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Raphaël Piéroni added a comment -

This issue will be fixed by NG-alpha-1

Show
Raphaël Piéroni added a comment - This issue will be fixed by NG-alpha-1
Hide
Permalink
Raphaël Piéroni added a comment -

These issues are addressed since the 2.0-alpha-n version of the plugin

Show
Raphaël Piéroni added a comment - These issues are addressed since the 2.0-alpha-n version of the plugin
Hide
Permalink
Wendy Smoak added a comment -

How was this addressed? ARCHETYPE-203 implies that it was not fixed for archetype:create, but that it does work with archetype:generate.

Show
Wendy Smoak added a comment - How was this addressed? ARCHETYPE-203 implies that it was not fixed for archetype:create, but that it does work with archetype:generate.
Hide
Permalink
Raphaël Piéroni added a comment -

Yup,
I leaved this intentionnaly in archetype:create as archetype:generate encompass the archetype:create behaviour.

But it obviously works with archetype/generate and new kind of archetypes. Migrating old kind of archetypes to new kind is still to be done.

Raphaël

Show
Raphaël Piéroni added a comment - Yup, I leaved this intentionnaly in archetype:create as archetype:generate encompass the archetype:create behaviour. But it obviously works with archetype/generate and new kind of archetypes. Migrating old kind of archetypes to new kind is still to be done. Raphaël

People

Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.