Skip to Content
Last modified by Lachlan Deck on 2009/03/24 19:05
From version 24.1
edited by Lachlan Deck
on 2009/03/24 18:40
Change comment: Reviewing and updating with helpful info, tips and links
To version 26.1
edited by Lachlan Deck
on 2009/03/24 19:02
Change comment: Extra note

Summary

Details

Page properties
Content
... ... @@ -87,7 +87,7 @@
87 87  
88 88  Java, of course, can work with anything you choose to place on your classpath. However, it's surely wise to avoid tripping yourself right?! If you're using maven to determine your classpath then I (ldeck) advise -- though nothing will stop the unwilling -- not additionally using the standard WOLips ant-based dependency management in conjunction with mavens.
89 89  
90 -That is to say, you need to understand why this would be a bad idea. Ant-based builds from wonder include their transitive dependencies in their final build; maven's do not because maven is able to resolve dependencies during your build whereas the ant-based builds won't (unless they add ivy or something similar to the mix).
90 +That is to say, you need to understand why this would be a bad idea. Ant-based builds from wonder include their transitive dependencies in their final build; maven's do not because maven is able to resolve dependencies during your build whereas the ant-based builds won't (unless they add ivy or something similar to the mix). WOLips ant-based dependency management has quite entirely different means for resolving its dependencies and as such unless you know what your doing you should avoid mixing and matching systems.
91 91  
92 92  {{/note}}
93 93