tag:blogger.com,1999:blog-19517292.post74461776641304338..comments2024-03-19T04:05:21.564+01:00Comments on One Jar To Rule Them All: Que Rabia Que Ternura Ser El Sol Y La Luna Esto Es Una Locura Lo Que Siento MujerAlexhttp://www.blogger.com/profile/11632964711752480304noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-19517292.post-13429623489180453992011-03-23T20:19:23.560+01:002011-03-23T20:19:23.560+01:00Hi,
Why not use Maven archetype ?
This is the best...Hi,<br />Why not use Maven archetype ?<br />This is the best way as the user can configure exactly the project when creating it for example using the artifactId in the scm url etc.<br /><br />What Mirko is talking about is dependencyManagement (providing a default version for dependencies thus eliminating the risk of incoherence in dependency version between projects)ehsavoiehttps://www.blogger.com/profile/15310007753097500007noreply@blogger.comtag:blogger.com,1999:blog-19517292.post-40643105453208712052011-03-23T19:21:23.790+01:002011-03-23T19:21:23.790+01:00Thank you Mirko for your comment, but in my case t...Thank you Mirko for your comment, but in my case this is difficult because one day I am developing a project using iBatis, and the other one Hibernate. For that reason simply I just don't want to create dependencies in parent pom. Anyway what you tell us is so interesting.<br /><br />Thank you very much,Alexhttps://www.blogger.com/profile/11632964711752480304noreply@blogger.comtag:blogger.com,1999:blog-19517292.post-81719955973297929542011-03-22T21:52:46.808+01:002011-03-22T21:52:46.808+01:00Hello,
I like to define as well to provide stand...Hello,<br /><br />I like to define as well to provide standard versions for dependencies. So individual projects do not need to define versions. <br /><br />Regards<br />MirkoMirkohttps://www.blogger.com/profile/15357555770760554778noreply@blogger.com