2008/3/25, stug23 <[EMAIL PROTECTED]>: > > Raphaël, > > From the transcript in JIRA ARCHETYPE-153 this appears to represent the > feature that I have requested. I wasn't able to run the example due to the > 2.0-alpha-3-SNAPSHOT which isn't in the Maven Central repository. > > If I understand what you did correctly, you simply specified an artifactId > as pro instead of proficio which should result in creating modules with the > prefix pro instead of proficio. > > It was interesting to note that although the build reports an > ArchetypeGenerationFailure, the summary still indicated a successful build?
Yup i saw this too, but i didn't yet have raised a jira for it. > > Thanks for your response! > > Is this feature very difficult to add to the archetype plugin? Nope, not really difficult, just currently bugged ;-) I am working on. Thanks, Raphaël > > > > > Raphaël wrote: > > > > Hi Pat, > > > > I created http://jira.codehaus.org/browse/ARCHETYPE-153 > > Please comment if this issue does not correspond to your issue. > > > > Regards, > > > > Raphaël > > > > 2008/3/24, stug23 <[EMAIL PROTECTED]>: > >> > >> Based on the lack of response to my posting, is this question too > >> esoteric > >> for Maven experts to answer? > >> > >> I have spent a fair amount of time learning about how to use archetypes > >> and > >> have successfully developed an archetype that uses parameter > >> substitution > >> with the Velocity templating. > >> > >> What I am seeking help with here is a way to rename the folders in the > >> archetype modules based on artifactId when the new project(s) are > >> generated > >> from the archetype. > >> > >> Can someone point me to documentation on the new archchetype NG that > >> shows > >> how to use mojos in an archetype development? > >> > >> > >> > >> stug23 wrote: > >> > > >> > I am seeking advice on how to construct an archetype for a > >> multi-module > >> > build such that the artifactId of each respective module becomes the > >> name > >> > for the module in the generated directory structure. > >> > > >> > The result I am looking for would resemble the naming conventions of > >> the > >> > Proficio multi-module project in Better Builds with Maven: > >> > > >> > proficio > >> > proficio-api > >> > proficio-cli > >> > proficio-core > >> > proficio-model > >> > proficio-stores > >> > proficio-store-memory > >> > proficio-store-xstream > >> > > >> > The intended usage of this archetype would be to create new Maven > >> > multi-module projects in Eclipse such that the project names follow > >> the > >> > convention shown in the example above. Without this project naming > >> scheme, > >> > it is quite difficult for a user to understand which projects are > >> related > >> > to a multi-module build in the Eclipse workspace. > >> > > >> > I wasn't sure whether the new archetype NG may have some feature that > >> > would help to accomplish this, or whether this requires mojos in the > >> > archetype, or if M2Eclipse can help out with this requirment. > >> > > >> > Thanks in advance for tips, pointers or advice on how to accomplish > >> this > >> > naming scheme. > >> > > >> > > >> > > >> > > >> > >> -- > >> > >> View this message in context: > >> > http://www.nabble.com/How-to-construct-an-archetype-for-multi-module-build-with-renamed-modules-tp16224882s177p16254209.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] > >> > >> > > > > > > > -- > View this message in context: > http://www.nabble.com/How-to-construct-an-archetype-for-multi-module-build-with-renamed-modules-tp16224882s177p16276697.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] > >
