Return-Path: 
 <dev-return-64353-apmail-ofbiz-dev-archive=ofbiz.apache.org@ofbiz.apache.org>
X-Original-To: apmail-ofbiz-dev-archive@www.apache.org
Delivered-To: apmail-ofbiz-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 21F989BC3
	for <apmail-ofbiz-dev-archive@www.apache.org>;
 Sun,  1 Apr 2012 12:50:49 +0000 (UTC)
Received: (qmail 34280 invoked by uid 500); 1 Apr 2012 12:50:48 -0000
Delivered-To: apmail-ofbiz-dev-archive@ofbiz.apache.org
Received: (qmail 34253 invoked by uid 500); 1 Apr 2012 12:50:48 -0000
Mailing-List: contact dev-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ofbiz.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ofbiz.apache.org>
List-Post: <mailto:dev@ofbiz.apache.org>
List-Id: <dev.ofbiz.apache.org>
Reply-To: dev@ofbiz.apache.org
Delivered-To: mailing list dev@ofbiz.apache.org
Received: (qmail 34244 invoked by uid 99); 1 Apr 2012 12:50:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Apr 2012 12:50:48 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Apr 2012 12:50:47 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 69D45352133
	for <dev@ofbiz.apache.org>; Sun,  1 Apr 2012 12:50:27 +0000 (UTC)
Date: Sun, 1 Apr 2012 12:50:27 +0000 (UTC)
From: "Hans Bakker (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: dev@ofbiz.apache.org
Message-ID: 
 <1317041230.3079.1333284627450.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1724438508.27630.1332920476901.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (OFBIZ-4765) build.xml in hot-deploy
 folder is not called correctly in the main build.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Hans Bakker edited comment on OFBIZ-4765 at 4/1/12 12:48 PM:
-------------------------------------------------------------

as i mentioned before build.xml should be optional both in the component as in the hot-deploy directory similar to component-load.xml

Regards,
Hans
                
      was (Author: hansbak):
    Is there any relation to a possible component-load.xml file in hot-deploy which also allows a certain sequence.....

as i mentioned before build.xml should be optional

Regards,
Hans
                  
> build.xml in hot-deploy folder is not called correctly in the main build.xml
> ----------------------------------------------------------------------------
>
>                 Key: OFBIZ-4765
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4765
>             Project: OFBiz
>          Issue Type: Wish
>    Affects Versions: SVN trunk
>            Reporter: Markus M. May
>            Priority: Minor
>             Fix For: SVN trunk
>
>         Attachments: OFBIZ-4765-fix-buildxml.patch, OFBIZ-4765-use-hotdeploy-buildxml-if-available.patch
>
>
> In the current build.xml in the ofbiz-Home-folder, the build target is executed for each subdirectory (framework, application, specialpurpose) with the fileset: 
> <filelist dir="." files="specialpurpose/build.xml"/>
> Only for the hot-deploy folder the fileset is quite different:
> <fileset dir="${basedir}/hot-deploy" casesensitive="no">
>    <exclude name="disabled/**"/>
>    <include name="*/build.xml"/>
> </fileset>
> This is calling the build.xml directly in the hot-deploy components, which is an error, if you do have several dependent components in there, which needs to get build in the right order. I propose to use the following filelist:
> <filelist dir="." files="hot-deploy/build.xml"/>
> Problem could be, that not every project do have an build.xml file in this folder (or is this already a requirement?). If it is not then we would need to check, if this build.xml is there, then execute this, and otherwise use the already existing one.
> A patch will be applied for the first solution.

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