From: Andreas S. <se...@st...> - 2012-10-08 15:48:07
|
Hi, >> - What was the intention behind the "attached" subdirectories some (but >> not all) benchmarks have? As far as I can see, they only contain the >> benchmark harness's sources. If that is the case, I propose that *every* >> benchmark should produce its own >> dacapo-${benchmark}-benchmark-sources.jar along with its primary >> dacapo-${benchmark}-benchmark.jar. (This is exactly what happens with my >> Scala benchmarks: >> <http://repo.scalabench.org/snapshots/org/scalabench/benchmarks/scalac-dacapo-benchmark/0.1.0-SNAPSHOT/>) > > I think you're right. I'm not sure how that arose. We simply want separate sources jars. OK, I'll try to cook something up in the next few days. (Fortunately -- and unlike JavaDoc JARs -- sources JARs are easily mergable) >> - What was the intention of putting JavaDoc documentation into the main >> dacapo.jar itself? Why not use a separate artifact? (FWIW, the DaCapo >> 9.12 JAR didn't include a "doc" directory; this is a later addition). > > I'm not sure how this came to be either. I'd suggest it was a mistake or something that was not entirely thought through. I think John Zigman implemented this, at least he committed "tools/transformer" to merge the menus generated by several independent runs of javadoc. This approach may be needlessly complex, though, given the availability of a sources JAR, which provides an IDE with all source-code comments it wants. Thoughts? Best wishes, Andreas |