ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Heath (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-6271) build management with maven
Date Mon, 04 May 2015 16:19:06 GMT

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

Adam Heath commented on OFBIZ-6271:

What Jacques is asking about, are all the other non-build targets in the build.xml.  Aka,
"load-demo", "start", etc.

I've been struggling(not with the implementation, but with the where) on how to deal with
those targets in a maven world.  Maven is a *build system*, while ant's build.xml is just
a series of commands(targets) that have names and do something, and might also require other
things to run first(depends).

There really isn't a simple way to just add callable commands to maven's pom.xml structures.
 I've played with making each called target from ant by a non-default-activated "profile".
 I then attempted to inline each target body using maven-antrun-plugin, but that was ugly.
 I then have switched to moving the special targets to a separate external build.xml snippet,
which is then called by both ant and maven.

This latter method actually seems like it would be generally useful, even without maven in
use.  Aka, the top-level build.xml, and all the internal component build.xml, should just
be for building/deploying ofbiz.  The extra cli targets at the top-level should be in a separate
location(similar to how we have that top-level tools folder).

For backwards compatibility, top-level would need to call the external targets for a time

Does that make sense?

> 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

View raw message