On Thu, Oct 8, 2009 at 5:56 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Hi > > Hadrian and others. > > The release process for Apache Camel is long and takes much time to do. > Can we split out the creating and publication of > - manual > Don't we still want to include this in the distribution? If we do, we would need to ensure that it gets generated before or during the release process... may be easier to just leave it as is. > - javadoc > This needs to be included with the release no? I think the javadoc jars get published to the maven central repo. Like http://repo2.maven.org/maven2/org/apache/camel/camel-core/2.0.0/camel-core-2.0.0-javadoc.jar > - maven reports (I doubt even these is updated) > Yeah, last updated time right now is 2009-01-18. So maybe they are already "separate" from the release process :) > > I would like to be able to update the javadoc once in a while. So if > there was some new maven goal I could run that would be great. > > The manual generation is error prone. Sometimes the Apache cwiki > returns error code 502 etc. I just fixed that in the maven tooling to > generate an empty placeholder file. > What we could do is to also have a special maven goal that could > release and publish the manual. > > And the maven reports. Either we gotta remove the link to them or have > a goal that works and can publish as well. > > Hadrian what are your thoughts? > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > -- Cheers, Jon http://janstey.blogspot.com/
