cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <lgaw...@mobilebox.pl>
Subject Re: "Stripping" the Cocoon source tree
Date Wed, 01 Dec 2004 13:00:55 GMT
Jorg Heymans wrote:
> My solution is not perfect ;)
> 
> But in this case, i would apply the patch to the local source, build 
> again, rename the jars to cocoon-patched-bart-2.1.7dev or thelike and 
> upload those to my local maven proxy. Adjust the project definition and 
> you're done.
> It's not so much that maven helps you downloading and centralizing jars, 
> the project definition makes it clear against which cocoon version you 
> need to compile/build/release a project.
> 
> Regards
> Jorg
> 
> Bart Molenkamp wrote:
> 
>> Hi Jorg,
>>
>> Thanks for your reply. Ok, so maven helps downloading the correct
>> version of Cocoon a specific version of your application. That solves a
>> part of the problem. But what if you need to make a change to some
>> Cocoon classes, or apply a patch (and for some reason you are forced to
>> maintain it in your repository e.g. because there is a chance that the
>> patch won't be applied in the Cocoon SVN repository before you release
>> your project)?
>>
>> Bart.
>>
>>
>>> -----Original Message-----
>>> From: news [mailto:news@sea.gmane.org] On Behalf Of Jorg Heymans
>>> Sent: Wednesday, December 01, 2004 10:46 AM
>>> To: dev@cocoon.apache.org
>>> Subject: Re: "Stripping" the Cocoon source tree
>>>
>>>
>>>
>>> Bart Molenkamp wrote:
>>>
>>>> Hi all,
>>>>
>>>>
>>>> I'm also very curious how other people include Cocoon in their
>>>> repositories for their Cocoon-based applications (just a guess that
>>
>>
>> many
>>
>>>> of you guys use Cocoon for other projects). The entire source tree,
>>
>>
>> or
>>
>>>> just the build (binary), or not at all?
>>>
>>>
>>> We use maven and define the cocoon version to be used in the
>>> projectdefinition. When a new release comes out, we build the cocoon
>>> jars with all blocks, rename them to adhere to maven conventions and
>>> upload them to our local maven proxy.
>>>
>>> HTH
>>> Jorg
>>
>>
>>
>>
> 
I am following a little bit modified solution described at. I am storing 
cocoon binaries in /tools directory and rebuilding once a while.

-- 
Leszek Gawron                                      lgawron@mobilebox.pl
Project Manager                                    MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65

Mime
View raw message