You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2014/09/19 18:56:33 UTC

[jira] [Commented] (OFBIZ-5779) Integrate ant build-dev target in build target

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

Jacques Le Roux commented on OFBIZ-5779:
----------------------------------------

The ant build-dev target is called by the build target an patches sources only if patch files are present in runtime/patches. So for people not interesed by this functionallity it's totally transparent.

> Integrate ant build-dev target in build target
> ----------------------------------------------
>
>                 Key: OFBIZ-5779
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5779
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Minor
>
> It's a long time this was itching me. There are several reasons why it was not there yet and few consequences.
> *Reasons*
> The main reason I did not do it already is I work on Windows, and I did not find an easy way to patch on Windows in Ant. So I was reluctant to rely on it, notably if other people would have to use it. It took me a moment to find the right way to do it with Ant. I wanted to chain the call on the build-dev target in the main build target and not being able to handle correctly on Windows was the main blockink reasons I did not do it.
> *Consequences*
> In my current custom project (still based on lively trunk HEAD), for now I had to duplicate the dev patches on other areas to have them applied there with the respectice build-* targets. 
> But I had also changes included in OFBiz OOTB code because it was simpler that way than having to duplicate in other areas, this was not good of course



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)