The project will be hosted on sourceforge so I can't really setup my own repository for this. Another option would be to ship dependencies not available on public repos with my distribution. But I want do avoid this if possible to keep download size for updates as small as possible.
On 9/10/05, Jorg Heymans <[EMAIL PROTECTED]> wrote: > > Stefan Podkowinski wrote: > > > I'm currently working on a project that does bundle the cform and > > portal block + core classes and is being build by maven1. This works > > quite well, the only problem is that some of cocoons dependencies > > cannot be found in the well known public repositories, mostly > > snapshot/dated jars such as rhino. > > > I usually put these in a company-wide maven proxy [1], not a perfect > solution but for apps deployed inside the company domain it does the trick. > > > dependences. Creating pom descriptors for each block would also be > > helpfull. > > pom descriptors are being created for every block yes. > > > Regards > Jorg > > [1] http://maven-proxy.codehaus.org/ > >
