No clue why it was designed like this, but at least for me, creating an archetype is not an everyday thing so its really not a big deal to spend a little extra time when I occasionally need to build a new archetype or work on an existing one.
With a little ls and sed/awk you can get all the files listed in the proper XML form right out of your command line. As with the rest of Maven, this is an open source project so you can post a JIRA and someone will consider adding the feature themselves or you can modify the code yourself and contribute it back to the project. Wayne On Tue, Sep 23, 2008 at 5:49 AM, Grzegorz Borkowski <[EMAIL PROTECTED]> wrote: > > I wanted to create my own archetype... > I've prepared set of prototype sources which should be used as tempate for > creating new project. According to document "Guide to creating archetypes" I > should put them under src/main/resources/archetype-resources/. That's ok, I > put them there. > But then the user guide says that I have to put every prototype file name > (with full path) into archetype.xml file! What for? (I gave up at this > point, it is too much unnecessary work.) > What's the point of such data redundancy? If I have the complete file > structure under src/main/resources/archetype-resources/, then maven > archetype plugin should simply copy it when creating project from archetype. > Putting the list of those files in archetype.xml is waste of time. > Can somebody explain me why it was designed so? > -- > View this message in context: > http://www.nabble.com/What%27s-the-point-of-listing-all-artifacts-in-archetype.xml--tp19626976p19626976.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
