[
https://issues.apache.org/jira/browse/OFBIZ-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528535#comment-14528535
]
Adam Heath commented on OFBIZ-6271:
-----------------------------------
Um, do you fully understand maven? This is not the right approach.
Maven has a distribute mirror network; your suggestion of an ofbiz-hosted
private repo would preclude that.
Ofbiz is no different than any other big project, why do you think INFRA would
allow us to host this repo?
When defining a dependency in a pom, it's possible to tell maven to *not* pull
in *any* transitive deps, or to override the version of a dep, or to exclude
just one transitive dep.
Also, a private external repo is not needed. I already have the
currently-checked-in jar files being used, without defining a top-level
<repository> in a pom. Plus, having a top-level repository defined is very
much bad form.
There are so many things wrong with your paragraph, do you actually understand
what maven can actually do?
> 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)
