You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Alexander Schatten <al...@gmx.at> on 2003/11/07 04:02:29 UTC
Compilation of Cocoon / Binary Distribution / Different Configurations,
I want to start a new thread, because I had some "compilation problems"
during still unsuccessful experiments with cli. but those are (at least
partly) no cli matters:
(1) To the first point: I believe it to be an extremly bad idea not to
provide an binary distribution, by many reasons, the following might be
the most important:
-- a Cocoon newbie has enough to deal with; that he/she also has to
compile the project is really daunting, believe me! I often hold XML
courses and also try to introduce Cocoon ...
-- Compilation takes a lot of time; I detected between 5 and 30 minutes,
depending on configuration and machine. Again: do we want to adress only
experts? currently we do tax the patience of news users a lot before
they can even start dealing with the main Cocoon issues...
-- If you want to create versions e.g. for production use, you have to
invest a lot of time to understand which blocks might be excluded;
recompilation needs a lot of time and so on... an enerving task!!
so:
(2) I believe, at least 2 or 3 binary distributions have to be
available for download.
However, if by some reasons, I might not understand (yet), no binary
distribution is provided, then *at least* some example build.properties
should be part of the download like
-- the one currently delivered
-- properties, that make CLI working
-- minimal setup
-- production setup (without examples and documentation)
well, this is at least my opinion.
thank you
alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Upayavira <uv...@upaya.co.uk>.
Alexander Schatten wrote:
> Thank you again for feedback; some comments though:
>
> Upayavira wrote:
>
>>
>> Dependencies between blocks are a relatively new thing - at the
>> moment we've just dealt with it with comments in the
>> blocks.properties file, which is not ideal, but better than not
>> telling anyone at all.
>
>
> yes, but unfortunately they are far from complete: since the last
> email I already had to restart the build twice because of not marked
> dependencies... this is really extremly awkward.
I agree it is awkward. If we can come up with a better way of
'annotating' the blocks.properties file, then I'm sure no-one will complain.
>> You probably perceive a resistance to helping to improve stuff like
>> the build process, or to making binaries available. This, I believe,
>> is because developers would rather concentrate on implementing real
>> blocks, rather than putting effort into the current build process,
>> which was _always_ seen as a temporary measure.
>
> yes, I think you have established that, and I understand it.
Ok.
> However, I have the impression, that the Cocoon developers, which are
> is very obviously a group of excellent developers, sometimes oversees
> the fact, that Cocoon is not longer a hacker tool, but there are
> thousands of "normal" users outside; and when you announce a new
> release, certain basic attributes should exists.
>
> One is, that the build and installation is transparent even to
> non-Cocoon-contributors;
Cocoon isn't a simple thing to use. I think we have to accept that. And
we do have a super block system in the pipeline. In the meantime, if we
can come up with relatively simple changes to our existing setup, then,
as I say, I think they'll be accepted.
> I might not be the brightest of all Cocoon users, but you might assume
> that I am at least the "average dummy user", and I report the problems
> and issues, because I love the project; many others simply dump the
> idea to use Cocoon.
And I for one appreciate it!
>>> cant you provide a set of 3-5 blocks.properties files at least, so
>>> that every user can choose from a set of working properties the best
>>> suited for the problem?
>>
>> I've watched this, again, and again, and again. No two people can
>> agree on what they need and what they don't. It is simply not
>> possible to identify a few tailored blocks.properties, as there are
>> just so many relevant combinations.
>
> Sorry, to point this out again: this is the usual "guru-problem": not
> agreeing about a solution, because no suggested solution offers 100%
> quality (only 80% at best), and the result is an eternal discussion
> with a "no-solution" that has the quality of 20% (as of now). And 95%
> of Cocoon installations use the "full program" as in the current
> properties file. This was not intended, I believe.
That's how it was with 2.0. If some people can work out how to cut down
within 2.1, then that's good, IMO.
> At this point I have to say:
>
> *please* -- for the sake of the normal user -- take a decision, and
> put 3-5 properties files into the release!! They can at least be a
> guidance for the unskilled ones. and the expert can configure as he
> does it right now.
What I propose (at least for now) is to improve the contents of the
blocks.properties file so that an unskilled user can work out what they
need to do.
E.g. If all you use is the basic Cocoon facilities (FileGenerator,
XSLTTransformer, HTMLSerializer) then you can disable ALL blocks.
Use with CLI
Note: currently the CLI will not work with these blocks included: XXX,
XXX, XXX
What do you think? Maybe you can suggest some other notes that would
help within the blocks.properties file.
Regards, Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Nicolas Toper <nt...@jouve.fr>.
Yes you're right, I meant something more easier to use but on the Website
and adding new processes (but automatic).
On the broadening base, let's look at PHP vs EJB (I know this is stupid :=))
EJB doesn't have so many users as PHP but it doesn't matters b/c EJB are
used in specific context...
Some core Cocoon's concept could be used not only for XML publishing but for
all kind of websites.
-----Message d'origine-----
De : Alexander Schatten [mailto:alasan@gmx.at]
Envoye : vendredi 7 novembre 2003 15:34
A : users@cocoon.apache.org
Objet : Re: Compilation of Cocoon / Binary Distribution / Different
Configurations,
Nicolas Toper wrote:
>Yes, but we would need to rethink the Cocoon build/releases cycles to
>simplify the installation...
>
>
no, I do not see why; As an expert one could rather easily provide such
an binary installation package. no problem at all I see.
>But we first need to know if we want to broaden the user base or the
>situation is fine (cocoon is seen as a powerful but difficult product)
>
>
yes, *this* is an important consideration; I have no clear answer yet. I
would suggest, that we should try to broaden the perspective.
you might not forget, that Cocoon is for many purposes not much more
complex then e.g. PHP. If you want to do XML publishing and you would
have the simple installation as described it is not so complex:
with things like Automounting of subsitemaps (great feature) and the like.
you only should remove the complexity from the installation and mark
*much, much clearer* what is ready for prime-time and what is experimental.
I often hear complaints like: Cocoon is nice, but I do not know where to
start when I want to solve problem X; there is solution A, B and C, ...
like: a dozen of form frameworks; database actions, SQL transformer,
XSP, logicsheets, ...
and no "best practice" document that is problem oriented...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Alexander Schatten <al...@gmx.at>.
Nicolas Toper wrote:
>Yes, but we would need to rethink the Cocoon build/releases cycles to
>simplify the installation...
>
>
no, I do not see why; As an expert one could rather easily provide such
an binary installation package. no problem at all I see.
>But we first need to know if we want to broaden the user base or the
>situation is fine (cocoon is seen as a powerful but difficult product)
>
>
yes, *this* is an important consideration; I have no clear answer yet. I
would suggest, that we should try to broaden the perspective.
you might not forget, that Cocoon is for many purposes not much more
complex then e.g. PHP. If you want to do XML publishing and you would
have the simple installation as described it is not so complex:
with things like Automounting of subsitemaps (great feature) and the like.
you only should remove the complexity from the installation and mark
*much, much clearer* what is ready for prime-time and what is experimental.
I often hear complaints like: Cocoon is nice, but I do not know where to
start when I want to solve problem X; there is solution A, B and C, ...
like: a dozen of form frameworks; database actions, SQL transformer,
XSP, logicsheets, ...
and no "best practice" document that is problem oriented...
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Nicolas Toper <nt...@jouve.fr>.
Yes, but we would need to rethink the Cocoon build/releases cycles to
simplify the installation...
But we first need to know if we want to broaden the user base or the
situation is fine (cocoon is seen as a powerful but difficult product)
-----Message d'origine-----
De : Alexander Schatten [mailto:alasan@gmx.at]
Envoye : vendredi 7 novembre 2003 14:55
A : users@cocoon.apache.org
Objet : Re: Compilation of Cocoon / Binary Distribution / Different
Configurations,
Nicolas Toper wrote:
>for instance I know tons of webdeveloper with no formal training and admin
>sys competencies. They use EasyPHP (a great product by the way) to develop
>their websites. Why? B/C it's easy to install on windows and for now
>definitely easier than Cocoon.
>
>
>
(1) yes, this is an important issue. Cocoon < 2 was extremly difficult
to install; so what I did then for my courses was to bundle a
tomcat/cocoon installation for my customers to download, because
otherwise, they would never have used Cocoon
(2) then I was so happy about the 2.0 release, because installation
meant to get the binary distribution and copy the war file into the
tomcat webapps directory (also binary distribution available). Although
an even better solution would have been to bundle tomcat/jetty with
Cocoon. simple unzip and start.
(3) Now we have the exasperating source distribution/compilation problem
that in result is an excellent measurement to avoid new Cocoon users
(particularly when they are no Java developers): If a new user-non Java
developer reads, that he has to install the JVM and compile Cocoon
before usage, he will switch to PHP or something else.
(4a) Even worse: there are some details that are very confusing for new
users: e.g. the "cocoon-latest-..." naming on the download. Even I was
stumbeling, because I though, this might be some developer snapshot,
some unstable release and I was searching for some release; and after I
found no "2.x" marked release I used this one.
(4b) References to cvs are *completley* useless for non-experts. No
"newbie user" who is not programmer will do this, particularly under
windows, where you have no cvs clients installed.
So most probably the new distribution strategy is a clear and solid step
backward.
To concluce: if the Cocoon Community is interested in
non-Java-expert-Cocoon users, there is to provide a binary installation
that has to be downloaded, unpacked and startet.
this is at least my opinion.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Alexander Schatten <al...@gmx.at>.
Nicolas Toper wrote:
>for instance I know tons of webdeveloper with no formal training and admin
>sys competencies. They use EasyPHP (a great product by the way) to develop
>their websites. Why? B/C it's easy to install on windows and for now
>definitely easier than Cocoon.
>
>
>
(1) yes, this is an important issue. Cocoon < 2 was extremly difficult
to install; so what I did then for my courses was to bundle a
tomcat/cocoon installation for my customers to download, because
otherwise, they would never have used Cocoon
(2) then I was so happy about the 2.0 release, because installation
meant to get the binary distribution and copy the war file into the
tomcat webapps directory (also binary distribution available). Although
an even better solution would have been to bundle tomcat/jetty with
Cocoon. simple unzip and start.
(3) Now we have the exasperating source distribution/compilation problem
that in result is an excellent measurement to avoid new Cocoon users
(particularly when they are no Java developers): If a new user-non Java
developer reads, that he has to install the JVM and compile Cocoon
before usage, he will switch to PHP or something else.
(4a) Even worse: there are some details that are very confusing for new
users: e.g. the "cocoon-latest-..." naming on the download. Even I was
stumbeling, because I though, this might be some developer snapshot,
some unstable release and I was searching for some release; and after I
found no "2.x" marked release I used this one.
(4b) References to cvs are *completley* useless for non-experts. No
"newbie user" who is not programmer will do this, particularly under
windows, where you have no cvs clients installed.
So most probably the new distribution strategy is a clear and solid step
backward.
To concluce: if the Cocoon Community is interested in
non-Java-expert-Cocoon users, there is to provide a binary installation
that has to be downloaded, unpacked and startet.
this is at least my opinion.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Nicolas Toper <nt...@jouve.fr>.
I completely agree. I'm a fairly new Cocoon user and it took me a while to
get used to it...
Besides, look at MySQL or JBoss: they try to have an easy install process.
Even Microsoft is doing it too...
I think it's good to smooth the installation process for a new user. The
easiest it is, the most will try and eventually they'll use it.
for instance I know tons of webdeveloper with no formal training and admin
sys competencies. They use EasyPHP (a great product by the way) to develop
their websites. Why? B/C it's easy to install on windows and for now
definitely easier than Cocoon.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Alexander Schatten <al...@gmx.at>.
Thank you again for feedback; some comments though:
Upayavira wrote:
>
> Dependencies between blocks are a relatively new thing - at the moment
> we've just dealt with it with comments in the blocks.properties file,
> which is not ideal, but better than not telling anyone at all.
yes, but unfortunately they are far from complete: since the last email
I already had to restart the build twice because of not marked
dependencies... this is really extremly awkward.
>
>
> You probably perceive a resistance to helping to improve stuff like
> the build process, or to making binaries available. This, I believe,
> is because developers would rather concentrate on implementing real
> blocks, rather than putting effort into the current build process,
> which was _always_ seen as a temporary measure.
yes, I think you have established that, and I understand it.
However, I have the impression, that the Cocoon developers, which are is
very obviously a group of excellent developers, sometimes oversees the
fact, that Cocoon is not longer a hacker tool, but there are thousands
of "normal" users outside; and when you announce a new release, certain
basic attributes should exists.
One is, that the build and installation is transparent even to
non-Cocoon-contributors;
I might not be the brightest of all Cocoon users, but you might assume
that I am at least the "average dummy user", and I report the problems
and issues, because I love the project; many others simply dump the idea
to use Cocoon.
>
>> cant you provide a set of 3-5 blocks.properties files at least, so
>> that every user can choose from a set of working properties the best
>> suited for the problem?
>
>
> I've watched this, again, and again, and again. No two people can
> agree on what they need and what they don't. It is simply not possible
> to identify a few tailored blocks.properties, as there are just so
> many relevant combinations.
Sorry, to point this out again: this is the usual "guru-problem": not
agreeing about a solution, because no suggested solution offers 100%
quality (only 80% at best), and the result is an eternal discussion with
a "no-solution" that has the quality of 20% (as of now). And 95% of
Cocoon installations use the "full program" as in the current properties
file. This was not intended, I believe.
At this point I have to say:
*please* -- for the sake of the normal user -- take a decision, and put
3-5 properties files into the release!! They can at least be a guidance
for the unskilled ones. and the expert can configure as he does it right
now.
thank you!
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Alexander Schatten <al...@gmx.at>.
Reinhard Poetz wrote:
>>I've watched this, again, and again, and again. No two people
>>can agree
>>on what they need and what they don't. It is simply not possible to
>>identify a few tailored blocks.properties, as there are just so many
>>relevant combinations.
>>
>>
>
>I haven't follow this tread very close but maybe a cli.blocks.properties
>file could help. It could contain all blocks where we are sure they work
>with CLI - the others are excluded by default.
>
>
>
yes, this was my suggestion --> my other posting.
I suggested (to be complete) properties files for e.g.,:
(1) full installation
(2) working CLI
(3) minimal installation
(4) suggested installation for production use (without docs, ...)
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Reinhard Poetz <re...@apache.org>.
> I've watched this, again, and again, and again. No two people
> can agree
> on what they need and what they don't. It is simply not possible to
> identify a few tailored blocks.properties, as there are just so many
> relevant combinations.
I haven't follow this tread very close but maybe a cli.blocks.properties
file could help. It could contain all blocks where we are sure they work
with CLI - the others are excluded by default.
--
Reinhard
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Upayavira <uv...@upaya.co.uk>.
Alexander Schatten wrote:
> Upayavira wrote:
>
>> Alexander,
>>
>> There are a whole host of reasons why we only distribute a source
>> version at present. When we get on with implemening cocoon blocks,
>> all will change. For the time being, a source distribution is what
>> we've got. (Reason for source distribution: it is the only simple way
>> to allow a user to switch on and off different blocks and other bits
>> within Cocoon). It is not possible at present to create a 'production
>> build', as everyone will disagree as to what should go in 'their'
>> production system.
>>
>> I certainly agree that the CLI could be made easier to use. For
>> example, I belive that at present, compiling Cocoon with the
>> Authentication framework present, breaks the CLI. That should not
>> happen.
>
>
> unfortunately this is really an adventure game if you are no Cocoon
> contributor: e.g., I just tried to follow your suggestion and removed
> the authentication block; there is a note about a dependency with the
> session-fw block, and so I removed both of them.
>
> started compilation.
>
> --> error
>
> why?
>
> because there is also the portal block, and this one is depending on
> authentication, I belive, but this dependency is *not* noted...
>
> the last days I spent at least 4-5 hours only trying to compile
> reduced cocoon versions...
>
> so you have to know one thing: in my experience, there are no cocoon
> users I know that do anything else then compile with the default
> settings, except explicit Cocoon contributors, who know, what they do.
> because it is very complex to understand the dependencies and to get
> whats happening. and because (see above) it is an extremly time
> consuming undertaking.
Dependencies between blocks are a relatively new thing - at the moment
we've just dealt with it with comments in the blocks.properties file,
which is not ideal, but better than not telling anyone at all.
> so what you did not answer (as I have to notice, that you do not want
> to share binary versions, and I still do not know why, because there
> is the possibility (as it always was) to provide binary as well as
> source distributions for those who want to configure all stuff by
> themselve) is the following:
This is the current situation (with some history):
1) For 2.0, we issued binaries, and those binaries included everything
2) For 2.1, we started having 'blocks', and people complained that they
didn't want everything
3) Stefano rewrote the build process so that it could include/exclude
blocks as desired.
4) It was proposed to offer only a source build, as this allows users to
configure Cocoon to their needs, something that at the moment would be
hard to do on a prebuilt system.
4) Stefano proposed 'real blocks' (read more on the wiki), which will
allow for runtime deployment of precompiled 'blocks', which can contain
components, but also sitemap snippets and other files, and his proposals
have been generally accepted as a good idea
5) We have started a 2.2 repository, in which we will hopefully soon
start coding real blocks.
You probably perceive a resistance to helping to improve stuff like the
build process, or to making binaries available. This, I believe, is
because developers would rather concentrate on implementing real blocks,
rather than putting effort into the current build process, which was
_always_ seen as a temporary measure.
However, I think there's a value in putting descriptions of the blocks
into the blocks.properties file itself. I'm going to propose this now.
> cant you provide a set of 3-5 blocks.properties files at least, so
> that every user can choose from a set of working properties the best
> suited for the problem?
I've watched this, again, and again, and again. No two people can agree
on what they need and what they don't. It is simply not possible to
identify a few tailored blocks.properties, as there are just so many
relevant combinations.
I think my advice would be to switch off _everything_ and work from there.
>> The CLI should work by unpacking the source archive then doing:
>> build webapp
>> cocoon cli -x cli.xconf
>>
>> and off it goes.
>>
>> Over time I'll see what I can do to get it there.
>>
> yes, I hope too!
>
> btw. I will answer the other email soon, I just want to test, whether
> CLI will work with cocoon compiled with authentication excluded.
Great.
Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Alexander Schatten <al...@gmx.at>.
Upayavira wrote:
> Alexander,
>
> There are a whole host of reasons why we only distribute a source
> version at present. When we get on with implemening cocoon blocks, all
> will change. For the time being, a source distribution is what we've
> got. (Reason for source distribution: it is the only simple way to
> allow a user to switch on and off different blocks and other bits
> within Cocoon). It is not possible at present to create a 'production
> build', as everyone will disagree as to what should go in 'their'
> production system.
>
> I certainly agree that the CLI could be made easier to use. For
> example, I belive that at present, compiling Cocoon with the
> Authentication framework present, breaks the CLI. That should not happen.
unfortunately this is really an adventure game if you are no Cocoon
contributor: e.g., I just tried to follow your suggestion and removed
the authentication block; there is a note about a dependency with the
session-fw block, and so I removed both of them.
started compilation.
--> error
why?
because there is also the portal block, and this one is depending on
authentication, I belive, but this dependency is *not* noted...
the last days I spent at least 4-5 hours only trying to compile reduced
cocoon versions...
so you have to know one thing: in my experience, there are no cocoon
users I know that do anything else then compile with the default
settings, except explicit Cocoon contributors, who know, what they do.
because it is very complex to understand the dependencies and to get
whats happening. and because (see above) it is an extremly time
consuming undertaking.
so what you did not answer (as I have to notice, that you do not want to
share binary versions, and I still do not know why, because there is the
possibility (as it always was) to provide binary as well as source
distributions for those who want to configure all stuff by themselve) is
the following:
cant you provide a set of 3-5 blocks.properties files at least, so that
every user can choose from a set of working properties the best suited
for the problem?
>
> The CLI should work by unpacking the source archive then doing:
> build webapp
> cocoon cli -x cli.xconf
>
> and off it goes.
>
> Over time I'll see what I can do to get it there.
>
yes, I hope too!
btw. I will answer the other email soon, I just want to test, whether
CLI will work with cocoon compiled with authentication excluded.
thank you for the suggestions!
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Compilation of Cocoon / Binary Distribution / Different Configurations,
Posted by Upayavira <uv...@upaya.co.uk>.
Alexander,
There are a whole host of reasons why we only distribute a source
version at present. When we get on with implemening cocoon blocks, all
will change. For the time being, a source distribution is what we've
got. (Reason for source distribution: it is the only simple way to allow
a user to switch on and off different blocks and other bits within
Cocoon). It is not possible at present to create a 'production build',
as everyone will disagree as to what should go in 'their' production system.
I certainly agree that the CLI could be made easier to use. For example,
I belive that at present, compiling Cocoon with the Authentication
framework present, breaks the CLI. That should not happen.
The CLI should work by unpacking the source archive then doing:
build webapp
cocoon cli -x cli.xconf
and off it goes.
Over time I'll see what I can do to get it there.
Regards, Upayavira
Alexander Schatten wrote:
> I want to start a new thread, because I had some "compilation
> problems" during still unsuccessful experiments with cli. but those
> are (at least partly) no cli matters:
>
> (1) To the first point: I believe it to be an extremly bad idea not to
> provide an binary distribution, by many reasons, the following might
> be the most important:
>
> -- a Cocoon newbie has enough to deal with; that he/she also has to
> compile the project is really daunting, believe me! I often hold XML
> courses and also try to introduce Cocoon ...
>
> -- Compilation takes a lot of time; I detected between 5 and 30
> minutes, depending on configuration and machine. Again: do we want to
> adress only experts? currently we do tax the patience of news users a
> lot before they can even start dealing with the main Cocoon issues...
>
> -- If you want to create versions e.g. for production use, you have to
> invest a lot of time to understand which blocks might be excluded;
> recompilation needs a lot of time and so on... an enerving task!!
>
> so:
>
> (2) I believe, at least 2 or 3 binary distributions have to be
> available for download.
>
> However, if by some reasons, I might not understand (yet), no binary
> distribution is provided, then *at least* some example
> build.properties should be part of the download like
>
> -- the one currently delivered
> -- properties, that make CLI working
> -- minimal setup
> -- production setup (without examples and documentation)
>
>
> well, this is at least my opinion.
>
>
> thank you
>
>
> alex
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org