openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Solodovnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENMEETINGS-501) fresh build fails with class org/jdom/JDOMException not found in anakia build section
Date Wed, 09 Jan 2013 03:12:12 GMT

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547587#comment-13547587
] 

Maxim Solodovnik commented on OPENMEETINGS-501:
-----------------------------------------------

Dear Burkhard,

Thanks for your patch.
I never seen such error (using automatic builds and manual builds on *nix and Windows machines)
Can you please describe how were you able to get this error message?
                
> 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: Improvement
>          Components: BuildsAndReleases
>    Affects Versions: 2.0 Apache Incubator Release
>         Environment: ant 1.8.3
>            Reporter: Burkhard Buelte
>            Assignee: SebastianWagner
>            Priority: Minor
>              Labels: build
>         Attachments: build-anakia-jdomjar-missin.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> 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