Hello,
I came up with a fix for
https://issues.apache.org/jira/browse/OFBIZ-12660 ("I" becomes "ı" -
dotless "i" - if locale = AZ or TR, which breaks a Less file path). I
opened a PR : https://github.com/apache/ofbiz-framework/pull/521.
Basically, after lowerca
:
This is an automated email from the ASF dual-hosted git repository.
jleroux pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git
The following commit(s) were added to refs/heads/trunk by this push:
new aab412b Improved: Fix some bug
e.org/repos/asf/ofbiz-framework.git
The following commit(s) were added to refs/heads/trunk by this push:
new aab412b Improved: Fix some bugs Spotbugs reports (OFBIZ-12386)
aab412b is described below
commit aab412b94827e4fcc8c79f7d6ecb528f8695862b
Author: Jacques Le Roux
AuthorDate: Sun
I mentioned this in the user list a week and a half ago, but I am going to
start working on making the build possible for JDK 13. There was already an
open issue for JDK 11 and I looked at that. It looks like the one issue I
am seeing with JDK 13 is the same thing.
I look forward to working with y
Thanks, Jacopo!
Will amend my fix versions.
Michael
Am 24.02.20 um 15:56 schrieb Jacopo Cappellato:
Hi Michael,
I have just created the version in Jira for 17.12.02: we should now use it.
Thanks,
Jacopo
On Mon, Feb 24, 2020 at 3:42 PM Michael Brohl
wrote:
Hi all,
how do set the "
Hi Michael,
I have just created the version in Jira for 17.12.02: we should now use it.
Thanks,
Jacopo
On Mon, Feb 24, 2020 at 3:42 PM Michael Brohl
wrote:
> Hi all,
>
> how do set the "fixed versions" in the case of a pending release like we
> have with 17.12.01 now?
>
> IMO 17.12.01 would b
I should have mentioned that there is no 17.12.02 release available at
the moment, therefore I chose the Release Branch.
The provided link does not seem to be related to my particular question
though.
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 24.02.20 um 15:52 schrieb Pierre Smits:
M
As an addendum to my previous posting regarding 'Project following that
methodology often have a release branch for the next release.'
In this case 'r17.12.01' so that there is an alignment between ticket and
repository.
Met vriendelijke groet,
Pierre Smits
*Proud* *contributor** of* Apache OFB
Michael, all,
It is very common that when an issue is identified for a particular release
(in this case 17.12.01) that, when fixed, the 'version field' is set to the
next version (to be released). That way, when the moment of releasing the
next release comes around, tickets can be identified. And
Reference to the issue where I selected "Release branch 17.12":
https://issues.apache.org/jira/browse/OFBIZ-11346
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 24.02.20 um 15:42 schrieb Michael Brohl:
Hi all,
how do set the "fixed versions" in the case of a pending release like
we have wi
Hi all,
how do set the "fixed versions" in the case of a pending release like we
have with 17.12.01 now?
IMO 17.12.01 would be wrong because it was tagged before and the change
would go to 17.12.02. In some case at the weekend I selected "Release
Branch 17.12" but not sure about it.
Curren
Nicolas Malin writes:
> Effectively, good point to make more attention on the future.
>
> I'm not sure that I can amend this commit without make a push force
> after, so I prefer to keep this error instead generate more
> inconvenient.
Indeed that was my suggestion to follow this convention in y
es Le Roux wrote:
Le 07/12/2019 à 16:06, Mathieu Lirzin a écrit :
Hello Nico,
nma...@apache.org writes:
commit 071a74238b4d53fb95ffd214e0e68e55840a28e3
Author: Nicolas Malin
AuthorDate: Fri Dec 6 21:29:01 2019 +0100
Fixed: Fix missing else during previous refactoring
(OFBIZ-
Le 07/12/2019 à 16:06, Mathieu Lirzin a écrit :
Hello Nico,
nma...@apache.org writes:
commit 071a74238b4d53fb95ffd214e0e68e55840a28e3
Author: Nicolas Malin
AuthorDate: Fri Dec 6 21:29:01 2019 +0100
Fixed: Fix missing else during previous refactoring
(OFBIZ-11253)
When you
Hello Nico,
nma...@apache.org writes:
> commit 071a74238b4d53fb95ffd214e0e68e55840a28e3
> Author: Nicolas Malin
> AuthorDate: Fri Dec 6 21:29:01 2019 +0100
>
> Fixed: Fix missing else during previous refactoring
> (OFBIZ-11253)
> When you rendering for with auto
a issue Dennis created a few
> months ago [1]. The CompDoc functionality of the content manager has
> several bugs and does not seem to work properly. We should discuss if we
> either
>
> a. fix these bugs and make the funtionality work properly? or
>
> b. remove the functi
t;> months ago [1]. The CompDoc functionality of the content manager has
> >> several bugs and does not seem to work properly. We should discuss if we
> >> either
> >>
> >> a. fix these bugs and make the funtionality work properly? or
> >>
> >> b. remove the functionality?
> >>
> >> What are your thoughts?
> >>
> >> Thanks and regards,
> >>
> >> Michael
> >>
> >> [1] https://issues.apache.org/jira/browse/OFBIZ-10476
> >>
> >>
> >>
>
CompDoc functionality of the content manager has
several bugs and does not seem to work properly. We should discuss if we
either
a. fix these bugs and make the funtionality work properly? or
b. remove the functionality?
What are your thoughts?
Thanks and regards,
Michael
[1] https://issues.apa
ompDoc functionality of the content manager has
> several bugs and does not seem to work properly. We should discuss if we
> either
>
> a. fix these bugs and make the funtionality work properly? or
>
> b. remove the functionality?
>
> What are your thoughts?
>
Hi all,
I'd like to drag your attention to the Jira issue Dennis created a few
months ago [1]. The CompDoc functionality of the content manager has
several bugs and does not seem to work properly. We should discuss if we
either
a. fix these bugs and make the funtionality work properl
ssues arise in webPos due to POS removing
new issues will be created
> Check if we should fix or remove the POS (hence WebPos?)
>
>
> Key: OFBIZ-7804
> URL: https://issues.apache.org/ji
able at https://svn.code.sf.net/p/xui/code/xui
I wanted to push the all XUI sources in the OFBiz repo to be sure it will stay
available but with the MOZILLA PUBLIC LICENSE this is impossible. So I'll kep
what I have and we will see, anyway I think the POS will stay as is...
> Check if we s
ity as long as we are not sure it works as expected!
> Check if we should fix or remove the POS (hence WebPos?)
>
>
> Key: OFBIZ-7804
> URL: https://issues.apache.org/jira/browse/OFBIZ-7804
eate a new Jira for that, but I'll wait
webpos experienced users's opinions because there is information here that I
don't want to copy/paste "there"
> Check if we should fix or remove the POS (hence WebPos?)
>
o be sure this is still working as it was before
removing the POS and I'm unable to confirm that, having never worked with the
webpos.
> Check if we should fix or remove the POS (hence WebPos?)
>
>
>
[
https://issues.apache.org/jira/browse/OFBIZ-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-7804:
--
Assignee: (was: Jacques Le Roux)
> Check if we should fix or remove the POS (he
nd people can jump in when needed at
a later stage to improve and fine-tune the requirements for WebPOS. So if no
one objects I think it is safe to perhaps close this JIRA and leave it for
others to take initiatives in the future.
> Check if we should fix or remove the POS (
from real webpos users, because I never got to
get this to work as I expected, so I guess users know better than me.
> Check if we should fix or remove the POS (hence WebPos?)
>
>
> Key: OFBIZ-7804
>
code.
And sincerely, it's maybe because I knew it by heart, but I found the POS UI
easier to use than the webPos one.
> Check if we should fix or remove the POS (hence WebPos?)
>
>
> Key: OFBIZ-7804
>
rces available so I will put all what I have
in repo before removing the component. At some point I created my own XUI
version but the authors fixed it after. I must also say that we had then any
issues with XUI and it's still working perfectly for the POS.
> Check if we should fix or re
nts to use the
POS or (why not?) revive it, it's will still be possible.
Note that the POS uses XUI which is no longer maintained (since 2008) and the
POS has not changed for years, my last effort was in end of 2009.
> Check if we should fix or remove
the rest could have an impact on the WebPos,
but I so far found not evidences, testing will say it!
> Check if we should fix or remove the POS (hence WebPos?)
>
>
> Key: OFBIZ-7804
> URL: https:
the Jars for the POS component since they
are used for the UI which is not used in web pos
> Check if we should fix or remove the POS (hence WebPos?)
>
>
> Key: OFBIZ-7804
> URL: https://iss
[
https://issues.apache.org/jira/browse/OFBIZ-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-7804:
---
Summary: Check if we should fix or remove the POS (hence WebPos?) (was:
Check if we should
[
https://issues.apache.org/jira/browse/OFBIZ-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-7804:
--
Assignee: Jacques Le Roux
> Check if we should fix or remove the POS (hence web
d on the user ML after a discussion on dev ML
http://markmail.org/message/oaqxcxsrlfbiid24
I'm still not sure if removing the POS has an influence on the WebPos. I'll
check that when removing the POS...
> Check if we should fix or remove the
s.le.roux):
It seems indeed that nobody is really interest by maintaing the POS so we
should move it in Attic. I'f though start a thread on the user ML to be sure
nobody potentially interested misses the notification. A simple link to the
decv ML should be sufficient.
> Check if we should
ally interest by maintaing the POS so we
should move it in Attic. I'f though start a thread on the user ML to be sure
nobody potentially interested misses the notification. A simple link to the
decv ML should be sufficient.
> Check if we should fix or remove the POS (
FBIZ-7924 right?
> Check if we should fix or remove the POS (hence webpos)
> ---
>
> Key: OFBIZ-7804
> URL: https://issues.apache.org/jira/browse/OFBIZ-7804
> Project: OFBiz
>
out filling the
> "Fix Versions/s" field in Jira
>
> Please read
> https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=7766050&selectedPageVersions=46&selectedPageVersions=45
>
> Thanks
>
> Jacques
>
>
Thanks Jacques for the update :)
Gil
Le 18/07/2016 à 18:16, Jacques Le Roux a écrit :
Hi Committer, Devs, All,
You might have noticed I Temporary changed our policy about filling
the "Fix Versions/s" field in Jira
Please read
https://cwiki.apache.org/conflu
Thanks Jacques for update.
Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
On Mon, Jul 18, 2016 at 9:46 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Hi Committer, Devs, All,
>
> You might have noticed I Temporary changed our policy about filling th
Hi Committer, Devs, All,
You might have noticed I Temporary changed our policy about filling the "Fix
Versions/s" field in Jira
Please read
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=7766050&selectedPageVersions=46&selectedPageVersions=45
Thanks
Jacques
tyGlAccounts
5. ListTaxAuthorityRateProducts
6. ListTaxAuthorityParties
TransactionForms.xml
1. ViewGatewayResponsePayments
> Add paginate target to list forms to fix the pagination error
> -
>
> Key: OFBIZ-7362
> U
I
close here
> Fix or remove scripts in tools folder
> -
>
> Key: OFBIZ-7774
> URL: https://issues.apache.org/jira/browse/OFBIZ-7774
> Project: OFBiz
> Issue Type: Sub-task
>
t this
bq. I think the issue with POS happened after the first commit which introduced
remote libraries. So it is one of those "jar dependency hell" problems. It is a
good idea either way to remove it from the start component and fix it outside
with its own bootstrapping code away
Jacques Le Roux created OFBIZ-7804:
--
Summary: Check if we should fix or remove the POS (hence webpos)
Key: OFBIZ-7804
URL: https://issues.apache.org/jira/browse/OFBIZ-7804
Project: OFBiz
e rc scripts are a bit more important than just convenient.
We're not doing an end-user product, but a business product used by
organisations and supported in managed environments. You're suggesting that
each instance deployed is managed only by hands?
> Fix or remove script
Jacques Le Roux created OFBIZ-7774:
--
Summary: Fix or remove scripts in tools folder
Key: OFBIZ-7774
URL: https://issues.apache.org/jira/browse/OFBIZ-7774
Project: OFBiz
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey updated OFBIZ-7381:
-
Sprint: Community Day 2 - 2016
> Fix 'requestitems' target fr
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey resolved OFBIZ-7381.
--
Resolution: Fixed
Fix Version/s: Upcoming Branch
Thanks [~chandan.khandelwal] for
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey closed OFBIZ-7381.
> Fix 'requestitems' target fr
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey updated OFBIZ-7381:
-
Summary: Fix 'requestitems' target from order menu (was: Fix
'requestitems
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-7381:
Description:
Go To Order > Request > ViewRequest > RequestItems
Need to fix incorrect t
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Khandelwal updated OFBIZ-7381:
--
Attachment: OFBIZ-7381.patch
> Fix 'requestitems' target fr
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Khandelwal updated OFBIZ-7381:
--
Attachment: (was: OFBIZ-7381.patch)
> Fix 'requestitems' target fr
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Khandelwal updated OFBIZ-7381:
--
Component/s: order
> Fix 'requestitems' target fr
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Khandelwal updated OFBIZ-7381:
--
Affects Version/s: Trunk
> Fix 'requestitems' target fr
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Khandelwal updated OFBIZ-7381:
--
Description:
Go To Order > Request > ViewRequest > RequestItems
Need to fix
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey reassigned OFBIZ-7381:
Assignee: Pranay Pandey (was: Chandan Khandelwal)
> Fix 'requestitems' targ
[
https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Khandelwal updated OFBIZ-7381:
--
Attachment: OFBIZ-7381.patch
> Fix 'requestitems' target fr
Chandan Khandelwal created OFBIZ-7381:
-
Summary: Fix 'requestitems' target from order menu.
Key: OFBIZ-7381
URL: https://issues.apache.org/jira/browse/OFBIZ-7381
Project: OFBiz
way in already 3 issues I know OFBIZ-7067,
OFBIZ-6547 and OFBIZ-5634
> Add paginate target to list forms to fix the pagination error
> -
>
> Key: OFBIZ-7362
> URL: https://issues.apache.or
lack the parameter 'paginate-target' and that
makes the URL accepting parameters from the form instead of passing them to the
request parameters ?
> Add paginate target to list forms to fix the pagination error
> -
>
tickets
will be added in it for various components.
> Add paginate target to list forms to fix the pagination error
> -
>
> Key: OFBIZ-7362
> URL: https://issues.apache.org/jira/browse/OFBIZ-736
have the same error message ?
> Add paginate target to list forms to fix the pagination error
> -
>
> Key: OFBIZ-7362
> URL: https://issues.apache.org/jira/browse/OFBIZ-7362
>
Amardeep Singh Jhajj created OFBIZ-7362:
---
Summary: Add paginate target to list forms to fix the pagination
error
Key: OFBIZ-7362
URL: https://issues.apache.org/jira/browse/OFBIZ-7362
Project
pati].
> Fix different forms, screens and services affected due to removal of
> parentTypeId from "PURCHASE_INVOICE" and "SALES_
runk and R15.12 already passed. I wait for the
rest before closing OFBIZ-7147, thanks Anurag and Arun!
> Fix different forms, screens and services affected due to removal of
> parentTypeId from "PURCHASE_INVOICE" and "SALES_
[
https://issues.apache.org/jira/browse/OFBIZ-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Patidar closed OFBIZ-7201.
---
Resolution: Fixed
Fix Version/s: 13.07.04
15.12.01
[
https://issues.apache.org/jira/browse/OFBIZ-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Chandak reassigned OFBIZ-7201:
-
Assignee: Arun Patidar (was: Anurag Chandak)
> Fix different forms, screens
[
https://issues.apache.org/jira/browse/OFBIZ-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Chandak updated OFBIZ-7201:
--
Attachment: OFBIZ-7201.patch
> Fix different forms, screens and services affected due
[
https://issues.apache.org/jira/browse/OFBIZ-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Chandak updated OFBIZ-7201:
--
Attachment: (was: OFBIZ-7147.patch)
> Fix different forms, screens and services affec
review it and let me know if you
have any queries.
> Fix different forms, screens and services affected due to removal of
> parentTypeId from "PURCHASE_INVOICE" and "SALES_INVO
Arun Patidar created OFBIZ-7201:
---
Summary: Fix different forms, screens and services affected due to
removal of parentTypeId from "PURCHASE_INVOICE" and "SALES_INVOICE" InvoiceType
data.
Key: OFBIZ-7201
[
https://issues.apache.org/jira/browse/OFBIZ-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313918#comment-15313918
]
Deepak Dixit commented on OFBIZ-7164:
-
This has been fixed at r#1746691
&
[
https://issues.apache.org/jira/browse/OFBIZ-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Dixit closed OFBIZ-7164.
---
Resolution: Fixed
Fix Version/s: Upcoming Branch
> Fix incorretly clsoed else tag in
Deepak Dixit created OFBIZ-7164:
---
Summary: Fix incorretly clsoed else tag in ftl
Key: OFBIZ-7164
URL: https://issues.apache.org/jira/browse/OFBIZ-7164
Project: OFBiz
Issue Type: Bug
[
https://issues.apache.org/jira/browse/OFBIZ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divesh Dutta updated OFBIZ-7102:
Fix Version/s: Upcoming Branch
> Fix the Approve button label for newly added item to the exist
[
https://issues.apache.org/jira/browse/OFBIZ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divesh Dutta closed OFBIZ-7102.
---
> Fix the Approve button label for newly added item to the existing
the issue and thanks [~Mohammad K] for
providing the patch. Your patch is committed in revision 1744948 in trunk.
> Fix the Approve button label for newly added item to the existing PO
>
>
>
[
https://issues.apache.org/jira/browse/OFBIZ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divesh Dutta reassigned OFBIZ-7102:
---
Assignee: Divesh Dutta
> Fix the Approve button label for newly added item to the exist
[
https://issues.apache.org/jira/browse/OFBIZ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Kathawala updated OFBIZ-7102:
--
Attachment: OFBIZ-7102-trunk.patch
Changed the Button Label to 'Approve Item&#x
nges required to fix this issue. UI label
needs to be change from "Approve Order" to "Approve Item" which is misleading
the user.
> Fix the Approve button label for newly added item to the existing PO
> --
for orders approved? Have we considered
the effect on forecasts, payments, accounting transactions, etc?
> Fix the Approve button label for newly added item to the existing PO
>
>
> Key: OFBIZ-7102
>
[
https://issues.apache.org/jira/browse/OFBIZ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ratnesh Upadhyay updated OFBIZ-7102:
Attachment: ApproveButtonLabel.png
> Fix the Approve button label for newly added item
Ratnesh Upadhyay created OFBIZ-7102:
---
Summary: Fix the Approve button label for newly added item to the
existing PO
Key: OFBIZ-7102
URL: https://issues.apache.org/jira/browse/OFBIZ-7102
Project
[
https://issues.apache.org/jira/browse/OFBIZ-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-6936:
---
Fix Version/s: (was: Release Branch 15.12)
(was: Release Branch
[
https://issues.apache.org/jira/browse/OFBIZ-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brohl closed OFBIZ-6972.
Resolution: Fixed
This is fixed in
trunk r1737631.
> Fix resource leaks in CommonServices.j
[
https://issues.apache.org/jira/browse/OFBIZ-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223031#comment-15223031
]
Jacques Le Roux commented on OFBIZ-6972:
+1 (only reviewed)
> Fix resourc
hing works, I believe you can safely commit your work
here.
> Fix resource leaks in CommonServices.java
> -
>
> Key: OFBIZ-6972
> URL: https://issues.apache.org/jira/browse/OFBIZ-6972
> Project:
the general the feedback was that this
change was very straightforward so please feel free to go ahead and commit it.
Thanks
> Fix resource leaks in CommonServices.java
> -
>
> Key: OFBIZ-6972
> URL: https://iss
[
https://issues.apache.org/jira/browse/OFBIZ-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharan Foga updated OFBIZ-6972:
---
Sprint: Re-Factor Sprint 1
> Fix resource leaks in CommonServices.j
the Re-Factor To Do List - I've
asked the team if anyone wants to review it before commit.
> Fix resource leaks in CommonServices.java
> -
>
> Key: OFBIZ-6972
> URL: https://issues.apache.or
> Fix resource leaks in CommonServices.java
> -
>
> Key: OFBIZ-6972
> URL: https://issues.apache.org/jira/browse/OFBIZ-6972
> Project: OFBiz
> Issue Type: Improvement
>
Michael Brohl created OFBIZ-6972:
Summary: Fix resource leaks in CommonServices.java
Key: OFBIZ-6972
URL: https://issues.apache.org/jira/browse/OFBIZ-6972
Project: OFBiz
Issue Type
Christian Geisert created OFBIZ-6936:
Summary: Fix broken 'run-test-list' target
Key: OFBIZ-6936
URL: https://issues.apache.org/jira/browse/OFBIZ-6936
Project: OFBiz
Issue
[
https://issues.apache.org/jira/browse/OFBIZ-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Geisert closed OFBIZ-6936.
> Fix broken 'run-test-list' target
> -
>
&g
[
https://issues.apache.org/jira/browse/OFBIZ-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Geisert resolved OFBIZ-6936.
--
Resolution: Fixed
Fixed with rev 1735250
> Fix broken 'run-test-list
4.12 r1735250
R13.07 r1735285
R12.04 r1735286
> Fix broken 'run-test-list' target
> -
>
> Key: OFBIZ-6936
> URL: https://issues.apache.org/jira/browse/OFBIZ-6936
> Project: OFBiz
> Is
1 - 100 of 586 matches
Mail list logo
