Mavenizing jbooktrader

[Sudarson]

HI All,
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.

I will be more than willing to work on that if I get a green signal
from the project owners.

[ShaggsTheStud]

What is the point?  Sorry, I am just clueless here.

--
You received this message because you are subscribed to the Google Groups "JBookTrader" group.
To post to this group, send email to jbook...@googlegroups.com.
To unsubscribe from this group, send email to jbooktrader...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.

[nonlinear]

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?

 

[Sudarson]

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

[John Smith]

Yep, I had to follow the 20 steps word file to have my eclipse env ready. Now how I do that for netbeans or IntellijIDEA. It's not that straightforward.

If you had the project mavenized, I just could have checked out the project in any IDE with a maven plugin, applied it maven dependencies management and right clicked on the commited run configuration and ready to go.

[John Smith]

Yeah, you should use SVN too :)

[Judson Wilson]

On Fri, Jun 10, 2011 at 2:41 PM, John Smith <hum...@gmail.com> wrote:

Yeah, you should use SVN too :)

Yeah, we use Eclipse and Hg because, well, they are better ;)  Definately the case for Hg.

[nonlinear]

Yeah, we use Eclipse and Hg because, well, they are better ;)  Definately the case for Hg.

I personally prefer IntellijJIdea to Eclipse, but that aside, it should take no longer than 10 minutes to set up JBookTrader in any IDE. Maven is intended for managing and reducing complexity, but in the case of JBT, it would actually add complexity.

[John Smith]

Well I mavenized the project locally on my comp. It adds a little
complexity but you feel at home instantly and is future proof.

I should try Hg.

On Jun 10, 11:57 pm, nonlinear <eugene.kono...@gmail.com> wrote:
> > Yeah, we use Eclipse and Hg because, well, they are better ;)  Definately
> > the case for Hg.
>
> I personally prefer IntellijJIdea to Eclipse, but that aside, it should take

> no longer than 10 minutes to set up JBookTrader in *any *IDE. Maven is

[John Smith]

Basically I renamed the source folder to src.

Created a pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://
www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>JBookTrader</groupId>
<artifactId>JBookTrader</artifactId>
<version>8.0.7-SNAPSHOT</version>
<packaging>jar</packaging>
<dependencies>
<dependency>
<groupId>commons-net</groupId>
<artifactId>commons-net</artifactId>
<version>2.0</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.5</version>
</dependency>
<dependency>
<groupId>ibapi</groupId>
<artifactId>ibapi</artifactId>
<version>9.63</version>
<scope>system</scope>
<systemPath>${basedir}/lib/ibapi-9.63.jar</systemPath>
</dependency>
<dependency>
<groupId>jcalendar</groupId>
<artifactId>jcalendar</artifactId>
<version>1.3.3</version>
<scope>system</scope>
<systemPath>${basedir}/lib/jcalendar-1.3.3.jar</systemPath>
</dependency>
<dependency>
<groupId>jfree</groupId>
<artifactId>jcommon</artifactId>
<version>1.0.16</version>
<scope>system</scope>
<systemPath>${basedir}/lib/jcommon-1.0.16.jar</systemPath>
</dependency>
<dependency>
<groupId>jfree</groupId>
<artifactId>jfreechart</artifactId>
<version>1.0.13</version>
<scope>system</scope>
<systemPath>${basedir}/lib/jfreechart-1.0.13.jar</systemPath>
</dependency>
</dependencies>
</project>

deleted libs that are on remote repositories and kept in the lib
folder thoses that are not.

Also added a JBookTrader.launch in the run folder:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration
type="org.eclipse.jdt.launching.localJavaApplication">
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS">
<listEntry value="/JBookTrader/src/com/jbooktrader/platform/startup/
JBookTrader.java"/>
</listAttribute>
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
<listEntry value="1"/>
</listAttribute>
<listAttribute key="org.eclipse.jdt.launching.CLASSPATH">
<listEntry value="&lt;?xml version=&quot;1.0&quot;
encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?
&gt;&#13;&#10;&lt;runtimeClasspathEntry
containerPath=&quot;org.eclipse.jdt.launching.JRE_CONTAINER/
org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/
JavaSE-1.6&quot; javaProject=&quot;JBookTrader&quot; path=&quot;
1&quot; type=&quot;4&quot;/&gt;&#13;&#10;"/>
<listEntry value="&lt;?xml version=&quot;1.0&quot;
encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?
&gt;&#13;&#10;&lt;runtimeClasspathEntry
id=&quot;org.eclipse.jdt.launching.classpathentry.defaultClasspath&quot;&gt;&#13;&#10;&lt;memento
exportedEntriesOnly=&quot;false&quot; project=&quot;JBookTrader&quot;/
&gt;&#13;&#10;&lt;/runtimeClasspathEntry&gt;&#13;&#10;"/>
<listEntry value="&lt;?xml version=&quot;1.0&quot;
encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?
&gt;&#13;&#10;&lt;runtimeClasspathEntry internalArchive=&quot;/
JBookTrader/resources&quot; path=&quot;3&quot; type=&quot;2&quot;/
&gt;&#13;&#10;"/>
</listAttribute>
<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER"
value="org.maven.ide.eclipse.launchconfig.classpathProvider"/>
<booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH"
value="false"/>
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE"
value="com.jbooktrader.platform.startup.JBookTrader"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS"
value="${project_loc}"/>
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR"
value="JBookTrader"/>
<stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER"
value="org.maven.ide.eclipse.launchconfig.sourcepathProvider"/>
<booleanAttribute key="org.eclipse.jdt.launching.STOP_IN_MAIN"
value="true"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-
Xmx512M"/>
</launchConfiguration>