[
https://issues.apache.org/jira/browse/OFBIZ-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851987#action_12851987 ]
Bob Morley commented on OFBIZ-3630:
-----------------------------------
Hey Adrian, I had talked a bit with Jacques on the use of "resolved" in JIRA. The line of thinking was if a non-contributor applies a patch to a JIRA ticket that resolves the issue then they can move it to that status so that there is some distinguishing status vs. normal created JIRAs that report bugs (but have no solution). From my understanding contributors can pickup resolved (but not closed) issues to review the patch and commit it and then close the issue. I believe if everyone was ok with this it was going to be modified in the best practices.
Let's start a dialog if we think this is incorrect usage of the "resolved" status. The current best practices suggested things were moved directly to closed so it was currently not being used at all.
In this case can we just commit the patch? :)
> Fix .classpath for hamcrest.jar inclusion
> -----------------------------------------
>
> Key: OFBIZ-3630
> URL:
https://issues.apache.org/jira/browse/OFBIZ-3630> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: SVN trunk
> Reporter: Bob Morley
> Fix For: SVN trunk
>
> Attachments: OFBIZ-3630_AddHamcrestToClasspath.patch
>
>
> It appears that the hamcrest.jar has been added to help in some of the cache related unit tests. This just adds it to the .classpath so that the project can compile in Eclipse.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Locked
