[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255388#comment-13255388
 ] 

Jacopo Cappellato commented on OFBIZ-4812:
------------------------------------------

Francis,

Sascha explained some of the motivations pretty well.
In addition to this I would like to add:
1) we should limit as much as possible to commit code for making it compliant 
with IDEs; for example I don't like the code that Jacques committed in rev. 
1308085 and not much the code committed in rev. 1326300
2) running OFBiz in Eclipse is not the best way to run it; you can do if you 
like and it works but if it is causing problems you should use ant or the shell;
3) we should always use officially released jars from other projects; using a 
patched version (that doesn't even convince the committers of the other 
project) is not ok, especially if the reason is to make of biz compatible with 
an IDE



                
> Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
> component
> --------------------------------------------------------------------------------
>
>                 Key: OFBIZ-4812
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: framework
>    Affects Versions: SVN trunk
>         Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
>            Reporter: Francis ANDRE
>         Attachments: jackrabbit-core-2.3.3.jar
>
>
> Hi
> When running ofbiz under Eclipse with the sources directories as classpath 
> and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
> because jackrabbit-core is using Class.forName() instead of using the current 
> classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
> I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
> the JCR-3288 issue.
> Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to