On Thu, Jan 28, 2010 at 1:04 AM, sorel <johann.so...@geomatys.fr> wrote:
> > The reason why I would like it to be splitted is more a design need. > > Actually geotoolkit alone weight ~10Mb for ~65 Jars. > 65! I need to check this project out, it's obviously bigger than I realised ;-) > With the dependencies it's ~45Mb and ~125 Jars. > Yep, that's quite a lot. > > You can understand that with big project we need to have to handle very > carefully > dependencies of it's overall size will explode. > We have ~100 maven modules to achieve a thin granularity so anyone can make > an > application with just what is needed, not more. > > The reason is for the end applications, an exemple is Java applets or web > applications. > (web container like tomcat/glassfish/jboss start to complain when you go > over 40Mb) > > geotoolkit has plenty of sub projects, constellation, mapfaces, puzzle-gis, > mdweb ... > > I understand that thin control is not a real problem on small projects but > at our level > we start to have a lot of 1+1+1+1 ... if you see what I mean :D. > > I can't force you to split it of course, it's your project. it's just a > kind of wish. > Honestly, I don't mind Osmosis being broken down into smaller pieces. In fact it probably makes a lot of sense. I just don't have the time to do it myself at the moment. I'll support anybody who wishes to have a go at it. Brett
_______________________________________________ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
