Hello Eugene, About the upgrade of the dependencies (not only velocity): i started to upgrade each dependency to newer versions, wherever this didn't break the build. But don't worry, i plan to replace velocity with groovy templates ;-)
About Jdom vs Dom4j, i don't remember exactly, maybe i use two libraries that each call one. About standadization, If anyone is interested to provide a patch on the whole archetype sources... Regards, Raphaël 2008/10/13 Eugene Kuleshov <[EMAIL PROTECTED]>: > > Raphaël, > > May I ask what was the reason to update velocity version used by > archetype-common from 1.4 to 1.5? Is there some known issues or the only > reason is to use the latest version? Velocity 1.5 is bigger and it have more > dependencies. We will have to submit separate IP review for each 3rd party > library required for Maven integration for Eclipse and it would be great to > minimize those dependencies. > > I also wonder why archetype-common need both jdom and dom4j libraries? It > is really odd to have two different xml framework. Generally I think it > would be a great idea to standardize on xml framework across all Maven > projects/plugins, at least those hosted at Apache and perhaps Codehaus Mojo > project > > What do you think? > > Eugene > > > > Raphaël wrote: >> >> Here i come to talk a little about the next features of the archetype >> plugin. >> >> First I would like to have some samples updated to the new archetype >> way of doing. For this step, i will need some sample projects to start >> from. This is an unshamed ask for pepople to provide some simple >> project :-) >> Here is the list of projects i will add for the next release: >> - quickstart >> - mojo >> - webapp >> - jee >> >> quickstart will be a mono module hello world library. >> mojo will provide a mono module hello wolrd goal. >> webapp will be a mono module hello world servlet. >> jee will be a multi module complete jee5 stack. with a library, an >> ejb, a servlet. Can someone give me this kind of project based on >> glassfish v3? >> I have the ability to create the 3 first samples ;-) >> >> I also plan to give some partial archetypes samples: >> - site >> - jnlp >> - izpack >> >> site will add a simple site on an existing maven project. >> jnlp will add the usage of the jnlp plugin (hoping it exists) on an >> existing maven project. Can anyone provide me a simple project for >> this ? >> izpack will add the usage of the izpack installer on top of a maven >> project. >> I have the ability to create site and izpack, but dunno anything on jnlp. >> >> Please provide me any advice on the way to achieve this... >> >> >> Second, I would like to have a programmatic way to call a maven goal >> on another project from inside a goal run from a project. For example, >> calling the deploy phase on a newly created archetype at the end of >> create-from-project. >> Of course, such a deploy should have to find the deployment >> information outside of the newly created archetype. >> Can anyone tell me where the release plugin works in calling the spawn >> maven build on the checkouted project. >> >> Thanks in advance for any advice/help. >> >> Regards, >> >> Raphaël >> > > -- > View this message in context: > http://www.nabble.com/-archetypes--future-features-tp19942462p19948184.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
