You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-dev@james.apache.org by Danny Angus <da...@apache.org> on 2003/07/02 16:19:48 UTC
website broken .. Help ..
I'm going to be away from email etc for about 8 days from tonight.
However I can't sort out the website because anoncvs access to james-server is broken.
When this is fixed someone needs to log on to deadalus and move the old-site tar from james.apache.org (it contains the current site tar.gz up for backup)
then delete the contents of the site,
then checkout **anonymously** from cvspublic james-server/www to update it to use the new module name.
Seems simple huh? It should be.
There's one "issue" some of the files in mailet/ and javadocs/ won't let _me_ delete them, they'll need chmodded or deleted by their owners.
d.
RE: new list address?
Posted by Danny Angus <da...@apache.org>.
Yes, there was a warning about it a few days ago.
> -----Original Message-----
> From: Richard O. Hammer [mailto:ROHammer@EarthLink.net]
> Sent: 02 July 2003 15:22
> To: James Developers List
> Subject: new list address?
>
>
> Should I update my address book to this new email address for the
> James developer list?
>
> Two messages which I have sent this morning to
> james-dev@jakarta.apache.org seem to have fallen into a black hole.
>
> Sorry if I missed the announcement.
>
> Rich Hammer
> Hillsborough, N.C.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
new list address?
Posted by "Richard O. Hammer" <RO...@EarthLink.net>.
Should I update my address book to this new email address for the
James developer list?
Two messages which I have sent this morning to
james-dev@jakarta.apache.org seem to have fallen into a black hole.
Sorry if I missed the announcement.
Rich Hammer
Hillsborough, N.C.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Website (was RE: website broken .. Help ..)
Posted by Danny Angus <da...@apache.org>.
> My company has been working on a web-based system that will
> automatically generate JavaDocs (and other documentation based on the
> source code) out of CVS. I don't know how quickly you plan to get the
> new site generated, but I wanted to share what we've done and see if the
> James project wanted to rely on it for the up-to-date javadoc release.
> It's not quite ready for prime time (we're still tweaking the output and
> need to add security settings), but hopefully next week I can send a
> link to everyone to see what it outputs.
That sounds cool.
My one reservation is that as our docs *are* generated and versioned we have
a (managerial) problem with version control of the docs published on the
website.
As it is strictly *not* necessary to make them available on the website and
we provide them there for convenience only it makes sense to not to hog
resources by maintaining several versions, and therefore to follow the
"principle of least suprise" we should be publishing the javadocs for the
current stable version. This means that they will have to lag behind cvs.
My first thought is that the simplest way to achieve this is to have the
release manager for any stable release simply copy the docs generated by the
same build that generates the downloads and commit them to the site cvs.
Then we _know_ that they match the download version and that they can't
easily be changed by accident.
I look forward to seeing what your tool does though, perhaps it will
facilitate a new behaviour we can make use of.
Re: Website (was RE: website broken .. Help ..)
Posted by Serge Knystautas <se...@lokitech.com>.
Danny Angus wrote:
> 2/ that we can have javadocs for the current *stable* release of James on
> the site not the docs for the head of cvs
> 2a/that we achieve 2 without messing around trying to check the correct
> javadocs using cvs tags and dates and things
Danny,
My company has been working on a web-based system that will
automatically generate JavaDocs (and other documentation based on the
source code) out of CVS. I don't know how quickly you plan to get the
new site generated, but I wanted to share what we've done and see if the
James project wanted to rely on it for the up-to-date javadoc release.
It's not quite ready for prime time (we're still tweaking the output and
need to add security settings), but hopefully next week I can send a
link to everyone to see what it outputs.
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com
Website (was RE: website broken .. Help ..)
Posted by Danny Angus <da...@apache.org>.
> > [NOTE TO server-dev@ SUBSCRIBERS: please notice the
> > site-dev@james.apache.org address. Messages related to site development
> > will be migrating, along with the site contents, to a new module
> > and list.]
>
> (As soon as I get back from Mallorca :-)
I'm back.
Boy was it ever Hot and Sunny :-)
Right, I'm going to make some proposals about the website stuff, anyone with
opinions pls subscribe to site-dev@ and say your stuff. I know I'm cross
posting this message, thats so that I can canvass people who aren't
subscribed there, but lets keep the discussion on site-dev please.
Ok. As I see it we want to achieve the following:
1/ that the website continues to be built from xdocs stored in cvs, and
updated to the webserver using cvs.
2/ that we can have javadocs for the current *stable* release of James on
the site not the docs for the head of cvs
2a/that we achieve 2 without messing around trying to check the correct
javadocs using cvs tags and dates and things
3/ that we can continue to build James distros with docs and without
*having* to include a snapshot of the site.
4/ that we admit the differences between product docs and website material
and provide a *simple* machanism to support and encourage the authoring of
both.
Therfore to these ends I think that we should seperate the existing xdocs
into website and product documentation, and rather than move everything en
masse into james-site move only the website docs to the site module leave
the James and Mailet docs in the server module.
We call the product docmentation The Manual, and the Project documentation
is the website.
In this fashion a build of James will build appropriate Manuals and
Javadocs. Users will have correct product documentation at their fingertips,
and won't have a lot of spurious material relating to policy and process.
If we then make it a task of release management (and make sure it is simple
to carry out) to commit the released Manual and Javadocs to site then we can
achieve all of this.
We can continue to use the refreshingly simple XSLT, which I personally
prefer to other systems only because I'm at more home with xsl, and see what
help we can get, some has been very kindly offered, for forrest-ising the
process.
If we don't automate the copying of Manual and Javadocs we will avoid people
accidentally comitting the wrong versions.
I'd like to conclude all this by re-arranging the James and Mailet
distributed documentation to include one or two cover pages which aren't
part of the manual, aren't copied to the website but do provide an
introduction to the project and links to the site and other on-line
material.
I'll accomodate this and anyones expressed opinions in a formal proposal
soon.
NB Opinions to site-dev@james.apache.org
d.
Website (was RE: website broken .. Help ..)
Posted by Danny Angus <da...@apache.org>.
> > [NOTE TO server-dev@ SUBSCRIBERS: please notice the
> > site-dev@james.apache.org address. Messages related to site development
> > will be migrating, along with the site contents, to a new module
> > and list.]
>
> (As soon as I get back from Mallorca :-)
I'm back.
Boy was it ever Hot and Sunny :-)
Right, I'm going to make some proposals about the website stuff, anyone with
opinions pls subscribe to site-dev@ and say your stuff. I know I'm cross
posting this message, thats so that I can canvass people who aren't
subscribed there, but lets keep the discussion on site-dev please.
Ok. As I see it we want to achieve the following:
1/ that the website continues to be built from xdocs stored in cvs, and
updated to the webserver using cvs.
2/ that we can have javadocs for the current *stable* release of James on
the site not the docs for the head of cvs
2a/that we achieve 2 without messing around trying to check the correct
javadocs using cvs tags and dates and things
3/ that we can continue to build James distros with docs and without
*having* to include a snapshot of the site.
4/ that we admit the differences between product docs and website material
and provide a *simple* machanism to support and encourage the authoring of
both.
Therfore to these ends I think that we should seperate the existing xdocs
into website and product documentation, and rather than move everything en
masse into james-site move only the website docs to the site module leave
the James and Mailet docs in the server module.
We call the product docmentation The Manual, and the Project documentation
is the website.
In this fashion a build of James will build appropriate Manuals and
Javadocs. Users will have correct product documentation at their fingertips,
and won't have a lot of spurious material relating to policy and process.
If we then make it a task of release management (and make sure it is simple
to carry out) to commit the released Manual and Javadocs to site then we can
achieve all of this.
We can continue to use the refreshingly simple XSLT, which I personally
prefer to other systems only because I'm at more home with xsl, and see what
help we can get, some has been very kindly offered, for forrest-ising the
process.
If we don't automate the copying of Manual and Javadocs we will avoid people
accidentally comitting the wrong versions.
I'd like to conclude all this by re-arranging the James and Mailet
distributed documentation to include one or two cover pages which aren't
part of the manual, aren't copied to the website but do provide an
introduction to the project and links to the site and other on-line
material.
I'll accomodate this and anyones expressed opinions in a formal proposal
soon.
NB Opinions to site-dev@james.apache.org
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: website broken .. Help ..
Posted by Danny Angus <da...@apache.org>.
> [NOTE TO server-dev@ SUBSCRIBERS: please notice the
> site-dev@james.apache.org address. Messages related to site development
> will be migrating, along with the site contents, to a new module
> and list.]
(As soon as I get back from Mallorca :-)
d.
RE: website broken .. Help ..
Posted by "Noel J. Bergman" <no...@devtech.com>.
> anoncvs access to james-server is broken.
Fixed.
> then delete the contents of the site
Just had to edit CVS/Repository and delete the subdirectories. Then cvs
update -Pd took care of recreating them from the new module.
--- Noel
[NOTE TO server-dev@ SUBSCRIBERS: please notice the
site-dev@james.apache.org address. Messages related to site development
will be migrating, along with the site contents, to a new module and list.]
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: website broken .. Help ..
Posted by "Noel J. Bergman" <no...@devtech.com>.
> anoncvs access to james-server is broken.
Fixed.
> then delete the contents of the site
Just had to edit CVS/Repository and delete the subdirectories. Then cvs
update -Pd took care of recreating them from the new module.
--- Noel
[NOTE TO server-dev@ SUBSCRIBERS: please notice the
site-dev@james.apache.org address. Messages related to site development
will be migrating, along with the site contents, to a new module and list.]