A few months ago, I developed a Groovy based component for Cocoon 2.2. I found the maven support very good. There were, at that time, a few very helpful archetypes that made setting up the project easy. I remember the Cocoon community as being very active, friendly and supportive. From my experience, I'd switch to Cocoon 2.2, as it is tailored to use maven. Of course, it depends on the complexity of your Cocoon 2.1.11 project and your Cocoon background. Anyway, you should carefully follow the instructions on the Cocoon web site / wikis.
HTH Armin Peter Horlock schrieb: > Hi, > > We are using Cocoon 2.1.11 with Maven and Java 6. > > I just joined the company, and I get a few thousand errors in eclipse when I > import the project - > As it seems the reason is that Java 6 includes a lot of new org.w3c classes, > that hadn't been in the other JDKs before, > so these classes were implemented by third party projects - now with Java 6 > both versions > clash and I get those errors, while, magically, everything works fine on the > other developers' machines - > I assume it works for them because they do have Java 4, 5 and 6 on their > machines, or whatsoever - > but instead of trying to adjust my system I would like to do it proper and > to make it work for every "clean system" too. > > Does anyone of you have a pom for Cocoon 2.1.11, or do you know if I could > update to Cocoon 2.2 without any worries? > I don't know much about Cocoon yet, but it seems there are several Cocoon > plugins for Cocoon 2.2. The project, however, > neither seems to provide a pom, but maybe it's not necessary because you can > use the plugins instead? > > Any help appreciated. > > Thanks in advance, > > Peter > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
