One of the nice things about the Cocoon 2.1x line is that oldies like me can just use a text editor and the command line. I never found Eclipse was worth the hassle and I was never quite sure what was going on behind the scenes. That risk can stifle progress and burn precious time when you start a new job and your colleagues are wanting to see some results of working on their codebase. they probably aren't sure how things are set-up either and no-one wants to look stupid by admitting their lack of knowledge. Sometimes the niceties of your environment. have to take a back seat to getting a  simple tool-chain in place.

No help here I'm afraid just the ramblings of an ageing hacker :)

2009/6/12 Peter Horlock <peter.horlock@googlemail.com>
Well, that was pretty dumb of me, that actually worked. Dunno why, I remeber I read I had to say cocoon.sh only.

However, now it seems like it build a file called "cocoon.jar" - I replaced the one I had in my Maven repo with this new one.
Are there anywhere any other jar files it generated?

E.g.:
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-xsp</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-chaperon</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-jsp</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-profiler</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-eventcache</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-mail</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-axis</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-taglib</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-forms</artifactId>
                <version>2.1.11</version>
            </dependency>
            <dependency>
                <groupId>cocoon</groupId>
                <artifactId>cocoon-fop</artifactId>
                <version>2.1.11</version>
            </dependency>


Couldn't find any of these files in the build folder. I am not even sure if what I am doing makes any sense - all I am trying to do is to get those strange XML errors in eclipse disapear - some jars overwrite classes of the org.w3c package of Java 6.

I guess I still need a proper pom for cocoon, or so...


Thanks,

Peter