search

havapa / testability-explorer

Automatically exported from code.google.com/p/testability-explorer
Apache License 2.0
0 stars 0 forks source link

Maven mangles the HTML report #14

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Maven places some navigation elements into the HTML report, which conflict
with the content that was written there by TE.

What steps will reproduce the problem?
1. run mvn:site with testability plugin enabled
2. browse to HTML report, it is borked

Original issue reported on code.google.com by aeagle22206 on 13 Apr 2009 at 11:11

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
For context, the bug is explained in
http://groups.google.com/group/testability-explorer/msg/3700c79eb721b341

Original comment by pja...@gmail.com on 23 Apr 2009 at 5:34

GoogleCodeExporter commented 8 years ago 
I'm going to take a look into this one.  Thanks Peter.

Original comment by christia...@gmail.com on 23 Apr 2009 at 6:56

GoogleCodeExporter commented 8 years ago 
So I ran it on israfil-micro-container, hosted at israfil-micro.googlecode.com, 
and it worked when I ran the TE 
report as the only maven report.  I'm going to start adding different reports 
around it and seeing if it's affected 
by them.  I'm wondering if something isn't being cleaned-up that we can find 
that's maybe wrecking the stream.

Original comment by christia...@gmail.com on 24 Apr 2009 at 6:07

GoogleCodeExporter commented 8 years ago 
yeah - even one other report plugin mangles the image.  The earlier runs I did 
also had no analysis underneath, 
but I can't tell if that was an anomaly.  At least it's clear there's some 
interaction between reporting plugins that's 
not healthy.

Original comment by christia...@gmail.com on 24 Apr 2009 at 6:30

GoogleCodeExporter commented 8 years ago

Original comment by aeagle22206 on 8 Jul 2009 at 5:26

GoogleCodeExporter commented 8 years ago 
Good ping, alex.  I'll put this back on my priority list.

Original comment by christia...@gmail.com on 8 Jul 2009 at 5:38

GoogleCodeExporter commented 8 years ago 
Any new news on this issue?

Original comment by gpampara@gmail.com on 16 Sep 2009 at 5:17

GoogleCodeExporter commented 8 years ago 
Any news on this issue?

Original comment by gauravsw...@gmail.com on 21 Nov 2009 at 8:44

GoogleCodeExporter commented 8 years ago 
Gak.  This is still on my list, but I haven't had any time to work on it.  I'm 
going to try to 
do a bit more investigation this coming week over the holiday.

Original comment by christia...@gmail.com on 21 Nov 2009 at 4:44

GoogleCodeExporter commented 8 years ago 
A trivial approach would be to define this as an external report, i.e. one that 
isn't
skinned.  I've attached a patch that does so; it's more of a workaround than a 
fix,
but at least the report is complete and usable.

I've actually been trying to get the skinned version working, and have a 
relatively
minimal IT that fails on a symptom of the corruption (two </html> tags in the 
output
file), but I'm having some trouble reusing the existing HTML report.  I think a 
fix
is going to mean a Maven-specific report generator, which probably belongs in 
the
plugin rather than in the core.

Original comment by pja...@gmail.com on 27 Nov 2009 at 6:41

Attachments:

GoogleCodeExporter commented 8 years ago 
What I am seeing is a page with the Maven skin/normal decorations but the TE 
data is
all plain text.  Is that what this issue is about (is that what borked means? 
;-))? 
(I'm wondering if there is some other setup needed on my part, e.g. CSS files or
something to make it work; but I don't think so based on my quick review)

What a bummer - really looking forward to adding this to our site gen! :-(

Original comment by jeffjjen...@gmail.com on 24 Feb 2010 at 9:11

GoogleCodeExporter commented 8 years ago 
any updates on this? Problem is still there on current version: the html output 
is
appended after the </html> of the normal maven-site. 

Is there a workaround? 

thanks,
dominik

Original comment by dominik....@gmail.com on 5 May 2010 at 10:35

GoogleCodeExporter commented 8 years ago 
I've revised my patch to more fully implement the external report, as simply
returning true from isExternalReport() doesn't appear to be sufficient.

This does appear to fix the original problem of corrupt HTML pages, so perhaps 
it's
worth adding a new defect to implement a skinnable version of the report?

Original comment by pja...@gmail.com on 13 May 2010 at 4:11

Attachments:

GoogleCodeExporter commented 8 years ago 
Sounds great... I think it is better to have the report/data and no skinning 
than no
report - I'm not worried about skinning!  Can a committer approve/commit this 
patch
and release so we can use it?

Original comment by jeffjjen...@gmail.com on 13 May 2010 at 6:09

GoogleCodeExporter commented 8 years ago 
I've tested this patch and appears to solve the problem. But it seems this 
issue has been forgotten. It would be *really* nice if a commiter could apprve 
this patch!

Original comment by otavioma...@gmail.com on 1 Oct 2011 at 2:21

GoogleCodeExporter commented 8 years ago 
I'll take a look at the patch tomorrow.  Sorry - this had completely fallen off 
my radar screen.

Original comment by christia...@gmail.com on 5 Oct 2011 at 2:23

GoogleCodeExporter commented 8 years ago 
Would definitely love this to be fixed.

Original comment by benha...@gmail.com on 17 Sep 2012 at 5:34