Re: Forrest skin for Jakarta-XX project
On Wed, 22 Oct 2003 17:26:50 -0700 "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > >(What about Struts?) > At the moment, Struts uses hand-crafted XSLT stylesheets that preceeded > the existence of Forrest (and Maven), but we are considering some > alternatives based on both Forrest's and Maven's site generation > facilities. Some proof-of-concept prototypes (not necessarily polished) > of the Struts main page, using three different Forrest skins, are at: > Krysalis style: http://www.twdata.org/dakine/site/ > Avalon/Tigris style: http://www.twdata.org/dakine/site1/ > Forrest/XML Apache style: http://www.twdata.org/dakine/site2/ Looks very nice. :) Kool. > Personally, I would prefer either the Krysalis or Avalon/Tigris styles > to the default Forrest/XML Apache style, but that's just me. Various > Struts developers have various opinions, as well as concerns about the > processing time implications of using Forrest. Likewise > We also use XSLT transformations for other reasons as well (i.e. > generating tag library descriptors and reference documentation), and > already enjoy nice things like print-friendly styles without the > navigation menu -- to say nothing of XHTML-compatible generated > output -- so I don't feel any great sense of urgency to make a > migration. I'm personally not going to have time to even think about > it in the very near term, due to day-job commitments. But, it's > certainly an option for us to share a common look and feel. In my mind, there might be four options: 1. Create "jakarta-skin" and put it (them) into jakarta-site2 2. Create "jakarta-skin" and put it (them) into xml-forrest. We have to wait the next release of Forrest (0.5.2 or 0.6), though 3. Update "avalon-tigris" skin / Patch to it (them) We have to wait the next release of Forrest (0.5.2 or 0.6), though 4. Create "jakarta-XX-skin"s and put it (them) into respective modules. We can make use of it (them) immediately Currently, Jakarta-POI adopts #4 style. Now, I am thinking of the Forrest-ization of Jakarta-Tapestry. (http://www.terra-intl.com/jakarta/tapestry/) Therefore, I am thinking of the #1/#2/#3 options. Any thoughts? -- Tetsuya. ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
Before that, could you please answer my (innocent) question? Why was there no "PDF-Rendering" function in the default avalon-tigris? I thought that Avalon-Team did not want the PDF files because PDF could have been big enough to be downloaded. Sure, I know that it would be related to skinconfig/disable-pdf-link @ skinconf.xml, though :) -- Rather, I thought that "jakarta-skin"/"ws-skin" naming would make sense (Just a copy and reuse of avalon-tigris, it would be), if it would be integrated into the default Forrest "skins" dir. ($FORREST/dist/shbat/) context - skins - |--avalon-tigris |--common |--forrest-css |--forrest-site |--jakarta-site |--krysalis-site |--template |--ws-site ... Make sense? -- Tetsuya. ([EMAIL PROTECTED]) P.S. Tapestry Version: http://www.terra-intl.com/jakarta/tapestry/ On Wed, 22 Oct 2003 19:32:53 +0200 (Subject: Re: Forrest skin for Jakarta-XX project) Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: > > Tetsuya Kitahata wrote: > > > Maybe you might have already known, ws-site/ws-axis/ws-soap [1][2][3] > > are now using the similar skin. (I put the skin into respective > > modules directly) > > Sure, I re-used the avalon-tigris, however, the Forrest 0.5.1 > > avalon-tigris did not suffice our gratifications. > > > > I am sure that I can post patches to forrest-dev, however, > > I am afraid it would affect seriously to avalon-site in the > > future. > > If the skin is just a better version of the same skin it would be ok to > patch it. If the skin will depart a lot from that, then the Avaloners > would need to decide to cooperate in it. > > In any case, the krysalis-site skin has many more features, and I'm > getting it ready to be able to switch forrest-site to use that one, with > of course the traditional Forrest colors. So you can look in that skin > to eventually add the extra features to the avalon-tigris skin. > > In any case, if you send teh patches for avalon-tigris I'll take a look > at them. > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > - - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ Apache Software Foundation Committer: http://www.apache.org/~tetsuya/ fingerprint: E420 3713 FAB0 C160 4A1E 6FC5 5846 23D6 80AE BDEA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
On Wed, 22 Oct 2003 19:25:56 +0100 "BAZLEY, Sebastian" <[EMAIL PROTECTED]> wrote: > > Maybe you can find "new" xsl file via > > jakarta-site2/xdocs/stylesheets/site.xsl > > > > ... Just copy to jmeter module and cvs commit, I guess.. > > As far as I know, the JMeter stylesheets are unique to JMeter, so I doubt if > that would work. D'oh... Sorry. I had a little confused. Okeydokey. What I proposed here, was not "Please use Forrest, all the Jakarta-XX-Team", but "Dear Jakarta-XX-Project, which want to use Apache Forrest ...". I've heard that Struts Team once discusses about the usage of Forrest, so I said "What about Struts?" As for JMeter, I think now it is working well. (Yes, I sent patches for the re-build of the site using Anakia, the other day) Just I took a look at the current JMeter site and found that there's still "Copyright 1999-2001" statement at the bottom of each pages. So, I told you the procedure of updating website how-to. Thank you. -- Tetsuya. ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
On this topic - I am tackling OJB documentation at the moment and would love to chat with someone who has put together a solid set of docs for one of the projects with excellent docs. As it isn't community relevant, really, drop me a line offline if you can give me a couple pointers about things to do/avoid. I have *written* lots, but don't think I know quite enough about good *deployment* of docs. -Brian On Wednesday, October 22, 2003, at 08:26 PM, Craig R. McClanahan wrote: Tetsuya Kitahata wrote: (What about Struts?) At the moment, Struts uses hand-crafted XSLT stylesheets that preceeded the existence of Forrest (and Maven), but we are considering some alternatives based on both Forrest's and Maven's site generation facilities. Some proof-of-concept prototypes (not necessarily polished) of the Struts main page, using three different Forrest skins, are at: Krysalis style: http://www.twdata.org/dakine/site/ Avalon/Tigris style: http://www.twdata.org/dakine/site1/ Forrest/XML Apache style: http://www.twdata.org/dakine/site2/ Personally, I would prefer either the Krysalis or Avalon/Tigris styles to the default Forrest/XML Apache style, but that's just me. Various Struts developers have various opinions, as well as concerns about the processing time implications of using Forrest. We also use XSLT transformations for other reasons as well (i.e. generating tag library descriptors and reference documentation), and already enjoy nice things like print-friendly styles without the navigation menu -- to say nothing of XHTML-compatible generated output -- so I don't feel any great sense of urgency to make a migration. I'm personally not going to have time to even think about it in the very near term, due to day-job commitments. But, it's certainly an option for us to share a common look and feel. Craig - 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]
Re: Forrest skin for Jakarta-XX project
Tetsuya Kitahata wrote: (What about Struts?) At the moment, Struts uses hand-crafted XSLT stylesheets that preceeded the existence of Forrest (and Maven), but we are considering some alternatives based on both Forrest's and Maven's site generation facilities. Some proof-of-concept prototypes (not necessarily polished) of the Struts main page, using three different Forrest skins, are at: Krysalis style: http://www.twdata.org/dakine/site/ Avalon/Tigris style: http://www.twdata.org/dakine/site1/ Forrest/XML Apache style: http://www.twdata.org/dakine/site2/ Personally, I would prefer either the Krysalis or Avalon/Tigris styles to the default Forrest/XML Apache style, but that's just me. Various Struts developers have various opinions, as well as concerns about the processing time implications of using Forrest. We also use XSLT transformations for other reasons as well (i.e. generating tag library descriptors and reference documentation), and already enjoy nice things like print-friendly styles without the navigation menu -- to say nothing of XHTML-compatible generated output -- so I don't feel any great sense of urgency to make a migration. I'm personally not going to have time to even think about it in the very near term, due to day-job commitments. But, it's certainly an option for us to share a common look and feel. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Forrest skin for Jakarta-XX project
> -Original Message- > From: Tetsuya Kitahata [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 19:17 > To: Jakarta General List > Subject: Re: Forrest skin for Jakarta-XX project > > > > On Wed, 22 Oct 2003 19:02:52 +0100 > (Subject: RE: Forrest skin for Jakarta-XX project) > "BAZLEY, Sebastian" <[EMAIL PROTECTED]> wrote: > > > > It's related to the fact that you did not login to minotaur > > > (www.apache.org) via ssh and have not done > > > $ umask 0002 > > > $ chmod -R g+w /x1/www/jakarta.apache.org/jmeter > > > $ cd /www/jakarta.apache.org/jmeter/ > > > $ cvs update > > > yet. > > > Sorry, I don't understand what you mean here. > > The XSL stylesheets are part of JMeter, and are used to > transform the XML > > into HTML. > > Changes have been made to the VSL (Anakia) stylesheets, but > not the XSL > > versions, so we cannot currently use XSL to generate either set of > > documentation, as far as I know. > > Sorry, me too at a loss :-) > > Maybe you can find "new" xsl file via > jakarta-site2/xdocs/stylesheets/site.xsl > > ... Just copy to jmeter module and cvs commit, I guess.. As far as I know, the JMeter stylesheets are unique to JMeter, so I doubt if that would work. S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
On Wed, 22 Oct 2003 19:02:52 +0100 (Subject: RE: Forrest skin for Jakarta-XX project) "BAZLEY, Sebastian" <[EMAIL PROTECTED]> wrote: > > It's related to the fact that you did not login to minotaur > > (www.apache.org) via ssh and have not done > > $ umask 0002 > > $ chmod -R g+w /x1/www/jakarta.apache.org/jmeter > > $ cd /www/jakarta.apache.org/jmeter/ > > $ cvs update > > yet. > Sorry, I don't understand what you mean here. > The XSL stylesheets are part of JMeter, and are used to transform the XML > into HTML. > Changes have been made to the VSL (Anakia) stylesheets, but not the XSL > versions, so we cannot currently use XSL to generate either set of > documentation, as far as I know. Sorry, me too at a loss :-) Maybe you can find "new" xsl file via jakarta-site2/xdocs/stylesheets/site.xsl ... Just copy to jmeter module and cvs commit, I guess.. -- Tetsuya. ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Forrest skin for Jakarta-XX project
> -Original Message- > From: Tetsuya Kitahata [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 18:47 > To: Jakarta General List > Subject: Re: Forrest skin for Jakarta-XX project > > > > On Wed, 22 Oct 2003 18:19:13 +0100 > "BAZLEY, Sebastian" <[EMAIL PROTECTED]> wrote: > > > Would using Forrest cause problems with this? > > Or perhaps it would make things easier? > > Forrest can create PDF file. I think it suffice the users' needs. For some things, yes, but not for the interactive Help system. Help uses Java to display an HTML document, and the application navigates to the correct part of the appropriate file. We don't want to require the users to install Acrobat. Java is very finicky about what it will cope with ... > > > At present, the XML is converted using Anakia, with > separate VSL fiels for > > the site and printable versions - there are some XSL > stylesheets, but I > > think these are rather out of date. > > It's related to the fact that you did not login to minotaur > (www.apache.org) via ssh and have not done > $ umask 0002 > $ chmod -R g+w /x1/www/jakarta.apache.org/jmeter > $ cd /www/jakarta.apache.org/jmeter/ > $ cvs update > yet. > Sorry, I don't understand what you mean here. The XSL stylesheets are part of JMeter, and are used to transform the XML into HTML. Changes have been made to the VSL (Anakia) stylesheets, but not the XSL versions, so we cannot currently use XSL to generate either set of documentation, as far as I know. > -- > > Anyway, I can forrest version of JMeter website, within a few days > (Really easy). Not sure we want to regenerate the whole site from CVS at present. There have been a lot of updates to the user documentation, but the corresponding version of the software has not been released. It would be confusing if the online docs described a version that was not generally available. However, if you can publish a separate version that does not change the existing site, that would be useful. S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
On Wed, 22 Oct 2003 18:19:13 +0100 "BAZLEY, Sebastian" <[EMAIL PROTECTED]> wrote: > Would using Forrest cause problems with this? > Or perhaps it would make things easier? Forrest can create PDF file. I think it suffice the users' needs. > At present, the XML is converted using Anakia, with separate VSL fiels for > the site and printable versions - there are some XSL stylesheets, but I > think these are rather out of date. It's related to the fact that you did not login to minotaur (www.apache.org) via ssh and have not done $ umask 0002 $ chmod -R g+w /x1/www/jakarta.apache.org/jmeter $ cd /www/jakarta.apache.org/jmeter/ $ cvs update yet. -- Anyway, I can forrest version of JMeter website, within a few days (Really easy). -- Tetsuya. ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
Tetsuya Kitahata wrote: Maybe you might have already known, ws-site/ws-axis/ws-soap [1][2][3] are now using the similar skin. (I put the skin into respective modules directly) Sure, I re-used the avalon-tigris, however, the Forrest 0.5.1 avalon-tigris did not suffice our gratifications. I am sure that I can post patches to forrest-dev, however, I am afraid it would affect seriously to avalon-site in the future. If the skin is just a better version of the same skin it would be ok to patch it. If the skin will depart a lot from that, then the Avaloners would need to decide to cooperate in it. In any case, the krysalis-site skin has many more features, and I'm getting it ready to be able to switch forrest-site to use that one, with of course the traditional Forrest colors. So you can look in that skin to eventually add the extra features to the avalon-tigris skin. In any case, if you send teh patches for avalon-tigris I'll take a look at them. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
Maybe you might have already known, ws-site/ws-axis/ws-soap [1][2][3] are now using the similar skin. (I put the skin into respective modules directly) Sure, I re-used the avalon-tigris, however, the Forrest 0.5.1 avalon-tigris did not suffice our gratifications. I am sure that I can post patches to forrest-dev, however, I am afraid it would affect seriously to avalon-site in the future. What would you say, Avalon-Team? (See http://jakarta.apache.org/poi/) -- Tetsuya. ([EMAIL PROTECTED]) [1] - http://ws.apache.org/ [2] - http://ws.apache.org/axis/ [3] - http://ws.apache.org/soap/ On Wed, 22 Oct 2003 19:14:55 +0200 (Subject: Re: Forrest skin for Jakarta-XX project) Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: > Nick Chalko wrote: > > Ask the Forrest group I am sure they will include as part of the normal > > build. > > > > Tetsuya Kitahata wrote: > ... > >> I prepared "Jakarta-Skin" which is similar to > >> "POI-skin" (Look and feel: http://jakarta.apache.org/poi/) > >> and I want to put it into jakarta-site2, so that other > >> projects can re-use. > > It looks like the avalon-tigris skin we have in Forrest. ATM this skin > is not very much maintained, so if you would like to send patches, we > can make the project use that one. > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > - > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ Apache Software Foundation Committer: http://www.apache.org/~tetsuya/ fingerprint: E420 3713 FAB0 C160 4A1E 6FC5 5846 23D6 80AE BDEA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Forrest skin for Jakarta-XX project
> -Original Message- > From: Tetsuya Kitahata [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 16:16 > To: Jakarta General List > Subject: Forrest skin for Jakarta-XX project > > > > Hi, > > > I am now thinking of the *unified* skin (of Apache Forrest) > for Jakarta SubProjects... > > Now, Jakarta-POI uses Apache Forrest for building the site. > http://jakarta.apache.org/poi/ > > I think Jakarta-Tapestry will make use of it. too. > > (What about Struts?) > > -- > > I prepared "Jakarta-Skin" which is similar to > "POI-skin" (Look and feel: http://jakarta.apache.org/poi/) > and I want to put it into jakarta-site2, so that other > projects can re-use. > > Any thoughts? JMeter needs to be able to build two versions of its documentation - one for the web-site, and the other for use when running JMeter. This does not have the left-hand navigation bar. JMeter uses some of the pages in its help system, which is displayed using Java. Would using Forrest cause problems with this? Or perhaps it would make things easier? At present, the XML is converted using Anakia, with separate VSL fiels for the site and printable versions - there are some XSL stylesheets, but I think these are rather out of date. S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
Nick Chalko wrote: Ask the Forrest group I am sure they will include as part of the normal build. Tetsuya Kitahata wrote: ... I prepared "Jakarta-Skin" which is similar to "POI-skin" (Look and feel: http://jakarta.apache.org/poi/) and I want to put it into jakarta-site2, so that other projects can re-use. It looks like the avalon-tigris skin we have in Forrest. ATM this skin is not very much maintained, so if you would like to send patches, we can make the project use that one. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest skin for Jakarta-XX project
Ask the Forrest group I am sure they will include as part of the normal build. Tetsuya Kitahata wrote: Hi, I am now thinking of the *unified* skin (of Apache Forrest) for Jakarta SubProjects... Now, Jakarta-POI uses Apache Forrest for building the site. http://jakarta.apache.org/poi/ I think Jakarta-Tapestry will make use of it. too. (What about Struts?) -- I prepared "Jakarta-Skin" which is similar to "POI-skin" (Look and feel: http://jakarta.apache.org/poi/) and I want to put it into jakarta-site2, so that other projects can re-use. Any thoughts? - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ Apache Software Foundation Committer: http://www.apache.org/~tetsuya/ fingerprint: E420 3713 FAB0 C160 4A1E 6FC5 5846 23D6 80AE BDEA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
RE: Deleting or archiving directories in CVS
> -Original Message- > From: Ortwin Glück [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 16:32 > To: Jakarta General List > Subject: Re: Deleting or archiving directories in CVS > > > BAZLEY, Sebastian wrote: > > I'm using Eclipse 2.1.1, in case that is relevant here. > > The top-level dir (docs) is in .cvsignore, so that is not > flagged as being > > out of synch, but all the subdirectories and files are > compared, and the > > result is that all the contents are shown as being new files. > > This is a clear misbehaviour of Eclipse. > > You should try the workaround: > - exit Eclipse > - manually remove CVS information from all directories under docs/: > cd docs && rm -rf `find -type d -name CVS` > - startup Eclipse > - refresh > - exit Eclipse > - startup Eclipse > - synchronize I removed the entire docs tree, which is what the ant build script does on a full build. Eclipse synchronize ignores the docs directory when it is not present. Eclipse also ignores entire directory trees if the top level is in .cvsignore and the tree is not in CVS. So far, so good. But if I create and populate the docs directory, the synchronize process picks up everything under docs. The difference is that docs is in CVS; Eclipse does not ignore CVS in this case. Now I thought .cvsignore files only applied to the current directory, so that there is a case for saying that Eclipse should check CVS for sub-directories? I'm confused! S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-site2/xdocs index.xml
cutting 2003/10/22 09:09:54 Modified:docs index.html xdocsindex.xml Log: Updated for Lucene 1.3 RC2 release. Revision ChangesPath 1.330 +1 -0 jakarta-site2/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-site2/docs/index.html,v retrieving revision 1.329 retrieving revision 1.330 diff -u -r1.329 -r1.330 --- index.html15 Oct 2003 14:11:41 - 1.329 +++ index.html22 Oct 2003 16:09:53 - 1.330 @@ -240,6 +240,7 @@ Jakarta Product news +22 October 2003 - Lucene 1.3 RC2 Released 13 October 2003 - Commons HttpClient 2.0 RC2 Released 11 October 2003 - Tomcat mod_jk 1.2.5 Connector Released 10 October 2003 - Velocity 1.4 R.C.1 released 1.268 +1 -0 jakarta-site2/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/jakarta-site2/xdocs/index.xml,v retrieving revision 1.267 retrieving revision 1.268 diff -u -r1.267 -r1.268 --- index.xml 15 Oct 2003 14:11:42 - 1.267 +++ index.xml 22 Oct 2003 16:09:54 - 1.268 @@ -46,6 +46,7 @@ Jakarta Product news +22 October 2003 - Lucene 1.3 RC2 Released 13 October 2003 - Commons HttpClient 2.0 RC2 Released 11 October 2003 - Tomcat mod_jk 1.2.5 Connector Released 10 October 2003 - Velocity 1.4 R.C.1 released - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-site2/xdocs/site binindex.xml news.xml
cutting 2003/10/22 09:01:05 Modified:docs/site binindex.html news.html xdocs/site binindex.xml news.xml Log: Updated for Lucene 1.3 RC2 release. Revision ChangesPath 1.370 +1 -0 jakarta-site2/docs/site/binindex.html Index: binindex.html === RCS file: /home/cvs/jakarta-site2/docs/site/binindex.html,v retrieving revision 1.369 retrieving revision 1.370 diff -u -r1.369 -r1.370 --- binindex.html 18 Oct 2003 22:23:43 - 1.369 +++ binindex.html 22 Oct 2003 16:01:05 - 1.370 @@ -862,6 +862,7 @@ http://cvs.apache.org/dist/jakarta/bsf/v2.3.0rc1/bin";>BSF 2.3.0-rc1 http://www.apache.org/dist/jakarta/commons/httpclient/binary/";>Commons HttpClient 2.0 Release Candidate 2 +http://cvs.apache.org/dist/jakarta/lucene/v1.3-rc2/";>Lucene 1.3 Release Candidate 2 http://www.apache.org/dist/jakarta/poi/dev/bin";>POI 2.0 prereleases Tapestry 3.0-beta-3 1.375 +9 -1 jakarta-site2/docs/site/news.html Index: news.html === RCS file: /home/cvs/jakarta-site2/docs/site/news.html,v retrieving revision 1.374 retrieving revision 1.375 diff -u -r1.374 -r1.375 --- news.html 14 Oct 2003 02:08:50 - 1.374 +++ news.html 22 Oct 2003 16:01:05 - 1.375 @@ -197,7 +197,15 @@ - + +22 October 2003 - Lucene 1.3 RC2 Released + +A new release candidate of Lucene is available, with many new +features and bug fixes. See http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-lucene/CHANGES.txt?rev=1.56";>CHANGES.txt +for details. Binary and source distributions are available http://cvs.apache.org/dist/jakarta/lucene/v1.3-rc2/";>here. + + + 13 October 2003 - Commons HttpClient 2.0 RC2 Released The HttpClient team is pleased to announce the latest 2.0 release candidate. 1.312 +1 -0 jakarta-site2/xdocs/site/binindex.xml Index: binindex.xml === RCS file: /home/cvs/jakarta-site2/xdocs/site/binindex.xml,v retrieving revision 1.311 retrieving revision 1.312 diff -u -r1.311 -r1.312 --- binindex.xml 18 Oct 2003 22:23:43 - 1.311 +++ binindex.xml 22 Oct 2003 16:01:05 - 1.312 @@ -767,6 +767,7 @@ http://cvs.apache.org/dist/jakarta/bsf/v2.3.0rc1/bin";>BSF 2.3.0-rc1 http://www.apache.org/dist/jakarta/commons/httpclient/binary/";>Commons HttpClient 2.0 Release Candidate 2 +http://cvs.apache.org/dist/jakarta/lucene/v1.3-rc2/";>Lucene 1.3 Release Candidate 2 http://www.apache.org/dist/jakarta/poi/dev/bin";>POI 2.0 prereleases Tapestry 3.0-beta-3 1.315 +13 -0 jakarta-site2/xdocs/site/news.xml Index: news.xml === RCS file: /home/cvs/jakarta-site2/xdocs/site/news.xml,v retrieving revision 1.314 retrieving revision 1.315 diff -u -r1.314 -r1.315 --- news.xml 14 Oct 2003 02:08:50 - 1.314 +++ news.xml 22 Oct 2003 16:01:05 - 1.315 @@ -12,6 +12,19 @@ + +22 October 2003 - Lucene 1.3 RC2 Released + + +A new release candidate of Lucene is available, with many new +features and bug fixes. See http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-lucene/CHANGES.txt?rev=1.56";>CHANGES.txt +for details. Binary and source distributions are available http://cvs.apache.org/dist/jakarta/lucene/v1.3-rc2/";>here. + + + + 13 October 2003 - Commons HttpClient 2.0 RC2 Released - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deleting or archiving directories in CVS
BAZLEY, Sebastian wrote: I'm using Eclipse 2.1.1, in case that is relevant here. The top-level dir (docs) is in .cvsignore, so that is not flagged as being out of synch, but all the subdirectories and files are compared, and the result is that all the contents are shown as being new files. This is a clear misbehaviour of Eclipse. You should try the workaround: - exit Eclipse - manually remove CVS information from all directories under docs/: cd docs && rm -rf `find -type d -name CVS` - startup Eclipse - refresh - exit Eclipse - startup Eclipse - synchronize HTH Odi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Forrest skin for Jakarta-XX project
Hi, I am now thinking of the *unified* skin (of Apache Forrest) for Jakarta SubProjects... Now, Jakarta-POI uses Apache Forrest for building the site. http://jakarta.apache.org/poi/ I think Jakarta-Tapestry will make use of it. too. (What about Struts?) -- I prepared "Jakarta-Skin" which is similar to "POI-skin" (Look and feel: http://jakarta.apache.org/poi/) and I want to put it into jakarta-site2, so that other projects can re-use. Any thoughts? - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ Apache Software Foundation Committer: http://www.apache.org/~tetsuya/ fingerprint: E420 3713 FAB0 C160 4A1E 6FC5 5846 23D6 80AE BDEA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deleting or archiving directories in CVS
> -Original Message- > From: Henning Schmiedehausen [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 14:59 > To: Jakarta General List > Cc: Apache Infrastructure > Subject: Re: Deleting or archiving directories in CVS > > > On Wed, 2003-10-22 at 14:57, BAZLEY, Sebastian wrote: > > > It is easy to create directories in CVS, but it seems to be > very difficult > > to remove directories. > > No it's not. It's impossible. :-) However, as empty > directories will not > show up when checked out (unless explicitly requested), this is not a > big problem. However, removing old directories from the CVS > server will > destroy the history of the files that once have been in this > directory. In the case of the javadoc directories (docs/api...), we are not interested in being able to recover any of the files. Most of the docs directory was likewise populated with files that were generated from xdocs. > > As this is only a problem with the CVS browser, do you really consider > removing the directories necessary? > Apart from the wasted space (perhaps not a big deal), the empty directories do seem to affect synchronisation. I'm using Eclipse 2.1.1, in case that is relevant here. Although there are no files in the directories in CVS, the same directories are needed in the local build environment - they are created and populated when building Javadoc and the manual. When synchronising, the whole docs tree is checked. The top-level dir (docs) is in .cvsignore, so that is not flagged as being out of synch, but all the subdirectories and files are compared, and the result is that all the contents are shown as being new files. This does not happen with a directory that is not in CVS (e.g. printable_docs) - so long as the directory is in the parent .cvsignore, the whole directory tree is ignored. I suppose we could rename the docs directory in the build file and whereever else it is used - but that is a kludge. S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deleting or archiving directories in CVS
With an update also empty directories will be checkedout unless you specify -P (eg cvs -q update -dP), to prune empty directories. Mvgr, Martin On Wed, 2003-10-22 at 15:59, Henning Schmiedehausen wrote: > On Wed, 2003-10-22 at 14:57, BAZLEY, Sebastian wrote: > > > It is easy to create directories in CVS, but it seems to be very difficult > > to remove directories. > > No it's not. It's impossible. :-) However, as empty directories will not > show up when checked out (unless explicitly requested), this is not a > big problem. However, removing old directories from the CVS server will > destroy the history of the files that once have been in this directory. > > As this is only a problem with the CVS browser, do you really consider > removing the directories necessary? > > Regards > Henning > > > > > I've tried various combinations of rmdir, cvs remove, cvs commit, but the > > directories remain in CVS. > > > > Is there a way to (re)move the unwanted directories? -- Martin van den Bemt <[EMAIL PROTECTED]> mvdb.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deleting or archiving directories in CVS
On Wed, 2003-10-22 at 14:57, BAZLEY, Sebastian wrote: > It is easy to create directories in CVS, but it seems to be very difficult > to remove directories. No it's not. It's impossible. :-) However, as empty directories will not show up when checked out (unless explicitly requested), this is not a big problem. However, removing old directories from the CVS server will destroy the history of the files that once have been in this directory. As this is only a problem with the CVS browser, do you really consider removing the directories necessary? Regards Henning > > I've tried various combinations of rmdir, cvs remove, cvs commit, but the > directories remain in CVS. > > Is there a way to (re)move the unwanted directories? -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED]+49 9131 50 654 0 http://www.intermeta.de/ Java, perl, Solaris, Linux, xSP Consulting, Web Services freelance consultant -- Jakarta Turbine Development -- hero for hire "Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!" -- AOL CD when played backwards (User Friendly - 200-10-15) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deleting or archiving directories in CVS
BAZLEY, Sebastian wrote: Is there a way to (re)move the unwanted directories? No, there isn't. You could remove them manually from the file system. However you may run into problems when you check out an earlier tag, because you have lost the history while moving files to different directories. It should be safe to move the RCS files on the CVS file system in the first place and then make a new checkout. Odi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deleting or archiving directories in CVS
We've done some re-arranging of the CVS directory structure in jakarta-jmeter, and some of the directories are now obsolete. I'd like to remove the directories that we will never use (e.g. javadoc output) and move the other unused ones to the Attic. It is easy to create directories in CVS, but it seems to be very difficult to remove directories. I've tried various combinations of rmdir, cvs remove, cvs commit, but the directories remain in CVS. Is there a way to (re)move the unwanted directories? -- Sebastian Bazley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
