jboss-benchmark project - standalone?

[tom.elrod]

Wanted to know if the jboss-benchmark project in CVS is going to be treated as a standalone project? If so, is it alright to add the needed libraries for this project? Also, will this project be using the new jboss build in the future?

Thanks.

-Tom

[clebert.suconic]

My initial though was to be a standalone project. My idea was to redistribute JARS. Like in the jboss-4.0/testsuite we would add it in the classpath.

And about the buildsuite, we can use it of course, unless we find any issues.


-Clebert

[tom.elrod]

If you are going to make it standalone, would certainly include the thirdparty jars in the CVS project and in the distribution. My personal suggestion would to maintain a similar structure for the lib directory as in jboss-head. For example:

jboss-benchmark
- lib
- apache-commons
- commons-logging.jar
- README.txt
- LICENSE.txt
- junit
- junit.jar
- README.txt

so that versions and licenses can be easily tracked between versions (is much more difficult if just have a lib directory with all the jars in it).

I can add this if you like?

[clebert.suconic]

I agree... it makes sense.

But what about jboss libs like jgroups?

Should we include it as third party jars?


-clebert

[tom.elrod]

The forum took out my spacing, but assume you understand the diretory structure.

For JBossRemoting I was just going to put a jboss directory under the lib directory with all the jboss libraries and a README.txt file with the versions for all the libraries (and mabye license, but may be repetative).

[tom.elrod]

Actually just reminded that the new build will eliminate this problem, so guess can just wait till then.