Hi,
I've written a tool that we're considering open sourcing, and I'm curious to
gauge how much interest there would be in it.
The purpose of the tool is to generate proper poms for each of the ofbiz
modules by inspecting an ofbiz directory. It works in two steps, and it uses
the Nexus search
I know various people have expressed interest in Maven over the years. From a
quick search I see such discussions going back to 2003!
OFBiz would definitely benefit from more modularization, and Maven may be able
to help with that. However, it is just a tool and would still require
significant
Hi,
One other point: this tool is currently useful against ofbiz "as-is", in order
to build software that depends on it, using maven. Converting ofbiz to use
maven is a considerably bigger project.
On 13 Jul 2011, at 15:01, David E Jones wrote:
>
> I know various people have expressed intere
Is part of the intent to use the Maven release plugin for deployment and such
as well?
-David
On Jul 13, 2011, at 3:12 PM, Eric Bowman wrote:
> Hi,
>
> One other point: this tool is currently useful against ofbiz "as-is", in
> order to build software that depends on it, using maven. Conver
Yes. We version our changes of ofbiz in a mavenesque way, and intend to use
the maven release plugin to generate releases which get "deployed" (in maven
terminology) to a repository, from which they get deployed to real servers.
On 13 Jul 2011, at 15:18, David E Jones wrote:
>
> Is part of th
This is an interesting idea, and there seem to be a number of plugins for Maven
that deal with release/build/deploy automation.
Looking around to learn more about this I found this interesting intro
presentation that talks about the Maven release plugin, plus plugins for other
tools like Codeh
Hi David, hi Eric,
first: cool tool Eric would love to see it!
I worked a lot with maven in the last year and must say it is pretty amazing
how easy thinks can be when you follow the convention over configuration
pattern. There are plenty of plugins which support you by
building/deploying/organiz
Yes, that's the point, I strong recommend migrate the build system to
maven, it's very handy to build/development/deploy/release with maven
since there is lots of plugins can be use, and you also can write your
plugin if possible. Just as Sascha mentioned, IMHO,
1. Maven follow the convention
I used Maven Ant Tasks in the development of new OFBiz applications.
The Maven Ant Tasks allow some of the Maven's artifact handling
features including the dependency management to be used from within
the Ant build.
So this could be an option for those who wants to use POM to manage
the dependenci
There's an ivy.xml file in the root of ofbiz trunk. Ant+Ivy seems to
be better alternative.
Since we have all the build.xml ready, the only thing we need is to
declare the dependencies using ivy. For this to work, components
build.xml files need to be modified to install the resulting jar files
in
To manage modularity have the same thin than Mansour.
On neogia addons librairy, we analysed maven and ivy. We use ivy
directly call by the addon manager system.
An example with a hat addon crm to resolve addon dependencies :
dependencies tree as resoled by ivy for the addon : neogia-crm
n
Hi,
I've placed "mavenizer" on github: https://github.com/ebowman/mavenizer
I wouldn't say it's too polished yet, so if anyone wants to be an early
adopter, much appreciated.
Note that you will need a Nexus installation nearby for this to be much use.
cheers,
Eric
On 12 Jul 2011, at 12:09, E
12 matches
Mail list logo
