plugins - this can serve as the area where the plugins for blue will reside (maybe have all plugins here - but you can choose which to build with)
docs - documentation
config - configuration files
build - the build directory
dist - the distributions that you build (multiple builds can reside here)
assemblies - this can be where Jetty and Tomcat can reside, 3rd party options for building the distributions
the rest of the files are self explanatory - except for the maven files - I think it is worth a look to be able to have the option to download plugins from a repository - if we used maven for that, may as well use it entirely.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The structure looks good. I think we should further define the src dir to separate production code from test code. A typical structure is:
src
|--> java (productiion code)
|--> test (unit tests)
From there we can have a parallel package structure so test classes actually live in the same java package as production classes. This way the tests have access to non-private members of the classes they are testing. But the source files are physically separated. This makes the build (ant/maven) a bit easier.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks a project structure, config should be etc, we need to keep that since it's more common on linux distributions. Also take a look at the nagios structure for both project and build. It should model similar, and they already have it laid out for an RPM build. Which we need to provide as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I took a look at the nagios structure for the project - perhaps we should add an html directory. Maybe later becoming a resources directory. Overall it might be easy to mimic their structure - but I am not sure it is a good fit for a port to Java.
Any direction much appreciated. As far as build - I am in the process of getting Nagios on my machine tonight - I will take a detailed look at the build.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
What do you all think about the following packaging structure:
blue
|->src
|->plugins
|->docs
|->config
|->build
|->dist
|->assemblies
LICENSE.txt
README.txt
RELEASE-NOTES-0.9.txt
maven.xml
pom.xml
project.properties
src - obviously blue source code
plugins - this can serve as the area where the plugins for blue will reside (maybe have all plugins here - but you can choose which to build with)
docs - documentation
config - configuration files
build - the build directory
dist - the distributions that you build (multiple builds can reside here)
assemblies - this can be where Jetty and Tomcat can reside, 3rd party options for building the distributions
the rest of the files are self explanatory - except for the maven files - I think it is worth a look to be able to have the option to download plugins from a repository - if we used maven for that, may as well use it entirely.
The structure looks good. I think we should further define the src dir to separate production code from test code. A typical structure is:
src
|--> java (productiion code)
|--> test (unit tests)
From there we can have a parallel package structure so test classes actually live in the same java package as production classes. This way the tests have access to non-private members of the classes they are testing. But the source files are physically separated. This makes the build (ant/maven) a bit easier.
Is this project structure or the build structure?
It looks a project structure, config should be etc, we need to keep that since it's more common on linux distributions. Also take a look at the nagios structure for both project and build. It should model similar, and they already have it laid out for an RPM build. Which we need to provide as well.
I took a look at the nagios structure for the project - perhaps we should add an html directory. Maybe later becoming a resources directory. Overall it might be easy to mimic their structure - but I am not sure it is a good fit for a port to Java.
Any direction much appreciated. As far as build - I am in the process of getting Nagios on my machine tonight - I will take a detailed look at the build.
I am still of the opinion that first a direct, working, complete port is essential. With as little differences as possible.