Morning all: In getting re-synchronized with the Keel changes, I saw the problems with maven.repo.local and maven.repo.remote. However, I think requiring these always be set the same might not be a good plan overall, and definitely will create incompatabilities with other Maven projects.
Maven will read build.properties in a specific sequence, as defined here: http://maven.apache.org/reference/user-guide.html#Properties_Processing (as I think someone mentioned on the list previously), so what we really need to do is create a build.properties in *one* place, ideally our home directory, then allow it to be used for all projects. E.g. in your $HOME, you should be able to put build.properties: maven.repo.local=/home/keel/keel-build/repository maven.repo.remote=http://keelframework.org/maven,http://ibiblio.org/maven and we can then remove this from *every* project's build.properties. This will allow you to put the local repo anywhere you want, (including the default directory, which is $HOME/.maven/repository) and to organize your maven.repo.remote any way you want, as long as somewhere in it is keelframework.org/maven - and this is only required if you're not building from source locally. Can anyone see a problem with this? I will re-check the plugins to make sure we're not making any assumptions as to the locations of either of these repositories, and fix 'em if we are. Mike http://keelframework.org/documentation.shtml Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
