Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of hzbarcea@gmail.com designates
 209.85.210.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=RPnMKCCBJuGxNqaDySKzmk3a5mhCQS32VMgJORDPeVrCiWNQ7u29Px7g+09Y7Nfu28
         eimXtCuTApB1QNC3Wt5op0tF0xaK6SGgGBfeqaSosxMNnuIN8aTDPx0uBlYcosCtC3iS
         +PHgJ4N9WL/r0ONqDqiu0p5hpD8lQCzl75Moc=
Message-Id: <05DA1C13-73A9-47F8-BC22-7322CD1902BF@gmail.com>
From: Hadrian Zbarcea <hzbarcea@gmail.com>
To: dev@camel.apache.org
In-Reply-To: <2748945d0910080645j43d65c6fsaf35f43dbdd130bb@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Camel release process - Separation the manual,
 maven reports and  javadoc etc.
Date: Fri, 9 Oct 2009 09:34:27 -0400
References: <5380c69c0910080126x29631912mf9b3b19734edd9d2@mail.gmail.com>
 <2748945d0910080630t11cb7881n9a7f6ba7fc08250f@mail.gmail.com>
 <5380c69c0910080642p7e6fac42k7b03db6ad46681f0@mail.gmail.com>
 <2748945d0910080645j43d65c6fsaf35f43dbdd130bb@mail.gmail.com>

Actually, it's more than that.

The issue with the manual is that it downloads a lot of the wiki  
locally (with imgs and all) to build the pdf.  That's both time and  
bandwidth consuming.
I would also think that camel-web should move somehow.  Either only  
building it when we activate a profile, or move it to a subproject.   
It builds a 30M jar, and uploading it during the release process is a  
lengthy and prone to timeouts.  There are other less used components  
that could move to a subproject. Camel grew kinda big lately.

What if we open a wiki page or jira, throw out some ideas and decide  
together on what to do?

Hadrian


On Oct 8, 2009, at 9:45 AM, Jon Anstey wrote:

> On Thu, Oct 8, 2009 at 11:12 AM, Claus Ibsen <claus.ibsen@gmail.com>  
> wrote:
>
>> On Thu, Oct 8, 2009 at 3:30 PM, Jon Anstey <janstey@gmail.com> wrote:
>>> On Thu, Oct 8, 2009 at 5:56 AM, Claus Ibsen <claus.ibsen@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
>>
>> Ah yeah the -javadoc jars are okay. Its the javadoc link on the camel
>> website I was referring to.
>>
>
> Ohhhh... in that case then I'm +1 for separating from the release  
> process
> too.
>
>
>>
>>
>>
>>>
>>>
>>>> - 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/
>>>
>>
>>
>>
>> --
>> 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/