openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Burkhard Buelte (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OPENMEETINGS-501) fresh build fails with class org/jdom/JDOMException not found in anakia build section
Date Tue, 08 Jan 2013 22:32:13 GMT
Burkhard Buelte created OPENMEETINGS-501:
--------------------------------------------

             Summary: fresh build fails with class org/jdom/JDOMException not found in anakia
build section
                 Key: OPENMEETINGS-501
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-501
             Project: Openmeetings
          Issue Type: Bug
          Components: BuildsAndReleases
    Affects Versions: 2.0 Apache Incubator Release
         Environment: ant 1.8.3
            Reporter: Burkhard Buelte
            Assignee: SebastianWagner
            Priority: Trivial


ant build fails with following error message

-retrieve-anakia:

anakia:

BUILD FAILED
C:\src\openmeeting2\singlewebapp\build.xml:694: taskdef A class needed by class
org.apache.velocity.anakia.AnakiaTask cannot be found: org/jdom/JDOMException
 using the classloader AntClassLoader[....

Reson: The anakia lib folder is empty (path  ./build/lib/anakia)  but should contain  jdom*.jar,
oro*.jar and logkit*.jar.  These were not downloaded by ivy task.

Possible Fix:
in build task          target name="-availability-check"    include a check that jdom is available.

After my workaround, replacing around lin 820

<available classpathref="check.anakia.classpath" classname="org.apache.oro.text.GlobCompiler"
/>

by

 <condition property="anakia.installed">
           <and>
    <available classpathref="check.anakia.classpath" classname="org.apache.oro.text.GlobCompiler"
/>
    <available classpathref="check.anakia.classpath" classname="org.jdom.JDOMException"
 />
            </and>
</condition>

build will complete w/o error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message