[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph updated MAGNOLIA-2716:
-------------------------------------

    Fix Version/s: 4.2.x
                       (was: 4.0.x)

> Invalid JDOM/JAXEN distribution included
> ----------------------------------------
>
>                 Key: MAGNOLIA-2716
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2716
>             Project: Magnolia
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.0.1
>         Environment: ubuntu 9.04, JBoss 5.0.1, MySQL 5.0
>            Reporter: Egor Kolesnikov
>            Assignee: Grégory Joseph
>             Fix For: 4.2.x
>
>         Attachments: server.txt
>
>
> After changing DERBY repository to MYSQL one, the following error appears 
> while deploying to JBoss 5.0.1:
>       java.lang.NoSuchMethodError: 
> org.jdom.Element.getParent()Lorg/jdom/Element;
>               at 
> org.jaxen.jdom.DocumentNavigator.getParentAxisIterator(DocumentNavigator.java:252)
>               at 
> org.jaxen.expr.iter.IterableParentAxis.iterator(IterableParentAxis.java:82)
>               at org.jaxen.expr.DefaultStep.axisIterator(DefaultStep.java:139)
>               at 
> org.jaxen.expr.DefaultLocationPath.evaluate(DefaultLocationPath.java:188)
> However, after replacing WEB-INF/lib/jaxen-1.0-FCS.jar and 
> WEB-INF/lib/jdom-1.0.jar with jdom.jar, jaxen-core.jar and jaxen-jdom.jar 
> from JDOM1.0 distribution obtained from jdom.org, everything started working 
> properly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to