[ https://issues.apache.org/jira/browse/OFBIZ-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527418#comment-14527418 ]
Adam Heath commented on OFBIZ-6271: ----------------------------------- Yes, no, both. I want maven to be have the ability to call load-demo, create-tenant, etc. I want ant to be able to call into maven, for the actual build. So, as a plan, the special non-build targets in the top-level build.xml get extracted out, to be placed into a single file, shared by both build systems. Then, both systems can call into this shared file. For a time, both build systems are maintained in parallel, with mostly identical features. This to give developers a time to acclimate. After a time, switch ant to call into maven for the build targets, but still leave the targets in build.xml. Add a deprecation message. Even more time, remove the build.xml from all of ofbiz. > 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)