TiborVyletel / fitnesse-launcher-maven-plugin

Automatically exported from code.google.com/p/fitnesse-launcher-maven-plugin
0 stars 0 forks source link

<useProjectDependencies> ignores <optional>true</optional> #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. My specific setup involved spring-orm.
2. It depends on many jars, most of them <optional>
3. Hibernate 3 and 4 are included. But both are <optional>. Since <optional> is 
ignored by <useProjectDependencies>, both of these jars are in my classpath. 
Neither should be.

What is the expected output? What do you see instead?
To only have required jars in the fitnesse classpath. All jars, <optional> or 
not.

What version of the product are you using? On what operating system?
Latest. Windows and Linux.

Please provide any additional information below.
At first I thought it was due to me not understanding compile, runtime, system, 
test... But no. I tried every combination. "compile" should work, but it gets 
too many jars.

Too many jars!!!

Original issue reported on code.google.com by charlesn...@gmail.com on 1 Apr 2014 at 4:14

GoogleCodeExporter commented 9 years ago
Possibly we also need a way to specify exclusions also ...

Original comment by stewart@javahelp.co.uk on 9 Jun 2014 at 9:25

GoogleCodeExporter commented 9 years ago
Fixed on /trunk for 1.4.0. Public SNAPSHOT updated.

Mojo property fitnesse.excludeOptionalDependencies controls excluding of 
optional dependencies. Defaults to true.

Significant reduction in number of jars on the FitNesse classpath :-)

Original comment by stewart@javahelp.co.uk on 9 Jun 2014 at 1:55