forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: xml-fop Build Failed
Date Fri, 29 Oct 2004 13:50:04 GMT
On Oct 29, 2004, at 1:56 AM, Juan Jose Pablos wrote:
>> I'm sorry about that. I first got on the job of getting the xml-fop  
>> web  site updated ages ago (6 months?). Unfortunately, the files were  
>> in  disarray. Soon after I started I saw that forrest was moving to  
>> 0.6, so  I decided to make xml-fop ready for the transition to 0.6.  
>> This meant  creating a site.xml file, removing the book.xml files,  
>> and making  assorted other changes (skinconf.xml, forrest.properties,  
>> tabs.xml,  etc.).
>>
>> Over this long period of time, I must've forgotten that I was the one  
>>  who created 'site.xml' on my local drive. I have since become a   
>> committer for xml-fop, and just committed site.xml.
>>
> I am not able to see this either. Are you commiting these changes on  
> the same cvs?

http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/ 
xdocs/site.xml

  Revision 1.1 - (view) (download) (as text)  (annotate)  - [select for  
diffs]
  Wed Oct 27 21:08:04 2004 UTC (40 hours, 38 minutes ago) by clay
  Branch:  MAIN
  CVS Tags:  HEAD
added site.xml to prepare for forrest-0.6

>> I never was able to get that patch to work. However, since I've been   
>> able to workaround the problem, I think I'm OK.
>
> It makes easier to help you out if you put the changes on a cvs so we  
> can work in the same version..
>
> Cheers,
> Cheche

The main reason I hadn't committed yet, is that I don't want to 'break'  
the xml-fop web site. So, I've been biding my time, working towards a  
BUILD SUCCESSFUL. Once I get that (with all content and issues  
resolved--especially CRITICAL issues) I will update to the most recent  
changes and commit my changes to CVS. At least that is my plan. :-)

Web Maestro Clay
-- 
Clay Leeds - <cleeds@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>


Mime
View raw message