Oh, I missed the move of

http://james.apache.org/server/index.html

to

https://svn.apache.org/repos/asf/james/project/branches/server_docs_3-alpha_and_2.2.0/

To further map the people.apache.org folder structure to the maven structure, we could integrate the server index.html (now in branche) to the server documentation. After all, it's part of it.

WDYT?

Eric

On 26/11/11 20:56, Eric Charles wrote:
Hi,

.../server/3/ is there because we also have .../server/2/

We have in .../server some files that are deployed from the
'project/server' maven module.

.../protocols/trunk should be simply .../protocols.

To deploy everything with 'mvn clean site-deploy', we would need to
review a bit the maven project and there associated folder structure on
people.apache.org. For example, putting the .../server/2 in
.../archive/server/2, merging the 'project/server' maven module with the
'server' maven module, and finally moving .../server/3 to .../server.

Thx,

Eric


On 23/11/11 10:14, Felix Knecht wrote:
Hi

What should be the way of deploy new documentation to the James website
and where should this actual deployment goto?
The website navigation has been defined as

http://james.apache.org/index.html
http://james.apache.org/server/index.html
http://james.apache.org/hupa/index.html
http://james.apache.org/protocols/index.html
http://james.apache.org/imap/index.html
http://james.apache.org/mailet/index.html
http://james.apache.org/mailbox/index.html
http://james.apache.org/mime4j/index.html
http://james.apache.org/jsieve/index.html
http://james.apache.org/jspf/index.html
http://james.apache.org/jdkim/index.html
http://james.apache.org/mpt/index.html
http://james.apache.org/postage/index.html

but the in the distributionManagement section of the project pom.xml's
(trunk) are different url's defined like e.g.

- people.apache.org/www/james.apache.org/server/3/
- people.apache.org/www/james.apache.org/protocols/trunk/
- others are matching the navigation structure

Can all be fix in the way that deploying the generated site via "mvn
site-deploy" is going into the actual navigation place?

A full update of the whole James website could be (wishfully) done
then by

$ svn co http://svn.apache.org/repos/asf/james/current current-james
$ cd current-james
$ mvn clean site-deploy

wdot?

Regards
Felix

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



--
Eric
http://about.echarles.net

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to