Ok but some of the dependencies on the Maven site are truly optional -jasperreports ect.
well, sorry, I was speaking for CVS Head.
For CVS Head, jasperreports is NOT optional - it must be used to compile the project. I think it could be possible - but must ask to Henner - to move the jreport servlet out of the core classes; I don't know if there are dependencies that do not permit this step.
Can we get a tab on that page saying what the jar is needed for (core dbf, devgui, jakarta tagpool, jasperreports etc). Then I will just point people to consult that list to decide what they need.
Yes, I think that:
a) we should prepare a src directory structure where core classes are separated from optional classes AND we must find a method to avoid dependencies between core and non-core classes.
b) maven deps page tells the dependencies used to build the core classes & friends
c) we could make another page to list useful links for 3rd part comnponents
Unless we decide to distribute all needed jars in a distribution. Ok legally???
Mmmm... I don't know, but I think we should check jars that came from Sun - they are distribuited using the binary license... the servlet.jar and jdbc-20-extension.jar (for jdk1.3)... other jars could be ok.
Anyway, Tomcat contains the servlet.jar library ...
Any lawyer out of here ?? ;^)
Shawn
Regards, Luca
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
