Hi,

I appreciate this is not really a Dukascopy issue, but I haven't found my answer on the web either.

How should I be setting up my strategies?
As per the wiki, I created a Package called My Strategies, and then I create a new java class file for each strategy. However this seems to mean that each time I am working on a strategy and then want to compile it, all the other strategies get compiled at the same time. Now I could have different versions of my strategies which would mean I could end up with 20 or more java class files.

Is that how others are doing it? Or do you create a new package for each strategy?

I just want to get an idea of the cleanest setup before I start bad habits.

thanks

Simon

1) NetBeans supports history feature: Menu -> View -> Editors -> History;

2) NetBeans supports more sophisticated versioning subsystems;

3) You can create different Maven projects (a project per a strategy) with the only parent pom file with jforex dependencies.

thanks hebasto.

The versioning/history feature is great - used it the other day.

I think I will try to have a different project then per strategy. Unless this creates a massive system resource issue in terms of space?
Is this how you have structured your strategies?
how could I use the same pom file?

Docs:
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html
https://maven.apache.org/pom.html

To create a Maven pom-packaging parent project in NetBeans:
Menu -> File -> New Project... -> Categories: Maven -> Projects: POM Project

The necessary line in a parent POM is:

<packaging>pom</packaging>

The most important lines in children POMs are the reference to their parent, e.g.:

<parent>
        <groupId>hebasto</groupId>
        <artifactId>JForex-SDK-Parent</artifactId>
        <version>1.0</version>
</parent>

Why would you need to do that?
Are you sure about this? Did you check the folder where the .class files are?

just looking for the best/neatest solution I guess.

I don't think you can compile a class file individually, so when I hit compile it compiles everything in the project folder. There could be 20 or more strategies in there. This then starts to get time consuming as it compiles each one. Or at least that seems to be what is happening in the test files i have so far.

How do you know that each of them get compiled? Did you check the creation dates of the .class files? We don't have expertise in NetBeans, but could it be that the most of the build time is due to other events, not the compilation itself? Before you create 20 projects in your workspace maybe it is worth to check the build time difference if you have 1 or 20 strategies? In our experience we use an Eclipse JForex-SDK-based project which contains more than 500 strategies and it works without any performance issues, as the Eclipse only recompiles those files which have been changed.

on further inspection you might be right. I think it was just that i had several test strategies that weren't compiled initially.

I am not a Netbeans user, but I think every IDE out there have a Build, and a Build All commands.
Build only compiles files that have been edited recently (since the last Build). (This is sometimes referred as Make.)
Build All compiling every file in the package.

Does this make any sense?

yup thanks