Re: Refer to the enclosing project's version in the generated archetype

Brett, That actually doesn't get translated for me (that was the first thing I tried). It shows up in the resulting pom when I generate a project from the archetype exactly as you typed it. Brett Porter wrote: version${project.version}/version -- View this message in context:

Re: Refer to the enclosing project's version in the generated archetype

Brett, Yes, I want it to be the same as the version of the archetype (I tried ${archetypeVersion}, but that stays as it is too). The archeytpe has a sibiling which is my core library. Brett Porter wrote: Sorry, I misunderstood that it was actually inside the archetype. Do you want it to

Re: Refer to the enclosing project's version in the generated archetype

Brett, I apologize, but I don't understand what you mean. When do I do the filtering? Do I need to put the pom.xml file somewhere else in my project structure? Do I just turn on filtering for the place where my pom.xml lies now? Brett Porter wrote: You are best to filter this in when

Refer to the enclosing project's version in the generated archetype

I have a project that contains a core library and a couple of archetypes that I want to use it. How do I put a dependency in my archetypes that says use the core library from the same version as me? Does that make sense? -- View this message in context:

Re: Archetype:create broken?

I'm having the same troubles. An archetype that we have used before doesn't work anymore! What's going on? nodje wrote: What's with the archetype:create? I suddenly get this error when trying to create a new project: mvn archetype:create -DgroupId=com.company.commons -DartifactId=xml