Re: Preventing Inclussion of Multiple Versions
Wes Wannemacher wrote: > > If you find some inconsistencies, let me know and I'll fix them up, > Thank you! I appreciate the offer and will get back to you if I find any. I switched to org.freemarker, and realized tabletags was the oddball and excluded freemarker:freemarker from that. Problem solved! Wes Wannemacher wrote: > > On Wednesday 08 July 2009 13:52:59 daniel.green wrote: >> daniel.green wrote: >> > Apparently struts2-core is bringing in org.freemarker:freemarker >> >> And, uh, struts2-annotations (1.0.2) is bringing in >> freemarker:freemarker...!? You think they'd remain consistent >> > > I'm jumping in late (sorry), so I didn't see the original pom file. Why > are you > bringing in such an old struts2-annotations? I'm pretty sure I did some > work > on that recently and it has a later version. > > If you find some inconsistencies, let me know and I'll fix them up, I'm > gearing > up to roll another release in the near future, which includes (among other > things) updates to dependencies that we haven't touched in a while > (commons- > logging and things like that). > > -Wes > > -- > Wes Wannemacher > Author - Struts 2 In Practice > Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more > http://www.manning.com/wannemacher > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/Preventing-Inclussion-of-Multiple-Versions-tp24392573p24426841.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Preventing Inclussion of Multiple Versions
On Wednesday 08 July 2009 13:52:59 daniel.green wrote: > daniel.green wrote: > > Apparently struts2-core is bringing in org.freemarker:freemarker > > And, uh, struts2-annotations (1.0.2) is bringing in > freemarker:freemarker...!? You think they'd remain consistent > I'm jumping in late (sorry), so I didn't see the original pom file. Why are you bringing in such an old struts2-annotations? I'm pretty sure I did some work on that recently and it has a later version. If you find some inconsistencies, let me know and I'll fix them up, I'm gearing up to roll another release in the near future, which includes (among other things) updates to dependencies that we haven't touched in a while (commons- logging and things like that). -Wes -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Preventing Inclussion of Multiple Versions
AFAIK full domain name is always preferred, so org.freemarker (which is a valid domain in reverse) is prefered over freemarker -Stephen 2009/7/8 daniel.green : > > Apparently struts2-core is bringing in org.freemarker:freemarker (one of the > redundant), while freemarker:freemarker is being brought in as a dependency > from something else... Is there a better way then just excluding the > requirement in the dependency tag? > > I'm maintaining an onsite repository, as a business requirement we can only > use that to provide artifacts. Which is preferred, org.freemarker or > freemarker? > > > Wayne Fay wrote: >> >>> extract the ear my project generates I'm discovery multiple versions of >>> the >>> same artifacts. What's going on? Is there anyway to fix this? I thought >>> maven did dependency mediation >> >> It does. What projects are giving you multiple versions? Maven does >> not handle when artifacts "move" (change groupId) very well, so you'll >> get 2 versions of some artifacts since they moved from version 1.2 to >> 1.4 etc. >> >> Wayne >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> > > -- > View this message in context: > http://www.nabble.com/Preventing-Inclussion-of-Multiple-Versions-tp24392573p24396182.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Preventing Inclussion of Multiple Versions
daniel.green wrote: > > Apparently struts2-core is bringing in org.freemarker:freemarker > And, uh, struts2-annotations (1.0.2) is bringing in freemarker:freemarker...!? You think they'd remain consistent daniel.green wrote: > > Apparently struts2-core is bringing in org.freemarker:freemarker (one of > the redundant), while freemarker:freemarker is being brought in as a > dependency from something else... Is there a better way then just > excluding the requirement in the dependency tag? > > I'm maintaining an onsite repository, as a business requirement we can > only use that to provide artifacts. Which is preferred, org.freemarker or > freemarker? > > > Wayne Fay wrote: >> >>> extract the ear my project generates I'm discovery multiple versions of >>> the >>> same artifacts. What's going on? Is there anyway to fix this? I thought >>> maven did dependency mediation >> >> It does. What projects are giving you multiple versions? Maven does >> not handle when artifacts "move" (change groupId) very well, so you'll >> get 2 versions of some artifacts since they moved from version 1.2 to >> 1.4 etc. >> >> Wayne >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> > > -- View this message in context: http://www.nabble.com/Preventing-Inclussion-of-Multiple-Versions-tp24392573p24396188.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Preventing Inclussion of Multiple Versions
Apparently struts2-core is bringing in org.freemarker:freemarker (one of the redundant), while freemarker:freemarker is being brought in as a dependency from something else... Is there a better way then just excluding the requirement in the dependency tag? I'm maintaining an onsite repository, as a business requirement we can only use that to provide artifacts. Which is preferred, org.freemarker or freemarker? Wayne Fay wrote: > >> extract the ear my project generates I'm discovery multiple versions of >> the >> same artifacts. What's going on? Is there anyway to fix this? I thought >> maven did dependency mediation > > It does. What projects are giving you multiple versions? Maven does > not handle when artifacts "move" (change groupId) very well, so you'll > get 2 versions of some artifacts since they moved from version 1.2 to > 1.4 etc. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/Preventing-Inclussion-of-Multiple-Versions-tp24392573p24396182.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Preventing Inclussion of Multiple Versions
> extract the ear my project generates I'm discovery multiple versions of the > same artifacts. What's going on? Is there anyway to fix this? I thought > maven did dependency mediation It does. What projects are giving you multiple versions? Maven does not handle when artifacts "move" (change groupId) very well, so you'll get 2 versions of some artifacts since they moved from version 1.2 to 1.4 etc. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Preventing Inclussion of Multiple Versions
I have made sure that the parent project dictates the versions through dependencyManagement, and none of the children specify versions, yet when I extract the ear my project generates I'm discovery multiple versions of the same artifacts. What's going on? Is there anyway to fix this? I thought maven did dependency mediation -- View this message in context: http://www.nabble.com/Preventing-Inclussion-of-Multiple-Versions-tp24392573p24392573.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
