ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-11275) bug in depends-on in ofbiz-component.xml
Date Sun, 01 Dec 2019 22:46:00 GMT

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

ASF subversion and git services commented on OFBIZ-11275:

Commit 87d7465306df2b7294587e4c0297360cf234ef92 in ofbiz-framework's branch refs/heads/trunk
from Mathieu Lirzin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=87d7465 ]

Improved: Move ‘ComponentContainerTest’ data to src/test/resources/ (OFBIZ-11275)

Remove unnecessary webapp declaration inside the test component

> bug in depends-on in ofbiz-component.xml
> ----------------------------------------
>                 Key: OFBIZ-11275
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11275
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Trunk, 18.12.01
>            Reporter: Samuel Trégouët
>            Assignee: Mathieu Lirzin
>            Priority: Major
>             Fix For: Upcoming Branch
>         Attachments: 0001-Implemented-Show-dependency-resolution-algorithm-pro.patch,
0002-Implemented-Add-a-generic-directed-graph-utilitary-c.patch, 0003-Fixed-Remove-dependency-management-from-ComponentCon.patch,
> when using `depends-on` tag in obfiz-component.xml one should expect ofbiz to load component
(and in particular container listed in ofbiz-component.xml) in particular order.
> I mean if component `accounting` has this line in its ofbiz-component.xml
> {noformat}
> <depends-on component="order" />{noformat}
> ofbiz should load order component first and then accounting. This is not the case. Only
classpath is modified according to depends-on declaration (and this is not really a usefull/used
feature but we'll see this in another issue ;) )
> So here are patches to fix this issue. First one is only a test (which is skipped to
allow ./gradlew test to be ok, so if one need to be convinced one should comment Ignore annotation)
to illustrate issue, the two others are actual fixes

This message was sent by Atlassian Jira

View raw message