Cool, thanks Grant!
Grant Ingersoll wrote:
> Sorry, missed that one. I put it in and ran the script. Should
> propagate in an hour or so.
>
> -Grant
>
> On Jan 12, 2008, at 4:50 PM, Michael Busch wrote:
>
>> Grant Ingersoll wrote:
>>>
>>> Done. For the record, the script runs:
>>>
>>
>> It w
Sorry, missed that one. I put it in and ran the script. Should
propagate in an hour or so.
-Grant
On Jan 12, 2008, at 4:50 PM, Michael Busch wrote:
Grant Ingersoll wrote:
Done. For the record, the script runs:
It works fine! I just checked the website and it has been updated by
the
Grant Ingersoll wrote:
>
> Done. For the record, the script runs:
>
It works fine! I just checked the website and it has been updated by the
script.
Only the new "nightly documentation" link doesn't work yet. Did you add
the following line to your script (I mentioned it in my last mail)?
/usr
Grant Ingersoll wrote:
>
> Done. For the record, the script runs:
Cool, thanks!
>
> /usr/local/bin/svn export --force
> http://svn.apache.org/repos/asf/lucene/java/site/docs
> /www/lucene.apache.org/java/docs
>
>
>> Another question: Do we also want to have a link to the unreleased
>> docum
On Jan 11, 2008, at 1:11 PM, Michael Busch wrote:
Grant Ingersoll wrote:
It is svn exported from a crontab on p.a.o under my account. If
you can
tell me what commands need to be run, I can add it.
You just need to "svn co" the docs from the new location
https://svn.apache.org/repos/asf/l
Grant Ingersoll wrote:
> It is svn exported from a crontab on p.a.o under my account. If you can
> tell me what commands need to be run, I can add it.
>
You just need to "svn co" the docs from the new location
https://svn.apache.org/repos/asf/lucene/java/site/docs and "scp" it to
/www/lucene.apa
It is svn exported from a crontab on p.a.o under my account. If you
can tell me what commands need to be run, I can add it.
Presumably the new version of Hudson has the ability to do scp now,
but I haven't had a chance to tackle that yet. At some point, we
should tackle that, which will s
Chris Hostetter wrote:
>
> i trust you :)
Thanks! :)
> i figured it was a work in progress, i just wasn't sure what your plan was
> for what docs would live in the "site" and which would live in the
> release. When i poked arround your preview directory earlier i found two
> copies of "gett
: The short answer is: I wasn't done yet :-). I'll update the trunk and
: 2.3 branch soon. You can see a preview of the changes I'm going to make
: here: http://people.apache.org/~buschmi/preview/. The 2.3 release will
: then only have 2.3 specific docs.
i trust you :)
i figured it was a work in
Chris Hostetter wrote:
> : OK, I checked in the new web site into a new location outside of trunk:
> : lucene/java/site/. The nightly cron job must copy the files now from
>
> Uh ... point of clarification: these files all seem to be have been
> "svn add"ed (not "svn move"d or "svn copy"ied so th
: OK, I checked in the new web site into a new location outside of trunk:
: lucene/java/site/. The nightly cron job must copy the files now from
Uh ... point of clarification: these files all seem to be have been
"svn add"ed (not "svn move"d or "svn copy"ied so they don't have any
history prese
Grant Ingersoll wrote:
> Works for me.
>
> -Grant
>
OK, I checked in the new web site into a new location outside of trunk:
lucene/java/site/. The nightly cron job must copy the files now from
lucene/java/site/docs instead of lucene/java/trunk/docs. Which script do
I have to change, Grant? The c
Works for me.
-Grant
On Jan 10, 2008, at 8:13 PM, Michael Busch wrote:
Doug Cutting wrote:
Grant Ingersoll wrote:
I don't know, I think it is nice to have explicit links to previous
ones as well, but it is one extra click. I suspect that is the main
thing people want from previous versions
Doug Cutting wrote:
> Grant Ingersoll wrote:
>> I don't know, I think it is nice to have explicit links to previous
>> ones as well, but it is one extra click. I suspect that is the main
>> thing people want from previous versions so it is nice to not have to
>> dig deep into the Site Versions and
Grant Ingersoll wrote:
I don't know, I think it is nice to have explicit links to previous ones
as well, but it is one extra click. I suspect that is the main thing
people want from previous versions so it is nice to not have to dig deep
into the Site Versions and have it right there from the
Grant Ingersoll wrote:
>
> Or, how about 2.3 and the current javadocs page? Such as:
>
> Javadocs
> - Latest Release -> points to latest official release
> - All Releases -> points to current javadocs page
>
OK sounds good. I will make the change!
-Michael
---
On Jan 10, 2008, at 5:02 PM, Michael Busch wrote:
Yeah, but I think the Javadocs site will become pretty full when we
add
2.3 links (and 2.4, 2.9, 3.0 in the future). Because we have to have
multiple links for core, demo, and contribs from 2.3 on.
We can age out older versions. We only hav
Yeah, but I think the Javadocs site will become pretty full when we add
2.3 links (and 2.4, 2.9, 3.0 in the future). Because we have to have
multiple links for core, demo, and contribs from 2.3 on.
Maybe we could have two menu items for the two most recent releases in
the left navigation bar? Olde
I don't know, I think it is nice to have explicit links to previous
ones as well, but it is one extra click. I suspect that is the main
thing people want from previous versions so it is nice to not have to
dig deep into the Site Versions and have it right there from the
javadocs link.
-G
Hi,
first of all: sorry for the late response!
I'm not sure why we need the new javadocs page? The users can access the
javadocs from old releases by using the "Site Versions" links.
Can we just keep the Javadocs menu in the left navigation bar and rename
it to "Lucene 2.3.0 API"?
Here's a prev
Hmm, it is possible, with a fair amount of work, that I am not going
to do... I'll just leave it as is
On Dec 5, 2007, at 6:09 AM, Grant Ingersoll wrote:
Ah, but the example in the first link shows all the items
expanded... I will dig in...
-Grant
On Dec 4, 2007, at 9:59 PM, Chris Ho
Ah, but the example in the first link shows all the items expanded...
I will dig in...
-Grant
On Dec 4, 2007, at 9:59 PM, Chris Hostetter wrote:
: I also have some Forrest questions. Does anyone know how to make
it so that
: the Documentation page is the default expanded page instead of
: I also have some Forrest questions. Does anyone know how to make it so that
: the Documentation page is the default expanded page instead of About?
: Similarly, how does one auto-expand a section? Ideally, I think we should
: have the Documentation page expanded, and all items underneath it.
OK, I committed some changes:
I introduced a new page called javadocs that contains links to 2.x
builds of the javadocs and also tells people where to go find older
versions of the javadocs (pre 2.x). This is now the main link from
Documentation->javadocs.
I moved the Nightly build javad
24 matches
Mail list logo
