cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simone Tripodi <>
Subject Re: Meet Cocoon CLI
Date Wed, 02 Nov 2011 08:09:48 GMT
Hi Torsten!!
Believe me or not, I have a mail in my draft box where describing an
alternative approach to XML sitemap, but never had the time (and the
brave :P) to complete and send :D

Just to give you more background on my madness: I thought about a CLI
tool because I used to test XSLTs using `xsltproc` from CLI, so IMHO
having a tool that would allow users testing an XML Pipeline would
alleviate users the suffering of not seeing the intermediate results,
unless the application is not properly deployed.
*My* issue - that induced me on the XML format - is that via CLI,
expressing a pipeline would be not so easy :/
Moreover, using my beloved commons-digester allowed me having a
working PoC in less than one day.
Anyway, I agree that something different from XML should be provided
to our users, my other issue is that I don't have good background on
JavaCC/AnTLR to write a DSL... and haven't taken a look yet on
XText... would you recommend it?

About packaging: I use the Application Assembler Maven Plugin[1] to
create the application - it generates even the scripts for both
linux/windows, so not so hard to manage.

I would be really pleased if you could share more thoughts and
suggestions on how to deliver our users a fresh new Cocoon CLI

All the best, have  anice day!


On Tue, Nov 1, 2011 at 9:41 PM, Torsten Curdt <> wrote:
>> So, what I did today is replicating the Apache Ant/Maven behavior, I
>> mean, cocoon-cli is a console application that takes in input an XML
>> pipeline descriptor - called c3p.xml by default - that looks like very
>> similar to ant build.xml file:
> ...which is not necessarily is a good thing :)
> I just had to think of an old thread about an even older discussion
> I think many people have come to terms with XML in the sense that it
> is just not great for humans to write. C3 could be perfect to come up
> with just a DSL
>> To package it, it is enough launching `mvn package` under
>> /cocoon-cli[1], its execution will produce .tar.gaz and .zip packages
>> under /cocoon-cli/target, that contain a multi-platform application
>> which directories tree looks like the Maven one:
>> .
>> ├── README
>> ├── bin
>> │   ├── c3pipe
>> │   └── c3pipe.bat
>> ├── lib
>>     ├── cocoon-cli-3.0.0-beta-1-SNAPSHOT.jar
>>     ├── cocoon-pipeline-3.0.0-beta-1-SNAPSHOT.jar
>>     ├── cocoon-sax-3.0.0-beta-1-SNAPSHOT.jar
>>     ├── cocoon-util-3.0.0-beta-1-SNAPSHOT.jar
>>     ├── cocoon-xml-2.0.2.jar
>>     ├── commons-beanutils-1.8.3.jar
>>     ├── commons-digester3-3.1.jar
>>     ├── jcl-over-slf4j-1.6.1.jar
>>     ├── jcommander-1.17.jar
>>     ├── logback-classic-0.9.29.jar
>>     ├── logback-core-0.9.29.jar
>>     └── slf4j-api-1.6.1.jar
> I would just use the maven shade plugin and make it a runnable jar.
> Makes it much easier to handle.
>> WDYT? Feedbacks are needed and of course participation is open,
>> everybody interested is welcome! :)
> Go go go Simone! :)
> cheers,
> Torsten

View raw message