Dev - Jar files that doesn't seem to be used
Locked
Dev - Jar files that doesn't seem to be used
 
|
Re: Dev - Jar files that doesn't seem to be used
|
|
Re: Dev - Jar files that doesn't seem to be used
|
|
Re: Dev - Jar files that doesn't seem to be used
|
|
In that case unless there is a license issues with Tidy we might as well keep it... I think there are a few others that we don't really need so much, but they might be convenient for some... I don't know. Some of these do have code that refers to them but it is not used unless configuration changes are made. It would be nice to have less libraries to maintain (and to download for those getting OFBiz, or when we do releases...). 1. base/lib/scripting/js.jar: we originally considered this for the UI level scripting tool, but BSH performs MUCH better and has some nice flexibilities in other ways (even if they didn't like our changes to more easily cache interpreted scripts... maybe in the future still... whatever the case we really aren't using the js.jar any more) 2. base/lib/scripting/jruby.jar: I don't think we have ever used this, and may never, so yeah might as well toss it for now until we do (been sitting so long we'll have to update before using anyway...) Side note: I would like to keep jython.jar as we will be using it for automated testing to run test scripts generated by PushToTest TestMaker. 3. framework\webapp\lib\MinML2.jar: this may be used by something, but it may just be one of the reporting libraries, like DataVistion; on that topic, the UomReport was really only a demo of DataVision, so I don't know if there is any reason to keep it, for now JasperReports seems to have won out, though it is LGPL so we are going to have to remove it from the build and pull the jars anyway... so, let's toss DataVision for now too 4. jetty: there isn't a license issue here and this is a pretty nice servlet container, but after some initial difficulties the Tomcat stuff is working great and this probably not being very well maintained; I say we keep the wrapper classes and demo config files, but remove the jars and just not build the jetty component 5. xapool.jar: we don't really need or use this (tried early on but there were too many bugs with it, so we're using an old version of Minerva that we maintain; on this topic... we should check out Geronimo and such now that it's available) and it is LGPL, so we might as well toss it 6. velocity: we decided a long time ago to go with FreeMarker instead of Velocity, but we do have some support out of the box for Velocity... is anyone using this? should we keep it, or have the wrappers not built by default and toss it? 7. jxunit and jxweb: these are fairly nice tools that Brett Palmer built some stuff on a while back, but the JXUnit and JXWeb stuff hasn't really been actively maintained so using it is difficult and hasn't really caught on for that reason; the license isn't a problem (BSD), but we are kind of going in a different direction with testing to hopefully stimulate activity in that area Okay, I guess this is the main stuff for now... There are a bunch of little ones in there that we might be able to toss, but I guess we'll get into that later. -David On Jan 28, 2006, at 7:45 AM, Al Byers wrote: > Jacopo, > > I used Tidy in the Undersun documentation site, and I think I thought > that it was going to be used more places in the content management > system. It probably, will be, but we can put it back when it is. > > -Al > > Jacopo Cappellato wrote: > >> Hi, >> >> I think that the following jar files are not actually used in OFBiz: >> >> base\lib\scripting\jruby.jar >> base\lib\Tidy.jar >> framework\webapp\lib\MinML2.jar >> >> I have removed them from my local copy and then built OFBiz >> without errors. >> >> Can we remove them? >> >> Jacopo >> >> _______________________________________________ >> Dev mailing list >> [hidden email] >> http://lists.ofbiz.org/mailman/listinfo/dev >> >> >> > > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
smime.p7s (3K)
Re: Dev - Jar files that doesn't seem to be used
|
|
Re: Dev - Jar files that doesn't seem to be used
Administrator
|
Re: Dev - Jar files that doesn't seem to be used
|
Administrator
|
Re: Dev - Jar files that doesn't seem to be used
|
|
Re: Dev - Jar files that doesn't seem to be used
|
|
In reply to this post by Jacopo Cappellato
This is a good idea in general, and something that I started a long time ago in the Best Practices Guide (on the ofbiz.org web site) for the more technical things, though deployment stuff is a different issue. Also some quick comments on there where there may be some misunderstanding: On Jan 30, 2006, at 3:54 AM, Jacopo Cappellato wrote: > Reporting engine: > > - screenfop is the official tool > - JasperReport, DataVision are optional tools The screen to FOP to PDF stuff isn't really for reporting. It is an ideal tool for printed collateral where you need good control over the layout of the page and so on, but it isn't really much of a reporting tool per se... JasperReport is probably the best option we have for reporting right now, but it is LGPL licensed so we can't include it by default. DataVision is interesting, but while it has matured over the years I really haven't evaluated it in a long time. > Database: > > - Derby is the default db (jar files are included) for demo/ > development > - Hsql, Postgres, MySQL, Axion etc... are available solutions > > Servlet Container: > > - Tomcat is the default container > - Jetty is optional > > Scripting: > > - BeanShell is the official language > - js, Velocity, JRuby are optional having some support for it, we don't have full infrastructure, like an extensions library for it and such). -David _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - Jar files that doesn't seem to be used
|
|
Re: Dev - Jar files that doesn't seem to be used
|
|
For now I have left hsqldb in, but I would like to get this issue resolved and then possibly toss hsqldb as well (and just have derby in by default). If I remember right you only had this problem with derby after applying a certain patch, but that patch was necessary to get this to work right with Postgres? Does this problem come up in the EE unit tests? -David On Jan 31, 2006, at 10:30 AM, Si Chen wrote: > Hi everybody - I was out for the weekend and just read through this. > Can we keep at least both hsql and derby in? > > (The reason has to do with a long-running blob/binary issue which was > solved with hsql/postgresql but then broke on derby for me. If you'd > like, I can go into it some more.) > > Thanks, > > Si > > David E. Jones wrote: > >> >> This is a good idea in general, and something that I started a long >> time ago in the Best Practices Guide (on the ofbiz.org web site) for >> the more technical things, though deployment stuff is a different >> issue. >> >> Also some quick comments on there where there may be some >> misunderstanding: >> >> >> On Jan 30, 2006, at 3:54 AM, Jacopo Cappellato wrote: >> >>> Reporting engine: >>> >>> - screenfop is the official tool >>> - JasperReport, DataVision are optional tools >> >> >> The screen to FOP to PDF stuff isn't really for reporting. It is an >> ideal tool for printed collateral where you need good control over >> the layout of the page and so on, but it isn't really much of a >> reporting tool per se... >> >> JasperReport is probably the best option we have for reporting right >> now, but it is LGPL licensed so we can't include it by default. >> DataVision is interesting, but while it has matured over the years I >> really haven't evaluated it in a long time. >> >>> Database: >>> >>> - Derby is the default db (jar files are included) for demo/ >>> development >>> - Hsql, Postgres, MySQL, Axion etc... are available solutions >>> >>> Servlet Container: >>> >>> - Tomcat is the default container >>> - Jetty is optional >>> >>> Scripting: >>> >>> - BeanShell is the official language >>> - js, Velocity, JRuby are optional >> >> >> Velocity is more of an alternative to FreeMarker (though in spite of >> having some support for it, we don't have full infrastructure, like >> an extensions library for it and such). >> >> -David >> >> --------------------------------------------------------------------- >> --- >> >> >> _______________________________________________ >> Dev mailing list >> [hidden email] >> http://lists.ofbiz.org/mailman/listinfo/dev >> > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - Jar files that doesn't seem to be used
|
|
Re: Dev - Jar files that doesn't seem to be used
|
|
Re: Dev - Jar files that doesn't seem to be used
|
|
| Free forum by Nabble | Edit this page |