Raj,

>Attempting to download app-crud-2.2.jar.
>WARNING: Failed to download app-crud-2.2.jar.
>Attempting to download app-personality-1.1.jar.
>WARNING: Failed to download app-personality-1.1.jar.
>  
>
OK, the default project has just been updated with many last versions of
modules in CVS, but not all the associated jars are already available
from http://www.keelframework.org/maven/keel/jars

So, 2 solutions:
- check the last versions available in the above repository and put them
in default/program.xml file
- rebuild your locale maven repository.

The first option is tedious but simple and sure.

For the second option, here are the steps:

   * Update Keel  from CVS, included tool-xxxx, (see email from  
28/03/05 on the ML ) :

   * add in  {home}/build.properties :

       maven.repo.local=c:/dev/.maven/repository
                
maven.repo.remote=http://www.ibiblio.org/maven,http://www.apache.org/dist/java-repository,http://svn.apache.org/repos/asf/excalibur/repository,http://www.keelframework.org/maven


       maven.multiproject.ignoreFailures=true
       maven.multiproject.includes=*/project.xml
       maven.multiproject.excludes= tool-xdoclet/project.xml ,
tool-maven-plugin/project.xml


   * add to envirnment variable MAVEN_OPTS the options:

        -XX:MaxPermSize=128m -Xmx256m

   * run "maven jar:install" in directories {keel_home}/keel-build,
     keel/tool-maven and keel/tool-maven-plugin.
   * run "maven plugin:install" inside directory
     {keel_home}/tool-maven-plugin
   * run "maven -Dgoal=jar:install multiproject:goal" inside directory
     {keel_home}
   * delete all the maven ".cache" files (see
     {maven.home.local}/cache/*.cache)
   * run "maven keel:maven clean war" inside project root directory; if
     needed, put in this directory the files build.properties et
     project.xml (see for example "default" example).

Not all the steps are always needed. Run the 3 last ones each time you
update from CVS and you get some trouble.

About the last step, you don't always need keel:maven+clean+war. Usualy,
war is enough.

Last point: each time a library version in a module is updated, it's a
mess even with the above process. You have to check and remove all the
"conflict" tag in your(s) project.xml file(s) before to run your
application.


Pierre


http://keelframework.org/documentation.shtml
Keelgroup mailing list
Keelgroup@list...
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com