search

zhoupan / jmesa

Automatically exported from code.google.com/p/jmesa
0 stars 0 forks source link

org.apache.poi:poi dependency should be declared as optional #297

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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.

Original issue reported on code.google.com by ssla...@gmail.com on 3 Nov 2010 at 3:52

GoogleCodeExporter commented 9 years ago 
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.

Original comment by ssla...@gmail.com on 3 Nov 2010 at 4:06

GoogleCodeExporter commented 9 years ago 
This sounds reasonable to me...I will look into it.

Original comment by jeff.johnston.mn@gmail.com on 4 Nov 2010 at 9:29