ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephane Bailliez <sbaill...@imediation.com>
Subject RE: [PATCH/CHANGE] JUnitReport
Date Wed, 11 Jul 2001 18:03:16 GMT
> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@apache.org]

> If you know which style task one would have to use, you could fake it
> using project.createTask("style") and populate the attributes
> yourself, no?

Good idea, did not even think about this. I just need to be sure where I can
get the stylesheets. That's all.

> > If backward compatibility has to remain, then for now you can avoid
> > applying the diff.
> 
> Not sure, I've seen you poll on ant-user and think this is a good
> idea.  The change would have the biggest impact for people that have
> their own modified versions of your original stylesheets, right?
> People that use the task in default setup, wouldn't have to change
> anything.

mm.. then I think i'd better do a '[POLL] JUnit users' to get attention and
feedback.
All in all, I think the modified stylesheets are SO painful to do that the
migration will be happily done. I see 3 cases:
- user is happy with the default.
- user need to change a couple of thing but is not too knowledgeable about
xsl, so he just modified a couple of things and just did a couple of minor
changes.
- user is experienced with xsl and had an heart attack when seeing the
stylesheet in 1.3 so he completely wrote his own and does not use the
<report> element but <style>.

-- 
 Stephane Bailliez 
 Software Engineer, Paris - France 
 iMediation - http://www.imediation.com 
 Disclaimer: All the opinions expressed above are mine and not those from my
company. 



Mime
View raw message