Hi folks, the file META-INF/maven/archetype.xml is used with the archetype plugin 1.0-alpha the 2.0-alpha version uses META-INF/maven/archetype-metadata.xml
Also the create-from-project mojo creates a correct archetype-metadata.xml but it creates a buggy archetype.xml file Hope this helps. Raphaël 2008/9/24 Niels van Kampenhout <[EMAIL PROTECTED]>: > Grzegorz Borkowski 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.) > > Try generating the archetype by running > > mvn archetype:create-from-project > > from the root of your prototype project. The generated archetype will be in > target/generated-sources/archetype/. You will probably have to fine tune a > little bit, but at least it saves you writing the file list in > archetype.xml. > >> 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? > > I can't answer that question I'm afraid -- to me the file list in > archetype.xml seems redundant as well... > > Niels > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
