Issue 297: org.apache.poi:poi dependency should be declared as optional
Status:  New
Owner: ----
Reported by ssla...@gmail.com, Nov 3, 2010
What steps will reproduce the problem?
1. In a project built using Apache Maven 2+ declare dependency to org.jmesa:jmesa:3.0.1
2. Don't use exporting to pdf functionality
3.

What is the expected output? What do you see instead?
When not using jmesa's exporting to pdf functionality apache poi shouldn't be present in project's dependency set. When using export to pdf feature one would define poi as dependency. Instead, project now always receives org.apache.poi:poi as transitive dependency from jmesa dependency.

What version of the product are you using? On what operating system?
org.jmesa:jmesa:3.0.1; any OS

Please provide any additional information below.
Suggested solution: set "<optional>true</optional>" for poi dependency declaration in jmesa pom file.

Nov 3, 2010
#1 ssla...@gmail.com
While at it, upgrading to poi:3.7 could be done as well - it would remove that log4j exlusion since it's declared as optional in poi 3.7.
Nov 4, 2010
Project Member #2 jeff.johnston.mn@gmail.com
This sounds reasonable to me...I will look into it.