That might work. But my way was easier :)

And unless this changed recently, the cobertura report outputs the
source code files in the cobertura directory, not a subdir. I'm assuming
the OP has already shut off xref reports and other things which contain
source.

-----Original Message-----
From: Stephen Connolly [mailto:[email protected]] 
Sent: Friday, October 23, 2009 10:26 AM
To: Maven Users List
Subject: Re: [cobertura] do not publish source code

or another technique would be to overwrite every html file that is in a
sub-dir with a simple html saying that the source code is
confidential...
that way your links will still work ;-)

2009/10/23 Edelson, Justin <[email protected]>

> Without an extensive amount of work, I suspect you could bind a custom

> execution of the clean plugin in the post-site phase to remove all the

> html files from target/site/cobertura EXCEPT for index.html, 
> frame-packages.html, frame-summary.html, frame-sourcefiles.html, and 
> help.html. This would lead to broken links. Not having broken links 
> would likely involve modifying cobertura and/or the plugin, so I'd 
> suggest at least trying the clean option and see how far that takes
you.
>
> Justin
>
> -----Original Message-----
> From: Daniele Dellafiore [mailto:[email protected]]
> Sent: Friday, October 23, 2009 10:04 AM
> To: Maven Users List
> Subject: [cobertura] do not publish source code
>
> Hi everyone.
>
> I want to publish code coverage for my project on a public site but 
> some projects are not open source. How can I avoid cobertura to 
> publish the source code for each class leaving all the coverage
reports?
>
> Thanks..
>
> --
> Daniele Dellafiore
> http://ildella.net
> http://twitter.com/ildella
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to