Hello Sumit, Inline
Ambient Solution wrote:
Hi, I worked on offbiz for four year previously and again I started as some of my associated recomend to research on it. I am not sure whether I am asking reight quesiton here or not. Previously when I was working on offbiz to setup workspace in eclipse , its a hattick job , Setting classpath is a manual process in eclipse while for build we use ant build. Same functionality is provided by Maven which support boath IDE and duild creation . Is some one already worked on ant to Maven Migration. The benifit I seen in MVN you can set dependecy which is required for perticular project or JAR level not you have set a full folder. Second benift I found that once you setup your repository on server which is not a part of your project , It will save space on version server , Cos every new branch or project dosent require to copy all jar.
I agree that most of the things that Ant do can be done by Maven. There are following reason for not using Maven.1) Ant started in July 19, 2000 & Maven started in 2002. And we all know that OFBiz has started in 2001. At that time we were having Ant for project build purpose. All the requirements are fulfilled by Ant so nobody complained about exploring or using Maven. 2) We don't have licensing issues with either Maven or Ant as both are project of ASF. So it depend on the community members to decide what to use.
More comment from an Article available on internet : --------------------------------------------------------------Historically Ant <http://ant.apache.org/> is much older tool and it was deigned to have some Java-based build tool. Something similar to Make which most of C++ developers use. Those who worked with /Make/ probably know that is extremely powerful tool which can do whatever developer wants.
Ant is different. Instead of a model where it is extended with shell-based commands, Ant is extended using Java classes. Instead of writing shell commands, the configuration files are XML-based, The power of Ant in practice results that /you/ have to setup build process yourself. Each project can have different build process. New team members have to study /this/ version of build which is probably they used to have in /another/ project.
Maven (Maven <http://maven.apache.org/>)on another hand wants a standard way to build the projects, a clear definition of what the project consisted of, an easy way to publish project information and a way to share JARs across several projects.
*Important One :*Maven does encourage best practices and some people can prefer Ant. *Maven is less flexible than Ant *and you have to be agree with making of some compromises. ------------------------------------------------------------------
You are looking interested in exploring possibility with the Maven.I will appreciate your help in this area and you can upload the document for community at http://docs.ofbiz.org/dashboard.action.
Thanks ! -- Ashish
This process also reduce traffic on n/w at build time , Cos that time you dont have to download jar again , MVN download only new or updated jar . If is there any one who worked on the same thing , Please help me. Regards, Sumit Solution Architect +91-9221182885
smime.p7s
Description: S/MIME Cryptographic Signature
