Products in the Build directory?

[Robert Simmons <Ro...@norcom.de>]

In my continuing quest to understand the build system in order to use it in
a production project, I would like to know what exactly is placed in the
build/cocoon-2.1 directory. I dont see the batch file to run cocoon. I dont
know what I would do with this "build." Could someone please enlighten me on
what this "build" is and how one should use it?

As a matter of fact it seems like cocoon is an academic project only instead
of a production one, especially with the removal of binary distributions. Is
it the intention of the cocoon developers to merely play with cocoon and
shelve it as a silly academic project? 

Sorry about the rant but its frustrating when all I want is a BLANK cocoon
instance ready with jetty packed in that I can start up and run and get
NOTHING. An application that I can fill with content from my customer. 

-- Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Products in the Build directory?

[Bertrand Delacretaz <bd...@codeconsult.ch>]

Le Mercredi, 27 aoû 2003, à 15:24 Europe/Zurich, Robert Simmons a écrit 
:

> In my continuing quest to understand the build system in order to use 
> it in
> a production project, I would like to know what exactly is placed in 
> the
> build/cocoon-2.1 directory. I dont see the batch file to run cocoon. I 
> dont
> know what I would do with this "build." Could someone please enlighten 
> me on
> what this "build" is and how one should use it?

You might want to read this thread, which led to the creation of the 
"standalone-demo" build target:

http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104928858008982&w=2

This explains why it would be unwise to create a deployment-ready setup 
from the incomplete version of Jetty that is found in the Cocoon CVS.

The standard build is meant to be run from the "cocoon.sh" script for 
experimenting, production installations require you to configure Cocoon 
for your favorite web container. See "./build.sh -projecthelp" for a 
description of other builds (like "build war" which is deployable).

> As a matter of fact it seems like cocoon is an academic project only 
> instead
> of a production one, especially with the removal of binary 
> distributions. Is
> it the intention of the cocoon developers to merely play with cocoon 
> and
> shelve it as a silly academic project?

Apart from the fact that such statements might make you unpopular here, 
I think I'm speaking for the team in saying that Cocoon is really 
targeted at developers, who are expected to be competent in deploying 
servlet-based applications.

There was a conscious decision not to go with turnkey deployments, as 
for any serious installation you need to think about which servlet 
container to use and learn enough about it to be able to properly tune 
and debug your setup.

--
   Bertrand Delacretaz
   independent consultant, Lausanne, Switzerland
   http://cvs.apache.org/~bdelacretaz/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

[proposal] Production Build Target (was Re: Products in the Build directory?)

[Geoff Howard <co...@leverageweb.com>]

Timothy Larson wrote:
> --- Geoff Howard <co...@leverageweb.com> wrote:
> ...
> 
>>Can you all agree on which options should define a "production build"?
>>
>>Geoff
> 
> I don't know.  Lets try!
> 
> I suggest that a baseline production build should:
> 
>   Include all components, even scratchpad and deprecated

I'd disagree.  In a production app, I don't want scratchpad or 
deprecated.  And because extra components can have performance 
implications, I want only the components I'll use.  (and I do this my 
self now with a pair of local.xxx.properties)

>   Exclude all samples

Agreed.

>   Exclude all documentation

Agreed (from the webapp)

>   Have an empty <map:pipelines> section in sitemap

Ok.

>   Be easy to specify includes and excludes starting
>   from this baseline configuration.

Includes and excludes of what?  If blocks, it doesn't get any easier (at 
the moment) than editing a local.blocks.properties.  If the things we 
just discussed above, this already exists in the first 10 lines or so of 
[local.]build.properties.

> Anybody who is interested, please speak up
> with your agreement, differences, etc.

This is exactly why I asked.  I'll be surprised if people can agree on 
this.  I think there may be an illusion of common requirements which on 
closer examination will turn out to have mutually exclusive conflicts. 
If not, I think this can be done easily in very little time.

Please, before weighing in, look over build.properties and 
blocks.properties, along with 
http://wiki.cocoondev.org/Wiki.jsp?page=BuildProperties, INSTALL.txt and
http://cocoon.apache.org/2.1/installing/index.html#Building+Cocoon

Geoff



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Products in the Build directory?

[Timothy Larson <ti...@yahoo.com>]

--- Geoff Howard <co...@leverageweb.com> wrote:
...
> Can you all agree on which options should define a "production build"?
> 
> Geoff

I don't know.  Lets try!

I suggest that a baseline production build should:

  Include all components, even scratchpad and deprecated
  Exclude all samples
  Exclude all documentation
  Have an empty <map:pipelines> section in sitemap
  Be easy to specify includes and excludes starting
  from this baseline configuration.

Anybody who is interested, please speak up
with your agreement, differences, etc.

--Tim Larson


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Products in the Build directory?

[Geoff Howard <co...@leverageweb.com>]

Timothy Larson wrote:
> Robert,
> 
> I am running the latest 2.1 development snapshots, but I
> think this also worked with the 2.1 final release as well.
> These are directions to build a "blank" Cocoon webapp.
> 
> In the top-level cocoon-2.1 directory create a file named
> "local.build.properties" and put this content in the file:
> 
> # File: local.build.properties
> # ---- Exclude from Webapp ----
> exclude.webapp.documentation=true
> exclude.webapp.javadocs=true
> exclude.webapp.idldocs=true
> exclude.webapp.samples=true
> # ---- Build Exclusions ----
> exclude.javadocs=true
> exclude.idldocs=true
> # End of file
> 
> Follow the the instructions in "INSTALL.txt":
>   Setup the JAVA_HOME environment variable.
>   Run the build script with no options.
> 
> The directory "cocoon-2.1/build/webapp" is now a webapp
> with no documentation or examples which can be dropped
> in Jetty, Tomcat, etc.  I would not worry about the
> "cocoon-2.1/build/cocoon-2.1" directory.
> 
> If you want to script your customizations to the sitemap
> or other XML configuration files, just use Ant with the
> XConfTool: http://wiki.cocoondev.org/Wiki.jsp?page=XPatchTaskUsage
> 
> It works for me, let me know if you need more help,
> --Tim Larson
> 
> BTW: I agree that there should be a simple build target
> that selects these options for you to build a "blank"
> version of Cocoon.  If you figure out a good way to do
> this, consider submitting a patch to the developers list
> or to Bugzilla.

Can you all agree on which options should define a "production build"?

Geoff

P.S. Welcome back, Robert.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Products in the Build directory?

[Timothy Larson <ti...@yahoo.com>]

Robert,

I am running the latest 2.1 development snapshots, but I
think this also worked with the 2.1 final release as well.
These are directions to build a "blank" Cocoon webapp.

In the top-level cocoon-2.1 directory create a file named
"local.build.properties" and put this content in the file:

# File: local.build.properties
# ---- Exclude from Webapp ----
exclude.webapp.documentation=true
exclude.webapp.javadocs=true
exclude.webapp.idldocs=true
exclude.webapp.samples=true
# ---- Build Exclusions ----
exclude.javadocs=true
exclude.idldocs=true
# End of file

Follow the the instructions in "INSTALL.txt":
  Setup the JAVA_HOME environment variable.
  Run the build script with no options.

The directory "cocoon-2.1/build/webapp" is now a webapp
with no documentation or examples which can be dropped
in Jetty, Tomcat, etc.  I would not worry about the
"cocoon-2.1/build/cocoon-2.1" directory.

If you want to script your customizations to the sitemap
or other XML configuration files, just use Ant with the
XConfTool: http://wiki.cocoondev.org/Wiki.jsp?page=XPatchTaskUsage

It works for me, let me know if you need more help,
--Tim Larson

BTW: I agree that there should be a simple build target
that selects these options for you to build a "blank"
version of Cocoon.  If you figure out a good way to do
this, consider submitting a patch to the developers list
or to Bugzilla.


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org