[
https://issues.apache.org/jira/browse/OFBIZ-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527421#comment-14527421 ]
Adam Heath commented on OFBIZ-6271:
-----------------------------------
I also struggled with moving the list of tasks from top-level build.xml into some piece of compiled code. However, those top-level tasks are really short scriptlets, batch files, shell scripts, whatever. So, making full-on java code doesn't really work either, and would be harder to maintain(in theory).
This is still a bit of an open-ended issue.
And, honestly, now that I am here, I'm actually kind of curious about that other elephant, aka, gradle.
> build management with maven
> ---------------------------
>
> Key: OFBIZ-6271
> URL:
https://issues.apache.org/jira/browse/OFBIZ-6271> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Reporter: Adam Heath
> Priority: Minor
> Attachments: console.log
>
>
> This is a new build system; the primary goal will be to not require any changes to existing ofbiz layouts(for backwards compatibility, at least initially).
> These pom.xml files are completely new; the existing build.xml infrastructure will continue to exist. The existing build.xml will never call into maven(which is what processes the pom.xml), and maven will never call into build.xml either.
> I have already committed a working pom.xml for the top level, and framework/start. Shortly, I will be adding framework/base and framework/entity, but into this branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
