Jody Garnett a écrit :
> unless we commit jar files
> it is *very* hard to make udig something you can check out and build. We
> have done a lot of work with scripts and so on but it feels
> like a loosing battle. Svn is supposed to have the ability to link; but
> you need to link to another svn repository.
I was not criticizing since I'm doing only a cleanup of geotools svn. Since I'm
not touching to udig SVN, I'm not in position to make anything else than a "by
the way" observation, and my observation may very well be irrelevant...
> I am considering setting up a seperate svn just to hold jars; so the
> udig check out can link to these things as needed. Is this a stupid
> idea? And do you have any suggestions on an approach that could be used.
It would make a smaller SVN to backup for the administrator, but I don't know if
you use Maven to build uDig, and if so what are the problems that prevented the
dependencies mechanism to work. A possible workaround could have been to put all
the JARs in the "resources" directory of a Maven module (not necessarly commited
to SVN, except maybe the pom.xml and directory structure) and get other modules
to download and unpack those JARs using the Maven "resources" plugin (if I
remember right).
Really not sure it is relevant though...
Martin
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
