Mans Schultz

+ Follow
since Mar 17, 2010
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Mans Schultz


I am having a rather nasty problem with windows 2008 server. We have a java application that is running as a service using the local services user. The problem is this user does not have access to read/write to the specified java tmp directory (specified by the system). This means that every time the application tries to create a tmp file an IOException is thrown.

Is there any way to make a java application that need access to the tmp directory run as a service without:
# Creating a new user specifically for the purspose
# Specifying a new tmp directory (which you will have to clean up yourself)
10 years ago
I took your council and excluded the tests. Better safe than sorry.

Thanks for the advice.
Thank you for the quick replies!

I understand the issue with submitting files that aren't needed, you have everything to loose and nothing to win. But I feel that my unit tests are a big part of motivating my design. Im afraid that some parts won't be understood without the tests. Is it perhaps better to rewrite the design so it can be more easily motivated (but not as testable) since the tests can't be submitted?

I have some small question about the delivery requirements. Since sun can't be contacted at any email right now I thought I would ask here.

I use maven to generate my javadoc for the assignment. This seemed natural at first but lately the requirements got me thinking. Is this really ok or does it break the rule that you can't submit code that isn''t your own? Maven does generate files so I will be submitting files that I have not written (even if I wrote the code the javadoc is based on). Then again, html files are not code and suns own javadoc tools also generates files.

Also is there a consensus on where to place test files in the delivery jar? Since the test classes should not be included in the application jar it seems wrong to keep them along with the rest of the code/javadoc. Nor do I want them to be omitted completly. Alot of my design choices are based around testability so the test classes are a major part of the general design. Do I risk an auto-fail if I add another folder for the tests?

What do you guys think?