Re: Keel build missing doclet-keel-1.2.2.zip

Raoul Pierre <[email protected]> Sun, 25 Sep 2005 03:15:39 +0200
Newsgroups gmane.comp.java.keel.devel
Message-ID <[email protected]>
Billy,

>
> I tried ant again, because I wasn't able to get maven to work.  I've 
> tried the build 20 times or so, but no luck.  Here is what I get when 
> trying to build  new project:
> It generates some files (see attachment), but is is only a couple of 
> directories, with source *.java files, but nothing compiles.  Is that 
> what I am supposed to get?  Also, I keep getting the following error 
> when I try to build the example project:
>
> "Attempting to download js-1.0.jar.
> WARNING: Failed to download js-1.0.jar.
> The build cannot continue because of the following unsatisfied 
> dependency:
>
> js-1.0.jar"

I found this dependency only in projects /all and /helm under 
keel-build/example-projects.

js/js-1.0.jar is neither in ibiblio nor keel maven repositories.

I think that you can replace it with rhino/js-1.6R1.jar. Anybody can 
confirm?

See also below.

>
> Also, I am using Maven 1.02 and following the exact directions of 
> provided by another user for Maven builds.

Maven 1.02 is OK

>
> Any suggestions?

Before to build your own application, did you succeed in building hoj or 
default keel examples?

Here is a check listwhen any trouble:

1.) Get all modules from Keels cvs to a directory of your choice, here referred to as {keel_home}

2.) Configure maven (access to remote maven repositories and others options)

a) Create a file build.properties in your {home} directory.

   Note: {home} depends on your operating system. On windows 
         it usually is C:\Documents and Settings\myDirectory.

b) Put in your {home}/build.properties:

   maven.repo.remote=http://www.ibiblio.org/maven,
   http://www.apache.org/dist/java-repository,
   http://www.keelframework.org/maven

   maven.multiproject.ignoreFailures=true
   maven.multiproject.includes=**/project.xml
   maven.multiproject.excludes=
   keel-build/example-projects/**/project.xml,
   **/target/**/project.xml
   
Note: in your real file, don't put any new line in the 2 lists above.

3.) Since the multiproject goal below uses a lot of memory, add 
    to your environment the variable MAVEN_OPTS with the options:

     -XX:MaxPermSize=128m -Xmx256m

Note: it's possible to define it in the file {maven_home}/bin/maven.bat for windows and {maven_home}/bin/maven for Linux

4.) Build maven-keel-plugin:

    a) run "maven jar:install" in directories: {keel_home}/keel-build first,
       then {keel_home}/tool-maven

       Note: run it also in {keel_home}/tool-maven-plugin if you want a jar file
             for maven keel plugin. It's not necessary to use maven keel plugin.

    b) run "maven plugin:install" inside directory {keel_home}/tool-maven-plugin

5.) (Re)build all keel jar files. 

a) Delete all the "cache" files (*.cache) in your maven cache directory
   
   Note: if you do not redefine neither "maven.home.local" nor
         "maven.plugin.unpacked.dir" in your build.properties, 
         the maven cache directory must be under {home}, e.g.
         {home}/.maven/cache
         You don't need to delete all the "cache" directory, only the "cache" 
         files inside it.

b) Delete all the keel target directories, run inside directory {keel_home}:

    delete */target 

    (in Unix/Cygwin: find . -name target -exec rm -rf {} \;)

c) Run inside directory {keel_home}:

    "maven multiproject:install" 

   Note: not all the jars are available from maven repositories, especialy 
         eclipse (not the last version) and jndi (Sun license) ones. See the 
         mailling list to get more information.

6.) Build the project war file. Here we'll start with keel default project example.

    a) copy {maven_home}/build-keel/example-projects/default 
       to preferred location, i.e. 
       {keel_home}/build-keel/default

    b) run "maven keel:maven" inside project root directory
       Note: even if warnings occur, it is only important to finish 
       with "build successfull".

    c) run "maven war" inside project root directory

7.) Get going with HOJ

To test the HOJ project, copy the default project and modified:

a) Add a HOJ dependency to the project.xml:

    <dependency>
      <groupId>keel</groupId>
      <artifactId>app-hoj</artifactId>
      <version>1.1</version>
      <properties>
        <keel.server>true</keel.server>
      </properties>
    </dependency>

b) run "maven keel:maven"

c) run "maven war"

8.) Your own project: 

a) create your project directory

b) copy in it project.xml (and build.properties if needed) from the keel default project

c) add in project.xml all the dependencies you need

d) run "maven keel:maven"

e) run "maven war"




Pierre


http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com