AW: Build Problem HOJ

Hi Raj,

I tried to do a maven jar:install on keel-common and got the same error.
This seems to be a new problem.
Although the missing library xalan-2.3.1.jar is downloaded successfully, it
still gives an error.
I solved by adding a dependency to project.xml in keel-common:
<dependency>

<groupId>xalan</groupId>

<artifactId>xalan</artifactId>

<version>2.3.1</version>

<type>jar</type>

<properties>

<war.bundle>true</war.bundle>

<keel.client>true</keel.client>

</properties>

</dependency>

 This made maven jar:install work successfully.

Uta



 -----Ursprüngliche Nachricht-----
Von: keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org
[mailto:keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org]Im Auftrag
von Raj Joshi
Gesendet: Dienstag, 30. August 2005 19:11
An: developers-6VIttnCrOeJXNEnpj1eHPNi2O/[email protected]
Betreff: Re: [Keelgroup] Build Problem HOJ


  Ok. I fetched fresh copy of entire keel project from CVS.
  went smoothly until the command:
  maven -Dgoal=jar:install multiproject:goal
  errors out with:
  multiproject:goal:
  build:start:

  java:prepare-filesystem:
      [mkdir] Created dir: C:\keel\keel-common\target\classes

  java:compile:
      [echo] Compiling to C:\keel\keel-common/target/classes
      [javac] Compiling 32 source files to
C:\keel\keel-common\target\classes
  C:\keel\keel-common\src\java\org\keel\util\i18n\DynamicMessageSupport.java
:35: p
  ackage org.apache.xpath does not exist
  import org.apache.xpath.XPathAPI;
                          ^
  C:\keel\keel-common\src\java\org\keel\util\i18n\DynamicMessageSupport.java
:529:
  cannot find symbol
  symbol  : variable XPathAPI
  location: class org.keel.util.i18n.DynamicMessageSupport
              NodeList resourcesList = XPathAPI.selectNodeList(doc,
ALL_RESOURCES)
  ;
                                       ^
  2 errors

  BUILD FAILED
  File...... C:\Documents and
Settings\U743937\.maven\cache\maven-multiproject-plu
  gin-1.3.1\plugin.jelly
  Element... maven:reactor
  Line...... 217
  Column.... 9
  Unable to obtain goal [java:compile] -- C:\Documents and
Settings\U743937\.maven
  \cache\maven-java-plugin-1.5\plugin.jelly:63:48: <ant:javac> Compile
failed; see
   the compiler error output for details.
  Total time: 10 seconds
  Finished at: Tue Aug 30 12:32:41 EDT 2005

  -raj


  On 8/30/05, Uta Kapp <[email protected]> wrote:
    Hi Raj,

    I got going with the default example by rebuilding all modules from CVS
    HEAD. I strictly followed
    a check list of Pierre.

    Here are the steps to do:

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

    2.) Build the newest maven-keel-plugin from source and install
        a) Delete the maven cache .maven/cache
        b) run "maven jar:install" in directories {keel_home}/keel-build,
          keel/tool-maven and keel/tool-maven-plugin.

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

    3.) Rebuild all Jar Files from CVS
    It is important, that maven does not fetch any old libraries for the
keel
    modules
    from  maven.repo.remote, so you first have to get going with the command

    "maven -Dgoal=jar:install multiproject:goal" inside directory
{keel_home}

    this will rebuild all keel modules.

    To make the command work, you have to create a build.properties in your
    {home} directory to control maven.multiproject:
    {home} depends on your operating system. on windows it usually is
somewhere
    in C:\Documents and Settings
    If you do not redefine your maven.repo.local property, the maven
repository
    is created automatically in {home}.

    build.properties:

       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



    Since the multiproject goal uses a lot of memory add to environment
variable
    MAVEN_OPTS the options:

         -XX:MaxPermSize=128m -Xmx256m
    I defined it in the file {maven_home}/bin/maven.bat for windows and
    {maven_home}/bin/maven for Linux

    4.) Build the war files

    When all the modules are built from cvs the war is ready to be built.
    a) Fetch a fresh version from CVS HEAD for /example-projects/default and
    copy to preferred location
    b) delete all the maven ".cache" files
(see{maven.home.local}/cache/*.cache)
    to be shure to
       use the latest plugin and not something old from cache
    c) run "maven keel:maven" inside project root directory
       even if warnings occur, it is only important to finish with "build
    successfull".

    d) run "maven war"

    5.) Get going with HOJ

    To test the HOJ project, I copied the default project and modified:

    a) I added 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"

    I deployed on Tomcat 5.5.1

    The HOJ functions work. It is a good idea to get going with keel if
    you work through the HOJ project.

    Uta

    -----Ursprüngliche Nachricht-----
    Von: keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org
    [mailto:keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org]Im
    Auftrag von Raoul Pierre
    Gesendet: Dienstag, 30. August 2005 08:24
    An: developers-6VIttnCrOeJXNEnpj1eHPNi2O/[email protected]
    Betreff: Re: AW: [Keelgroup] Build Problem HOJ


    Raj,

    >
    C:\keel\keel-client\src\java\org\keel\clients\DefaultClientConnector.jav
a:25
    :
    > ca
    > nnot find symbol
    > symbol  : class DynamicMessageSupport
    > location: package org.keel.util.i18n
    > import org.keel.util.i18n.DynamicMessageSupport;
    >                           ^

    DynamicMessageSupport is a very new class in keel-common. Can you check
    in default program.xml the keel-common version: 3.1

    Here, I can ran default application without probleme (Tomcat 5.0.28).

    About hoj: there is much more dependencies than in default application.
    One of them seems to be de trop, the log file gives:

    [...]
    [KeelContainer] Try re-building this application
    Error initializing container:
    org.keel.core.exception.NestedException: Cannot set up Container.
    Startup lifecycle failure
        at
    org.keel.core.container.KeelContainerFactory.getContainerManager(KeelCon
tain
    erFactory.java:234)
    [...]

    I don't know enough avalon container to help here. And I haven't time to
    check all the dependencies in hoj to find the culprit...

    Pierre


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

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