|
As I mentioned a few times, I am concerned about the amount of jar files bundled in OFBiz: there are so many and some of them are really old and, because of dependencies and the lack of proper documentation (we did not a good job in keeping track of what we have, from where it comes and how it is used, and if bug fix releases are issued etc...) no one seems really able to manage them properly.
In order to try to gain control of the situation I have started the long, boring and complex process of analyzing each and every jar, trying to figure out their dependencies and how they are used. I am still at the early stage of this effort, but I would like to report a couple of possible issues: 1) geronimo-qname_1.1_spec-1.0.jar seems to contain the same classes of xml-apis-2.9.1.jar (javax.xml.namespace); we can probably remove geronimo-qname_1.1_spec-1.0.jar 2) juel-2.2.1.jar contains classes for the packages javax.el and de.odysseus.el; the file el-api-2.2.jar, that is required by Tomcat, contains classes for the packages javax.el; how should we deal with this? (maybe Adrian knows what to do) This is all for now, Jacopo |
|
Try removing the el-api-2.2.jar file and see what happens.
-Adrian On 4/6/2013 4:14 PM, Jacopo Cappellato wrote: > As I mentioned a few times, I am concerned about the amount of jar files bundled in OFBiz: there are so many and some of them are really old and, because of dependencies and the lack of proper documentation (we did not a good job in keeping track of what we have, from where it comes and how it is used, and if bug fix releases are issued etc...) no one seems really able to manage them properly. > In order to try to gain control of the situation I have started the long, boring and complex process of analyzing each and every jar, trying to figure out their dependencies and how they are used. > I am still at the early stage of this effort, but I would like to report a couple of possible issues: > > 1) geronimo-qname_1.1_spec-1.0.jar seems to contain the same classes of xml-apis-2.9.1.jar (javax.xml.namespace); we can probably remove geronimo-qname_1.1_spec-1.0.jar > 2) juel-2.2.1.jar contains classes for the packages javax.el and de.odysseus.el; the file el-api-2.2.jar, that is required by Tomcat, contains classes for the packages javax.el; how should we deal with this? (maybe Adrian knows what to do) > > This is all for now, > > Jacopo > |
|
All tests passed successfully after I removed it (as I was suspecting).
Should we move juel-2.2.1.jar to the j2eespecs folder? Do you have some details from where the juel-2.2.1.jar comes and from where we should take the updates? Thanks! Jacopo On Apr 6, 2013, at 5:19 PM, Adrian Crum <[hidden email]> wrote: > Try removing the el-api-2.2.jar file and see what happens. > > -Adrian > > On 4/6/2013 4:14 PM, Jacopo Cappellato wrote: >> As I mentioned a few times, I am concerned about the amount of jar files bundled in OFBiz: there are so many and some of them are really old and, because of dependencies and the lack of proper documentation (we did not a good job in keeping track of what we have, from where it comes and how it is used, and if bug fix releases are issued etc...) no one seems really able to manage them properly. >> In order to try to gain control of the situation I have started the long, boring and complex process of analyzing each and every jar, trying to figure out their dependencies and how they are used. >> I am still at the early stage of this effort, but I would like to report a couple of possible issues: >> >> 1) geronimo-qname_1.1_spec-1.0.jar seems to contain the same classes of xml-apis-2.9.1.jar (javax.xml.namespace); we can probably remove geronimo-qname_1.1_spec-1.0.jar >> 2) juel-2.2.1.jar contains classes for the packages javax.el and de.odysseus.el; the file el-api-2.2.jar, that is required by Tomcat, contains classes for the packages javax.el; how should we deal with this? (maybe Adrian knows what to do) >> >> This is all for now, >> >> Jacopo >> > |
| Free forum by Nabble | Edit this page |
