You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Erwan de FERRIERES (Commented) (JIRA)" <ji...@apache.org> on 2012/04/12 18:45:19 UTC

[jira] [Commented] (OFBIZ-4803) Improve Eclipse integration

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

Erwan de FERRIERES commented on OFBIZ-4803:
-------------------------------------------

Please Francis keep the issues where they belong, it will be easier to manage them.
Also, who patched the jar ? Is it the jackrabbit team or you ? Maybe it would be better updating jackrabbit to 2.4.1 if the bugs are corrected instead of patching a jar.

Regards,
                
> Improve Eclipse integration
> ---------------------------
>
>                 Key: OFBIZ-4803
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4803
>             Project: OFBiz
>          Issue Type: Improvement
>          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, ofbiz-eclipse.patch
>
>
> Hi
> I suggest to improve the integration of ofbiz under Eclipse by adding 4 lauching configurations:
> tools/ofbiz.start
> tools/ofbiz.stop
> tools/ofbiz.status
> tools/ofbiz.test
> The ofbiz.start has the specific JVM  property DEBUG set to the value of "eclipse" -DDEBUG=eclipse so that all ofbiz jars located under each build/lib won't be loaded/added to the classpath. This will allow to continue producing all ofbiz jars with the build.xml while allowing hot replacement of classes when running under the Eclipse's debug launcher.
> Also, I added to this issue a patched version of the jackrabbit-core-2.3.3.jar that should replace the one in the framework/jcr/lib to avoid the jdbc driver exception: See https://issues.apache.org/jira/browse/JCR-3288
> Hope this help

--
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