Re: Guide to creating archetypes...
Hi, If I want to create an archetype, which one is better to use ? what's the difference ? http://mojo.codehaus.org/maven-archetypeng/ or mvn archetype:create -DgroupId=[your project's group id] -DartifactId=[your project's artifact id] -DarchetypeArtifactId=maven-archetype-archetype (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html) Rémy
Re: Guide to creating archetypes...
2007/5/3, Rémy Sanlaville [EMAIL PROTECTED]: what's the difference ? Mainly - the descriptor is changed - user is prompted for selecting the archetype and configuration (unless using -B) - any file can be resolved as packaged (using package in the directory resolution) - any file can be resolved as binary (copied instead of velocity template) - support for multi project I forgot: - archetype creation form an existing project (yes with the above features packaged, filtered, multiproject) http://mojo.codehaus.org/maven-archetypeng/ which is not yet released Did you have a roadmap when it will be released ? I got a roadmap (on paper without any date) But i could say it need at least 2 weeks before putting a first alpha release Raphaël So, if I understand, maven-archetypeng has more features and seems more powerful. So it's better to look at maven-archetypeng instead of maven-archetype. I will have a look. I imagine it will normally replace maven-archetype in the future. or mvn archetype:create -DgroupId=[your project's group id] -DartifactId=[your project's artifact id] -DarchetypeArtifactId=maven-archetype-archetype (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html) Hope the answer makes sense Nice thanks. Rémy
Re: Guide to creating archetypes...
I'm trying to use the archetypeNG plugin from an existing complex (multi module) project. The plugins ask me for archetype groupId and other properties on every module of the source project. It generates an archetype for every module. I'd like to generate the complete project with modules from a single archetype, based on my sample project. How to do this ? Nico. 2007/5/3, Raphaël Piéroni [EMAIL PROTECTED]: 2007/5/3, Rémy Sanlaville [EMAIL PROTECTED]: what's the difference ? Mainly - the descriptor is changed - user is prompted for selecting the archetype and configuration (unless using -B) - any file can be resolved as packaged (using package in the directory resolution) - any file can be resolved as binary (copied instead of velocity template) - support for multi project I forgot: - archetype creation form an existing project (yes with the above features packaged, filtered, multiproject) http://mojo.codehaus.org/maven-archetypeng/ which is not yet released Did you have a roadmap when it will be released ? I got a roadmap (on paper without any date) But i could say it need at least 2 weeks before putting a first alpha release Raphaël So, if I understand, maven-archetypeng has more features and seems more powerful. So it's better to look at maven-archetypeng instead of maven-archetype. I will have a look. I imagine it will normally replace maven-archetype in the future. or mvn archetype:create -DgroupId=[your project's group id] -DartifactId=[your project's artifact id] -DarchetypeArtifactId=maven-archetype-archetype (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html) Hope the answer makes sense Nice thanks. Rémy
Re: Guide to creating archetypes...
Try mvn -N archetypeng:create-from-project Raphaël 2007/5/3, nicolas de loof [EMAIL PROTECTED]: I'm trying to use the archetypeNG plugin from an existing complex (multi module) project. The plugins ask me for archetype groupId and other properties on every module of the source project. It generates an archetype for every module. I'd like to generate the complete project with modules from a single archetype, based on my sample project. How to do this ? Nico. 2007/5/3, Raphaël Piéroni [EMAIL PROTECTED]: 2007/5/3, Rémy Sanlaville [EMAIL PROTECTED]: what's the difference ? Mainly - the descriptor is changed - user is prompted for selecting the archetype and configuration (unless using -B) - any file can be resolved as packaged (using package in the directory resolution) - any file can be resolved as binary (copied instead of velocity template) - support for multi project I forgot: - archetype creation form an existing project (yes with the above features packaged, filtered, multiproject) http://mojo.codehaus.org/maven-archetypeng/ which is not yet released Did you have a roadmap when it will be released ? I got a roadmap (on paper without any date) But i could say it need at least 2 weeks before putting a first alpha release Raphaël So, if I understand, maven-archetypeng has more features and seems more powerful. So it's better to look at maven-archetypeng instead of maven-archetype. I will have a look. I imagine it will normally replace maven-archetype in the future. or mvn archetype:create -DgroupId=[your project's group id] -DartifactId=[your project's artifact id] -DarchetypeArtifactId=maven-archetype-archetype (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html) Hope the answer makes sense Nice thanks. Rémy
Re: Guide to creating archetypes...
I allready tried this, but the generated archetype does not include modules (only parent pom). 2007/5/3, Raphaël Piéroni [EMAIL PROTECTED]: Try mvn -N archetypeng:create-from-project Raphaël 2007/5/3, nicolas de loof [EMAIL PROTECTED]: I'm trying to use the archetypeNG plugin from an existing complex (multi module) project. The plugins ask me for archetype groupId and other properties on every module of the source project. It generates an archetype for every module. I'd like to generate the complete project with modules from a single archetype, based on my sample project. How to do this ? Nico. 2007/5/3, Raphaël Piéroni [EMAIL PROTECTED]: 2007/5/3, Rémy Sanlaville [EMAIL PROTECTED]: what's the difference ? Mainly - the descriptor is changed - user is prompted for selecting the archetype and configuration (unless using -B) - any file can be resolved as packaged (using package in the directory resolution) - any file can be resolved as binary (copied instead of velocity template) - support for multi project I forgot: - archetype creation form an existing project (yes with the above features packaged, filtered, multiproject) http://mojo.codehaus.org/maven-archetypeng/ which is not yet released Did you have a roadmap when it will be released ? I got a roadmap (on paper without any date) But i could say it need at least 2 weeks before putting a first alpha release Raphaël So, if I understand, maven-archetypeng has more features and seems more powerful. So it's better to look at maven-archetypeng instead of maven-archetype. I will have a look. I imagine it will normally replace maven-archetype in the future. or mvn archetype:create -DgroupId=[your project's group id] -DartifactId=[your project's artifact id] -DarchetypeArtifactId=maven-archetype-archetype (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html) Hope the answer makes sense Nice thanks. Rémy
Re: Guide to creating archetypes...
Hi Dave, Currently, you can't add that folder. Please feel free to raise a Jira. Raphaël 2007/5/2, Dave Hoffer [EMAIL PROTECTED]: The process given for creating a custom archetype seems limiting and confusing. I want the standard maven directory layout but in addition I want to add higher level folders called trunk tags this way my new artifact projects will be configured correctly for VCS usage. (The maven build usage of this will be in the trunk folder so we do use the standard maven layout.) The docs say that these elements represent different sections of the project, what is not clear is if these are hard coded paths or if these have this path because the archetype descriptor defines them this way. If they are hard coded it makes no sense for the path to be included in the descriptor file, which it is. * sources = src/main/java * resources = src/main/resources * testSources = src/test/java * testResources = src/test/resources * siteResources = src/site Here is my descriptor: archetype idxrite-archetype-default/id sources sourcetrunk/src/main/java/App.java/source /sources testSources sourcetrunk/src/test/java/AppTest.java/source /testSources resources resourcetrunk/src/site/site.xml/resource resourcetrunk/src/site/apt/overview.apt/resource resourcetrunk/src/site/fml/faqs.fml/resource /resources /archetype Although my files do have this layout pattern when I run this archetype I an error Template 'trunk/src/main/java/App.java' not in directory 'src/main/java' How can I add the trunk folder? -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Guide to creating archetypes...
Can you give me a link to ...the 'next generation' archetype plugin that is going on over at Codehaus? -Dave -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 02, 2007 9:10 AM To: Maven Users List Subject: Re: Guide to creating archetypes... On 5/2/07, Dave Hoffer [EMAIL PROTECTED] wrote: The process given for creating a custom archetype seems limiting and confusing. I'd say limited and tedious. :) Although my files do have this layout pattern when I run this archetype I an error Template 'trunk/src/main/java/App.java' not in directory 'src/main/java' How can I add the trunk folder? The current archetype code won't let you. I don't think much more is going to happen with this codebase, so you might want to check out the work on the 'next generation' archetype plugin that is going on over at Codehaus and the related discussion on the dev list archives. -- Wendy - 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]
Re: Guide to creating archetypes...
On 5/2/07, Dave Hoffer [EMAIL PROTECTED] wrote: Can you give me a link to ...the 'next generation' archetype plugin that is going on over at Codehaus? http://mojo.codehaus.org/maven-archetypeng/ -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide to creating archetypes
I second that one. My biggest stumbling block so far with adopting Maven has been lack of documentation. However, I do understand how difficult it can be to get the docs written. Richard Alexander Hars wrote: Hi, Two weeks ago I wrote a significantly expanded Guide to Creating Archetypes. It was immediately posted to CVS, but it is still not available on the website. Is there some reason why the Maven2 site is not updated regularly (last update was 10/21). Shouldn't it be very easy using Maven2? I am sure that lots of improvements have been made to the documentation in the last weeks. The documentation is really essential for all us newbies to Maven2 and it would help very much if you could update the site. Thank you very much Alexander - 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]
Re: Guide to creating archetypes
maybe we can use http://wiki.apache.org/maven/ for a collaborative effort? there is no specific wiki site for maven2 but from what i can see that wiki is relatively unused by maven1. finalized documents could then be promoted to the official site as the maintainers see fit. not everybody has ready access to the development branch so i guess there will be people who will benefit in this effort. ciao! On 11/8/05, Richard Allen [EMAIL PROTECTED] wrote: I second that one. My biggest stumbling block so far with adopting Maven has been lack of documentation. However, I do understand how difficult it can be to get the docs written. Richard Alexander Hars wrote: Hi, Two weeks ago I wrote a significantly expanded Guide to Creating Archetypes. It was immediately posted to CVS, but it is still not available on the website. Is there some reason why the Maven2 site is not updated regularly (last update was 10/21). Shouldn't it be very easy using Maven2? I am sure that lots of improvements have been made to the documentation in the last weeks. The documentation is really essential for all us newbies to Maven2 and it would help very much if you could update the site. Thank you very much Alexander - 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] -- Programming, an artform that fights back Anuerin G. Diaz Registered Linux User #246176 Friendly Linux Board @ http://mandrivausers.org/index.php http://capsule.ramfree17.org , when you absolutely have nothing else better to do - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide to creating archetypes
On Tue, 2005-11-08 at 13:53 +0100, Alexander Hars wrote: Hi, Two weeks ago I wrote a significantly expanded Guide to Creating Archetypes. It was immediately posted to CVS, but it is still not available on the website. http://maven.apache.org/guides/mini/guide-creating-archetypes.html Is that not it? Is there some reason why the Maven2 site is not updated regularly (last update was 10/21). Shouldn't it be very easy using Maven2? mvn site-deploy I am sure that lots of improvements have been made to the documentation in the last weeks. It is usually deployed once a day if not more. The documentation is really essential for all us newbies to Maven2 and it would help very much if you could update the site. We usually update the site when changes are made, but like all human beings we sometimes miss things. If the guide you are referring does not have the expected content just let me know. Thank you very much Alexander - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide to creating archetypes
On Tue, 2005-11-08 at 08:02 -0500, Richard Allen wrote: I second that one. My biggest stumbling block so far with adopting Maven has been lack of documentation. However, I do understand how difficult it can be to get the docs written. If there is something lacking then it is best to use one of the four components we have for documentation: http://jira.codehaus.org/secure/BrowseProject.jspa As far as the site goes I've tried to make the first quick links give a clear path to the documentation if that is lacking just let us know: Features Download Installation Instructions Getting Started Documentation Available Plug-ins Plug-in Matrix Where is it? The plug-in matrix is particularly helpful when looking for specific things you need and we now have 34 mini guides, and 11 guides on introductory material. We can only help with users' direction. Saying there is a lack of documentation doesn't really help anyone. We need to know where it is lacking in order to fix it. Richard Alexander Hars wrote: Hi, Two weeks ago I wrote a significantly expanded Guide to Creating Archetypes. It was immediately posted to CVS, but it is still not available on the website. Is there some reason why the Maven2 site is not updated regularly (last update was 10/21). Shouldn't it be very easy using Maven2? I am sure that lots of improvements have been made to the documentation in the last weeks. The documentation is really essential for all us newbies to Maven2 and it would help very much if you could update the site. Thank you very much Alexander - 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] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide to creating archetypes
On Tue, 2005-11-08 at 15:11 +0200, Anuerin Diaz wrote: maybe we can use http://wiki.apache.org/maven/ for a collaborative effort? there is no specific wiki site for maven2 but from what i can see that wiki is relatively unused by maven1. Anyone is welcome to use the wiki but we have a decent pattern started for the doco. People can help by adding to the FAQs, creating mini guides and creating introductory guides. If they are placed in JIRA they are usually processed pretty quickly. Full documents if they are new are preferred and patches for everything else are greatly appreciated. Patches get absorbed pretty quickly. finalized documents could then be promoted to the official site as the maintainers see fit. not everybody has ready access to the development branch so i guess there will be people who will benefit in this effort. Unfortunately we don't have a very good work flow in place for this right now and JIRA is your best bet at the moment. ciao! On 11/8/05, Richard Allen [EMAIL PROTECTED] wrote: I second that one. My biggest stumbling block so far with adopting Maven has been lack of documentation. However, I do understand how difficult it can be to get the docs written. Richard Alexander Hars wrote: Hi, Two weeks ago I wrote a significantly expanded Guide to Creating Archetypes. It was immediately posted to CVS, but it is still not available on the website. Is there some reason why the Maven2 site is not updated regularly (last update was 10/21). Shouldn't it be very easy using Maven2? I am sure that lots of improvements have been made to the documentation in the last weeks. The documentation is really essential for all us newbies to Maven2 and it would help very much if you could update the site. Thank you very much Alexander - 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] -- Programming, an artform that fights back Anuerin G. Diaz Registered Linux User #246176 Friendly Linux Board @ http://mandrivausers.org/index.php http://capsule.ramfree17.org , when you absolutely have nothing else better to do - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org Three people can keep a secret provided two of them are dead. -- Unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide to creating archetypes
On 11/8/05, Jason van Zyl [EMAIL PROTECTED] wrote: On Tue, 2005-11-08 at 15:11 +0200, Anuerin Diaz wrote: maybe we can use http://wiki.apache.org/maven/ for a collaborative effort? there is no specific wiki site for maven2 but from what i can see that wiki is relatively unused by maven1. Anyone is welcome to use the wiki but we have a decent pattern started for the doco. People can help by adding to the FAQs, creating mini guides and creating introductory guides. If they are placed in JIRA they are usually processed pretty quickly. Full documents if they are new are preferred and patches for everything else are greatly appreciated. Patches get absorbed pretty quickly. finalized documents could then be promoted to the official site as the maintainers see fit. not everybody has ready access to the development branch so i guess there will be people who will benefit in this effort. Unfortunately we don't have a very good work flow in place for this right now and JIRA is your best bet at the moment. the way i see it is we can use JIRA as the official promotion vehicle. documentation could be refined in the wikis by user comments and suggestions and if no more flaws are detected then it could be submitted to JIRA for inclusion on the main site. the wiki can also be a repository of bits and pieces that are not full-bodied enough to warrant their own mini-guide (e.g. a listing of all properties that could be accessed in maven) . another advantage of this approach is that the the rough drafts can aid users find their way. although the downside is if the draft is very rough it could make learning something more difficult than it seems. just an idea. :) ciao! -- Programming, an artform that fights back Anuerin G. Diaz Registered Linux User #246176 Friendly Linux Board @ http://mandrivausers.org/index.php http://capsule.ramfree17.org , when you absolutely have nothing else better to do - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Guide to creating archetypes
2005/11/8, Jason van Zyl [EMAIL PROTECTED]: On Tue, 2005-11-08 at 13:53 +0100, Alexander Hars wrote: Hi, Two weeks ago I wrote a significantly expanded Guide to Creating Archetypes. It was immediately posted to CVS, but it is still not available on the website. http://maven.apache.org/guides/mini/guide-creating-archetypes.html Is that not it? What I miss there is what archetype.xml contains in the META-INF directory. That does not seem to get explained. regards, Wim
