On Fri, Dec 4, 2009 at 4:23 AM, Hyrum K. Wright
hyrum_wri...@mail.utexas.edu wrote:
On Dec 3, 2009, at 2:14 PM, Paul Querna wrote:
On Thu, Dec 3, 2009 at 9:31 AM, Doug Cutting cutt...@apache.org wrote:
Paul Querna wrote:
httpd and apr have published doxygen of their trunks periodically,
Hi,
On Fri, Dec 4, 2009 at 4:18 AM, Bhuvaneswaran A bhuvaneswa...@gmail.com wrote:
On Fri, Dec 4, 2009 at 4:23 AM, Hyrum K. Wright
hyrum_wri...@mail.utexas.edu wrote:
Back the original question: What's the best/typical way of generating
and providing these documents? Subversion is using
On Fri, Dec 4, 2009 at 2:12 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Some Apache projects are now using Hudson builds to generate their web
sites from sources stored in svn. The generated site is periodically
rsynced to the correct place people.apache.org. This setup is still a
bit
Hi all,
https://issues.apache.org/jira/browse/DROIDS-65
I am looking into adding droids to the public apache maven rep. I did
some research but could not really find a extend how to.
Can somebody point me in the right direction?
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source
If you use maven in your project:
http://maven.apache.org/developers/release/apache-release.html
Don't know for ant builds, maybe this will help?
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Is ivy able to upload releases? If it can you can upload them to the
apache
Paul Querna wrote:
http://httpd.apache.org/docs/trunk/
Which is linked from the sidebar everywhere, and on the docs page:
http://httpd.apache.org/docs/
That trunk documentation is at least labelled dev. I'd argue it
should only be linked to from http://httpd.apache.org/dev/ and that it
On Fri, Dec 4, 2009 at 5:29 PM, Doug Cutting cutt...@apache.org wrote:
Paul Querna wrote:
http://httpd.apache.org/docs/trunk/
Which is linked from the sidebar everywhere, and on the docs page:
http://httpd.apache.org/docs/
That trunk documentation is at least labelled dev. I'd argue it
Niall Pemberton wrote:
It might be good a good idea to not confuse users trying to find docs
that relate to a release from that of of the current trunk, but its
doing incubating projects a disservice to try and make out that
release policy cover the docs they publish on their web site.
Don't
On Fri, Dec 4, 2009 at 9:09 PM, Doug Cutting cutt...@apache.org wrote:
Niall Pemberton wrote:
It might be good a good idea to not confuse users trying to find docs
that relate to a release from that of of the current trunk, but its
doing incubating projects a disservice to try and make out
Niall Pemberton wrote:
What we publish on the ASF websites
doesn't have to conform to the licensing policy that releases do.
I'm not talking about the website in general. I'm talking specifically
about publishing content primarily intended for inclusion in releases.
Would we permit someone
On Fri, Dec 4, 2009 at 11:45 PM, Doug Cutting cutt...@apache.org wrote:
Niall Pemberton wrote:
What we publish on the ASF websites
doesn't have to conform to the licensing policy that releases do.
I would prefer what I say isn't distorted by selective editing.
I'm not talking about the
Niall Pemberton wrote:
I would prefer what I say isn't distorted by selective editing.
Sorry, that was not my intent.
I'm not talking about the website in general. I'm talking specifically
about publishing content primarily intended for inclusion in releases. Would
Publication release
On Wed, Dec 2, 2009 at 18:48, Bhuvaneswaran A bhu...@apache.org wrote:
Here's a query related to publishing api docs for Subversion project
periodically.
We tend to update the api docs generated using doxygen and java doc on
a nightly basis. We are evaluating a workaround to publish it
13 matches
Mail list logo
