[Stat-scm-developer] Alternative build- and reporting output directories
Brought to you by:
benoitx,
dougculnane
|
From: Martin K. <mar...@cu...> - 2008-06-16 18:56:14
|
Greetings developers,
I just found StatSCM and started to play around with it. It's a really
nice interface to StatCVS and StatSVN - great work!
However, I immediately hit a case where StatSCM could not handle a POM
to correctly generate a report.
After looking at the source code I see that that StatSCM cannot handle
POM overrides of the default build- and reporting output directories.
(Ie ${project.build.directory} and ${project.reporting.outputDirectory})
Some paths are hard coded to follow the Maven Standard Directory Layout
with default build directory "${basedir}/target" and reporting output
directory "${project.build.directory}/site".
In my case, the POM is a conversion from a legacy Ant project that does
not follow the SDL structure (which still makes it a perfectly valid POM).
I am currently testing a small patch that will fix this in StatSCM (use
POM-configured paths if they are set, otherwise fall back to the
previous code -- i.e. should be backwards compatible).
Would you be interested in this patch and if so, would you like a
(unified?) diff on the dev-list or should I open an issue in the project
tracker?
Regards,
Martin
|