Mike/All,
The clnt-* module artifactId-s were keel-clnt-* instead of clnt-*, not matching the CVS module/directory names. This was messing up Eclipse projects, when the .project/.classpath was generated by Maven. I went through and changed all the artifactId-s, and changed all the references in various project.xml, module-*.properties, and the example projects all, default, helm, minimal.
Until the newly named JARs are uploaded to the Maven repo on keelframework.org, you can use "maven -Dgoal=jar:install multiproject:goal" to install the new JARs in your local repo. I found that defining the following env. variable, "MAVEN_OPTS=-XX:MaxPermSize=128m -Xmx256m", avoids Mavens OutofMemory error when doing a multiproject install.
Sorry for the disruption...but figured better now than later...
Shash
http://keelframework.org/documentation.shtml Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
