"Stripping" the Cocoon source tree

[Bart Molenkamp <b....@bizzdesign.nl>]

Hi all,

Is there any automated way for stripping the Cocoon source tree? I only
need the core code and some blocks. I want to remove unused blocks,
remove all samples, remove all documentation, remove as much tools as
possible, removing unused jars from lib/optional, etc.

I want this, because I want to include the Cocoon source in my local
Subversion repository as a "vendor branch" (see the SVN book,
http://svnbook.red-bean.com/en/1.0/ch07s04.html) but I think that if I
add the entire Cocoon source tree to it, it might give performance
problems.

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?

Thanks,
Bart.

Re: "Stripping" the Cocoon source tree

[Jorg Heymans <jh...@domek.be>]

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

RE: "Stripping" the Cocoon source tree

[Eric Jacob <er...@bell.ca>]

Hi,

I've just commit an how-to on building Cocoon with Maven.

http://wiki.apache.org/cocoon/HowToBuildAndDeployCocoonWithMaven

It is not perfect, but it is a start.

Hope this help,

Eric

-----Original Message-----
From: Ralph Goers [mailto:Ralph.Goers@dslextreme.com] 
Sent: Wednesday, December 01, 2004 9:34 AM
To: dev@cocoon.apache.org
Subject: Re: "Stripping" the Cocoon source tree

Bart Molenkamp wrote:

>Hi all,
>
>Is there any automated way for stripping the Cocoon source tree? I only
>need the core code and some blocks. I want to remove unused blocks,
>remove all samples, remove all documentation, remove as much tools as
>possible, removing unused jars from lib/optional, etc.
>
>I want this, because I want to include the Cocoon source in my local
>Subversion repository as a "vendor branch" (see the SVN book,
>http://svnbook.red-bean.com/en/1.0/ch07s04.html) but I think that if I
>add the entire Cocoon source tree to it, it might give performance
>problems.
>
>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?
>
>Thanks,
>Bart.
>  
>
I suggest you look at the user's forum archives. There was a discussion 
about this just last week.

Ralph

Re: "Stripping" the Cocoon source tree

[Ralph Goers <Ra...@dslextreme.com>]

Bart Molenkamp wrote:

>Hi all,
>
>Is there any automated way for stripping the Cocoon source tree? I only
>need the core code and some blocks. I want to remove unused blocks,
>remove all samples, remove all documentation, remove as much tools as
>possible, removing unused jars from lib/optional, etc.
>
>I want this, because I want to include the Cocoon source in my local
>Subversion repository as a "vendor branch" (see the SVN book,
>http://svnbook.red-bean.com/en/1.0/ch07s04.html) but I think that if I
>add the entire Cocoon source tree to it, it might give performance
>problems.
>
>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?
>
>Thanks,
>Bart.
>  
>
I suggest you look at the user's forum archives. There was a discussion 
about this just last week.

Ralph

Re: "Stripping" the Cocoon source tree

[Mark Lundquist <ml...@wrinkledog.com>]

On Dec 1, 2004, at 1:34 AM, Bart Molenkamp wrote:

> Hi all,
>
> Is there any automated way for stripping the Cocoon source tree? I only
> need the core code and some blocks. I want to remove unused blocks,
> remove all samples, remove all documentation, remove as much tools as
> possible, removing unused jars from lib/optional, etc.
>
> I want this, because I want to include the Cocoon source in my local
> Subversion repository as a "vendor branch" (see the SVN book,
> http://svnbook.red-bean.com/en/1.0/ch07s04.html) but I think that if I
> add the entire Cocoon source tree to it, it might give performance
> problems.

See http://wiki.apache.org/cocoon/CocoonVendorBranch (just added! :-)

> 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?

For me, it's not at all.

I don't to a local Cocoon build within each project; I maintain builds 
of the Cocoon distro that I can share among many projects (although I 
can use a local Cocoon build for a project if need be).  But until we 
get our real shared repository support into the Cocoon build system, 
I'm using a "Cocoon-centric" repository scheme, where the lib/ 
directory in the Cocoon build _is_ my repository.  I have an ant task 
that copies WEB-INF from the 'coon build, then copies needed whatever 
additional jars it needs (e.g. Hibernate, Spring etc.) out of 
lib/optional.  It's just easier that way.

HTH,
-ml-