On Thu, Jul 4, 2013 at 11:14 AM, Uwe Schindler <[email protected]> wrote:
> Hi, > > I have no problem with it i fit is *not* part oft he WAR or the example > folder's lib! If it would be it would be a bug! > > In general we should split all JARs needed for "compilation" and those for > "test runtime" and "production runtime" by 3 different configurations. The > test runtime is only added to classpath when tests are ran. The production > env is used for building the webapp/example app. The compile classpath only > contains direct dependencies, no transient ones. > > See e.g. forbidden-apis as an example. It splits those classpaths > completely (and uses ivy:cachepath for classpath / ivy:cachefileset for > packaging zips). > And this is also much easier to implement if you are using ivy:cachepath/cachefileset. As long as we have lib/ directories, its harder because then we would have to add additional ones and make things more complicated. On the other hand, the cachepath/fileset is faster and does still work with IDEs (at least with intellij and eclipse IDEs it seems, but you need ivyDE).
