In this e-mail I describe how I mavenized cocoon. I would like to hear some suggestions and comments about my procedure.
First I realized that Cocoon 2.0.4 contains about 57 libraries (not all are necessary for my project, but to get Cocoon running with Maven, I decided to include all dependencies. Writing all the dependencies into the project.xml is a pain. So I wrote a small application, that creates all dependencies in project.xml and copies the .jar files from the WEB-INF/lib/ folder into the local maven repository.
What do you guys think? Is this the right way, or is there any better way?
I want to create a Maven plugin to convert any old-fashioned project (with an individual lib/ folder) into a mavenized project. Does anyone else see any use for that?
And finally what do you think about the strategy, copying the files into the local repository. This is difficult for team development. I think about automatically creating an archive (zip, jar or tar) that contains all the dependencies, ready for copying to the remote repository. Is that useful?
-Mo.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
