openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dianne Richards (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OPENJPA-2077) Pom references to org.codehaus.mojo openjpa-maven-plugin cause problems
Date Sat, 26 Nov 2011 23:08:40 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dianne Richards resolved OPENJPA-2077.
--------------------------------------

    Resolution: Fixed
    
> Pom references to org.codehaus.mojo openjpa-maven-plugin cause problems
> -----------------------------------------------------------------------
>
>                 Key: OPENJPA-2077
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2077
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Dianne Richards
>            Assignee: Dianne Richards
>             Fix For: 2.2.0
>
>
> I made a change to XMLPersistenceMetaDataParser, adding a call to StringUtils.endsWithIgnoreCase().It
worked fine in eclipse. But it failed with a maven build with a NoSuchMethodException. StringUtils
is in commons-lang. This method is introduced  in version 2.4 The openjpa-parent pom.xml does
specify version 2.4, so it should work. But, it also specifies org.codehaus.mojo openjpa-maven-plugin.
Investigation discovered that this is pulling in commons-lang version 2.1,which is being used
and gives the exception.
> I've discussed this with several people. The consensus is that the openjpa-maven-plugin
that was introduced by OPENJPA-1934 was meant as a replacement for the codehaus version. So,
I've changed multiple pom files, replacing references to the codehaus version with the apache
version. I've tested these changes on a complete build and it works fine.
> I'll wait a day or 2 before committing, in case someone knows of a problem with this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message