ok. Thanks for your reply. I do understand that the current build setup is good. But wouldn't it be great if we have a standard build mechanism where we can make changes to the code and build it using a standard way? just run 'mvn clean install'. Also it will have a quick integration with all IDE's.
standardization reuse consistency wrt build output dependency management scalability (lower level of additional info/code to add a new step to the build process) http://maven.apache.org/benefits-of-using-maven.html On Apr 6, 11:38 am, nonlinear <[email protected]> wrote: > > Is there any plans/work-in-progress to use maven in jbooktrader? I > > believe maven is more cleaner and structured way of handling dependent > > artifacts and build. infrastructure. > > Just like Shaggs who responded above, I also don't understand the intent. > The jars (which you presumably proposing to manage via Maven) almost never > change. The build process for JBT itself is very simple and straightforward. > The dependencies never change, and there are no sub-systems to build. > > What would be the benefit of mavenizing it, then? -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.
