Roel De Nijs wrote:to have a bit a readible thread I changed the javadoc call a bit: if you want to use the build file you just have to delete ...> and <...
Andrew Monkhouse wrote:To get around that particular problem, I tend to split my lines - even in the production code.
Andrew Monkhouse wrote:Do you feel like adding a link to this in the JavaRanch SCJD FAQ?
Alecsandru Cocarla wrote:DocCheck generates HTML reports about how well your code is documented. You should try it
MyInterface.java:72: warning - @return tag has no arguments.
MyInterface.java:59: warning - @param argument "parameter2" is not a parameter name.
Vasya Pupkin wrote:PMD and javadoccheck appear to be very helpful.
Vasya Pupkin wrote:Roel, thanks again for your shared code. I finally had some time to run your code. It did not take long to modify everything for my needs (B&S).
Roel De Nijs wrote:Hi Nilesh,
This certainly is the first topic having my name in the title
Nilesh Thali wrote:Addressing this to you, Roel, since you created this extremely handy ant build file
Glad I could help and share with the community
It would have been better if you asked your question in the thread where I posted my Ant-file, so everybody using that build file, could also read your question (and my answer). So someone else with the same question, wouldn't have to post it again, because you already did.
More info about the overview comment file, you can read here. This section of the javadoc tool documentation covers all your questions, so I would suggest just reading it and it will (hopefully) clear all your doubts.
[javadoc] Generating Javadoc
[javadoc] Javadoc execution
[javadoc] Loading source files for package suncertify.db...
[javadoc] Loading source files for package suncertify.direct...
[javadoc] Loading source files for package suncertify.domain...
[javadoc] Loading source files for package suncertify.gui...
[javadoc] Loading source files for package suncertify.remote...
[javadoc] Loading source files for package suncertify.test...
[javadoc] Constructing Javadoc information...
[javadoc] Standard Doclet version 1.6.0_18
[javadoc] Building tree for all the packages and classes...
[javadoc] Building index for all the packages and classes...
[javadoc] Building index for all classes...
[javadoc] javadoc: error - Error while reading file /home/morillo/src/java/scjd/submission/src/overview.html
[javadoc] Generating /home/morillo/src/java/scjd/submission/output/submission/docs/javadoc/stylesheet.css...
[javadoc] 1 error
/home/morillo/src/java/scjd/submission/build.xml:92: Javadoc returned 1
Total time: 23 seconds
[auyantepui]</home/morillo/src/java/scjd/submission>% java -version
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Server VM (build 16.0-b13, mixed mode)
[auyantepui]</home/morillo/src/java/scjd/submission>% cat /etc/release
Solaris 10 5/09 s10s_u7wos_08 SPARC
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 30 March 2009
[auyantepui]</home/morillo/src/java/scjd/submission>% file /home/morillo/src/java/scjd/submission/src/overview.html
/home/morillo/src/java/scjd/submission/src/overview.html: cannot open: No such file or directory
[unjar] Expanding: /home/morillo/src/java/scjd/submission/ASSIGNMENT.jar into /home/morillo/src/java/scjd/submission/output/temp/assignment
/home/morillo/src/java/scjd/submission/build.xml:118: Error while expanding /home/morillo/src/java/scjd/submission/ASSIGNMENT.jar
Total time: 24 seconds
[unjar] Expanding: /home/morillo/src/java/scjd/submission/Carlos_Morillo.jar into /home/morillo/src/java/scjd/submission/output/temp/submission
[javac] Compiling 45 source files to /home/morillo/src/java/scjd/submission/output/temp/test
.The full path of every file in my source code with [javac] at the beginning of the line
/home/morillo/src/java/scjd/submission/build.xml:151: /home/morillo/src/java/scjd/submission/src/resources not found.
Total time: 32 seconds
/home/morillo/src/java/scjd/submission/build.xml:155: The <classpath> for <junit> must include junit.jar if not in Ant's own classpath
Total time: 32 seconds
Carlos Morillo wrote:I thought since you called it script that perhaps it was possible to run it from the command line.
Carlos Morillo wrote:which could be solved I guess by adding the JUnit4.jar from NetBeans in Solaris or perhaps downloading it and adding it to the Classpath.
Carlos Morillo wrote:it shows a green bar and green checkmark 4/4 Runs, 0 Errors, 0 Failures, so I think I should be good to go.
Michael Enudi wrote:I don't know if I previously did anything wrong but now I just feel more confident.
Thanks for sharing.
Sean Keane wrote:One small change I would suggest is to the testSourceRequirements method in the TestJarSubmission class - just add a message string to the first Assert.assertTrue.
failed to load main-class manifest attribute from
Daniel Kohl wrote:Unfortunately the script builds a META-INF-Folder automatically so i ended up in calling the jar-Tool itself (with option M).
Daniel Kohl wrote:Hmmm...in my assignment the layout of the .jar is described as a "must", and finally the description doesn't contain a META-INF at root.
Unfortunately the script builds a META-INF-Folder automatically so i ended up in calling the jar-Tool itself (with option M).
Anayonkar Shivalkar wrote:
I'm not sure, but I guess in the requirement document, there is a command given - which will be used to run your jar (e.g. java -jar runme.jar). At that time, there has to be someone to tell Java that which is the main class (i.e. entry point). That is the purpose of META-INF/manifest.mf file.
Daniel Kohl wrote:The packaging-jar AROUND ALL FILES (the submission-package), will also have a useless META-INF using this ant-script.
That's not mentionend in the requirement and the described layout is a must-requirement.