You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "K.C. Baltz (JIRA)" <ji...@codehaus.org> on 2006/04/26 18:43:19 UTC
[jira] Commented: (MEV-382) Display tag does not specify a version
for beanutils, but appears to need 1.7+
[ http://jira.codehaus.org/browse/MEV-382?page=comments#action_64197 ]
K.C. Baltz commented on MEV-382:
--------------------------------
If I build an app with no dependencies other than displaytag-1.1, I get commons-beanutils-1.7 jar in WEB-INF/lib.
If I also have an explicit dependency on beanutils-1.6 in my pom, then I don't get commons-beanutils-1.7 jar, I get 1.6.
I'll assume this is correct behavior and my fault for specifying a conflicting dependency.
Also, sorry about assuming the version wasn't specified. I didn't think to check for a parent pom.
> Display tag does not specify a version for beanutils, but appears to need 1.7+
> ------------------------------------------------------------------------------
>
> Key: MEV-382
> URL: http://jira.codehaus.org/browse/MEV-382
> Project: Maven Evangelism
> Type: Bug
> Components: Invalid POM
> Reporter: K.C. Baltz
> Assignee: fabrizio giustina
>
>
> We tried upgrading our displaytag in our project today and kept getting NoClassDefFound errors for NestedNullException. According to the Javadoc, that class was added in vesrion 1.7 of commons-beanutils. The Pom for displaytag-1.1 doesn't specify a version. It seems to me it needs to say 1.7. Otherwise I'm guessing Maven will grab whatever version is already in the project, which I think was 1.6.1 since that's what Struts wants.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira